DcUsers dc_wiki-users https://users.duckcorp.org//index.php/Main_Page MediaWiki 1.39.5 first-letter Media Special Talk User User talk DcUsers DcUsers talk File File talk MediaWiki MediaWiki talk Template Template talk Help Help talk Category Category talk 0 1 1 2010-04-25T18:17:51Z MediaWiki default 0 wikitext text/x-wiki <big>'''MediaWiki has been successfully installed.'''</big> Consult the [http://meta.wikimedia.org/wiki/Help:Contents User's Guide] for information on using the wiki software. == Getting started == * [http://www.mediawiki.org/wiki/Manual:Configuration_settings Configuration settings list] * [http://www.mediawiki.org/wiki/Manual:FAQ MediaWiki FAQ] * [https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list] bd962048d95fbb6b6b514885867811db20a5476b 2 1 2010-04-25T21:25:12Z Duck 2 Replaced content with '{{:Main Page/Introduction}}' wikitext text/x-wiki {{:Main Page/Introduction}} b9b916baa745685dc9c6499120ba043ab68862cb 23 2 2010-04-25T21:34:09Z Duck 2 Protected "[[Main Page]]" ([edit=sysop] (indefinite) [move=sysop] (indefinite)) wikitext text/x-wiki {{:Main Page/Introduction}} b9b916baa745685dc9c6499120ba043ab68862cb 0 2 3 2010-04-25T21:25:44Z Duck 2 Created page with '{{Robelbox|title=Admin Areas|theme={{{theme|1}}}}} {{Padbox}} Coin ! {{Padbox/close}} {{Robelbox/close}}' wikitext text/x-wiki {{Robelbox|title=Admin Areas|theme={{{theme|1}}}}} {{Padbox}} Coin ! {{Padbox/close}} {{Robelbox/close}} 9b1b61f4a331b8f628a62436189689ec21aaba9c 22 3 2010-04-25T21:33:55Z Duck 2 wikitext text/x-wiki {{Robelbox|title=Introduction|theme={{{theme|1}}}}} {{Padbox}} Coin ! {{Padbox/close}} {{Robelbox/close}} 0bbab7f8144d373b003bbf9c5c92b7effd616922 10 3 4 2010-04-25T21:26:36Z Duck 2 Created page with '<div style="{{Robelbox/pad}}">' wikitext text/x-wiki <div style="{{Robelbox/pad}}"> 9f26510a8abf1c68aba668494f1397a72a40d9dc 5 4 2010-04-25T21:27:19Z Duck 2 Protected "[[Template:Padbox]]" ([edit=sysop] (indefinite) [move=sysop] (indefinite)) wikitext text/x-wiki <div style="{{Robelbox/pad}}"> 9f26510a8abf1c68aba668494f1397a72a40d9dc 10 4 6 2010-04-25T21:27:39Z Duck 2 Created page with '</div>' wikitext text/x-wiki </div> 125a168e24b2bd38aadb84cbb5f87f316b073c41 7 6 2010-04-25T21:27:45Z Duck 2 Protected "[[Template:Padbox/close]]" ([edit=sysop] (indefinite) [move=sysop] (indefinite)) wikitext text/x-wiki </div> 125a168e24b2bd38aadb84cbb5f87f316b073c41 10 5 8 2010-04-25T21:28:16Z Duck 2 Created page with '<noinclude> This Template was borrowed from the wikiversity wiki (2009-05-26). '''''This page has been protected for good reason! If you are a custodian editing this page, plea…' wikitext text/x-wiki <noinclude> This Template was borrowed from the wikiversity wiki (2009-05-26). '''''This page has been protected for good reason! If you are a custodian editing this page, please read the talk page first! Thank you.''''' ''This is a special kind of box with a hanging icon in the right hand top corner. The size of the icon can be increased indefinitely without the height of the title bar being affected. If an empty title is specified, the title bar shrinks to a small band.'' </noinclude> {| cellspacing="2" cellpadding="0" style="margin:0em 0em 0em 0em; width:{{{width|100%}}}; {{#ifeq:{{{height|100%}}}|none||height:{{{height|100%}}}}};" | colspan="1" style="width:100%; {{#ifeq:{{{height|100%}}}|none||height:100%;}} vertical-align:top; border:1px solid {{Robelbox/C2|{{{theme|1}}}}}; background-color:{{Robelbox/C1|{{{theme|1}}}}};" | {{#ifeq:{{{icon|default}}}|default||[[Image:{{{icon|Namespace Wikipedia.svg}}}|{{{iconwidth|32px}}}|right]]}} <div style="border-bottom:1px solid {{Robelbox/C2|{{{theme|1}}}}}; background-color:{{Robelbox/C3|{{{theme|1}}}}}; padding:0.2em 0.9em 0.2em 0.5em; font-size:120%; font-weight:bold;">{{{title|Title}}}</div> <noinclude><div style="padding:0.75em 1.5em 0em 0.75em;"> ''Parameters:'' * ''theme'': Values 1 to 14; gives colour scheme: {{Robelbox/theme}} * ''title'': Box title. * ''width'': Box width; default is 100%. * ''height'': Guess; default is 100%. * ''icon'': Image name for icon. * ''iconwidth'': Pixel width of icon; default is 56. Include "px". ''Don't forget to use the <nowiki>{{Robelbox/close}}</nowiki> template after your content!'' <br>''This template should be used together with <nowiki>{{Robelbox/pad}}</nowiki> to pad out the box contents - see examples below, and see talk page. </div> |} ==Simple examples== __TOC__ ===Theme 1: Tan (default)=== This code: <nowiki>{{robelbox|title=Test title}} <div style="{{Robelbox/pad}}"> Test content using a default box </div> {{Robelbox/close}}</nowiki> produces this box: {{robelbox|title=Test title}} <div style="{{Robelbox/pad}}"> Test content using a default box </div> {{Robelbox/close}} ===Theme 2: Mid green=== This code: <nowiki> {{robelbox|theme=2|title=Test title}} <div style="{{Robelbox/pad}}"> Test content using a default box with theme=2 </div> {{Robelbox/close}} </nowiki> produces this box: {{robelbox|theme=2|title=Test title}} <div style="{{Robelbox/pad}}"> Test content using a default box with theme=2 </div> {{Robelbox/close}} == Color samples == {| |{{Robelbox|theme=1|title=Theme 1|width=200px|iconwidth=48px}}<div style="{{Robelbox/pad}}"> ''Content goes here.'' </div> {{Robelbox-close}} |{{Robelbox|theme=2|title=Theme 2|width=200px|iconwidth=48px}}<div style="{{Robelbox/pad}}"> ''Content goes here.'' </div> {{Robelbox-close}} |{{Robelbox|theme=3|title=Theme 3|width=200px|iconwidth=48px}}<div style="{{Robelbox/pad}}"> ''Content goes here.'' </div> {{Robelbox-close}} |{{Robelbox|theme=4|title=Theme 4|width=200px|iconwidth=48px}}<div style="{{Robelbox/pad}}"> ''Content goes here.'' </div> {{Robelbox-close}} |- |{{Robelbox|theme=5|title=Theme 5|width=200px|iconwidth=48px}}<div style="{{Robelbox/pad}}"> ''Content goes here.'' </div> {{Robelbox-close}} |{{Robelbox|theme=6|title=Theme 6|width=200px|iconwidth=48px}}<div style="{{Robelbox/pad}}"> ''Content goes here.'' </div> {{Robelbox-close}} |{{Robelbox|theme=7|title=Theme 7|width=200px|iconwidth=48px}}<div style="{{Robelbox/pad}}"> ''Content goes here.'' </div> {{Robelbox-close}} |{{Robelbox|theme=8|title=Theme 8|width=200px|iconwidth=48px}}<div style="{{Robelbox/pad}}"> ''Content goes here.'' </div> {{Robelbox-close}} |- |{{Robelbox|theme=9|title=Theme 9|width=200px|iconwidth=48px}}<div style="{{Robelbox/pad}}"> ''Content goes here.'' </div> {{Robelbox-close}} |{{Robelbox|theme=10|title=Theme 10|width=200px|iconwidth=48px}}<div style="{{Robelbox/pad}}"> ''Content goes here.'' </div> {{Robelbox-close}} |{{Robelbox|theme=11|title=Theme 11|width=200px|iconwidth=48px}}<div style="{{Robelbox/pad}}"> ''Content goes here.'' </div> {{Robelbox-close}} |{{Robelbox|theme=12|title=Theme 12|width=200px|iconwidth=48px}}<div style="{{Robelbox/pad}}"> ''Content goes here.'' </div> {{Robelbox-close}} |- |{{Robelbox|theme=13|title=Theme 13|width=200px|iconwidth=48px}}<div style="{{Robelbox/pad}}"> ''Content goes here.'' </div> {{Robelbox-close}} |{{Robelbox|theme=14|title=Theme 14|width=200px|iconwidth=48px}}<div style="{{Robelbox/pad}}"> ''Content goes here.'' </div> {{Robelbox-close}} |} [[Category:Design templates]]</noinclude> 755a9aa4cdafc9d728aef2887ec597baea4d9cfa 9 8 2010-04-25T21:28:24Z Duck 2 Protected "[[Template:Robelbox]]" ([edit=sysop] (indefinite) [move=sysop] (indefinite)) wikitext text/x-wiki <noinclude> This Template was borrowed from the wikiversity wiki (2009-05-26). '''''This page has been protected for good reason! If you are a custodian editing this page, please read the talk page first! Thank you.''''' ''This is a special kind of box with a hanging icon in the right hand top corner. The size of the icon can be increased indefinitely without the height of the title bar being affected. If an empty title is specified, the title bar shrinks to a small band.'' </noinclude> {| cellspacing="2" cellpadding="0" style="margin:0em 0em 0em 0em; width:{{{width|100%}}}; {{#ifeq:{{{height|100%}}}|none||height:{{{height|100%}}}}};" | colspan="1" style="width:100%; {{#ifeq:{{{height|100%}}}|none||height:100%;}} vertical-align:top; border:1px solid {{Robelbox/C2|{{{theme|1}}}}}; background-color:{{Robelbox/C1|{{{theme|1}}}}};" | {{#ifeq:{{{icon|default}}}|default||[[Image:{{{icon|Namespace Wikipedia.svg}}}|{{{iconwidth|32px}}}|right]]}} <div style="border-bottom:1px solid {{Robelbox/C2|{{{theme|1}}}}}; background-color:{{Robelbox/C3|{{{theme|1}}}}}; padding:0.2em 0.9em 0.2em 0.5em; font-size:120%; font-weight:bold;">{{{title|Title}}}</div> <noinclude><div style="padding:0.75em 1.5em 0em 0.75em;"> ''Parameters:'' * ''theme'': Values 1 to 14; gives colour scheme: {{Robelbox/theme}} * ''title'': Box title. * ''width'': Box width; default is 100%. * ''height'': Guess; default is 100%. * ''icon'': Image name for icon. * ''iconwidth'': Pixel width of icon; default is 56. Include "px". ''Don't forget to use the <nowiki>{{Robelbox/close}}</nowiki> template after your content!'' <br>''This template should be used together with <nowiki>{{Robelbox/pad}}</nowiki> to pad out the box contents - see examples below, and see talk page. </div> |} ==Simple examples== __TOC__ ===Theme 1: Tan (default)=== This code: <nowiki>{{robelbox|title=Test title}} <div style="{{Robelbox/pad}}"> Test content using a default box </div> {{Robelbox/close}}</nowiki> produces this box: {{robelbox|title=Test title}} <div style="{{Robelbox/pad}}"> Test content using a default box </div> {{Robelbox/close}} ===Theme 2: Mid green=== This code: <nowiki> {{robelbox|theme=2|title=Test title}} <div style="{{Robelbox/pad}}"> Test content using a default box with theme=2 </div> {{Robelbox/close}} </nowiki> produces this box: {{robelbox|theme=2|title=Test title}} <div style="{{Robelbox/pad}}"> Test content using a default box with theme=2 </div> {{Robelbox/close}} == Color samples == {| |{{Robelbox|theme=1|title=Theme 1|width=200px|iconwidth=48px}}<div style="{{Robelbox/pad}}"> ''Content goes here.'' </div> {{Robelbox-close}} |{{Robelbox|theme=2|title=Theme 2|width=200px|iconwidth=48px}}<div style="{{Robelbox/pad}}"> ''Content goes here.'' </div> {{Robelbox-close}} |{{Robelbox|theme=3|title=Theme 3|width=200px|iconwidth=48px}}<div style="{{Robelbox/pad}}"> ''Content goes here.'' </div> {{Robelbox-close}} |{{Robelbox|theme=4|title=Theme 4|width=200px|iconwidth=48px}}<div style="{{Robelbox/pad}}"> ''Content goes here.'' </div> {{Robelbox-close}} |- |{{Robelbox|theme=5|title=Theme 5|width=200px|iconwidth=48px}}<div style="{{Robelbox/pad}}"> ''Content goes here.'' </div> {{Robelbox-close}} |{{Robelbox|theme=6|title=Theme 6|width=200px|iconwidth=48px}}<div style="{{Robelbox/pad}}"> ''Content goes here.'' </div> {{Robelbox-close}} |{{Robelbox|theme=7|title=Theme 7|width=200px|iconwidth=48px}}<div style="{{Robelbox/pad}}"> ''Content goes here.'' </div> {{Robelbox-close}} |{{Robelbox|theme=8|title=Theme 8|width=200px|iconwidth=48px}}<div style="{{Robelbox/pad}}"> ''Content goes here.'' </div> {{Robelbox-close}} |- |{{Robelbox|theme=9|title=Theme 9|width=200px|iconwidth=48px}}<div style="{{Robelbox/pad}}"> ''Content goes here.'' </div> {{Robelbox-close}} |{{Robelbox|theme=10|title=Theme 10|width=200px|iconwidth=48px}}<div style="{{Robelbox/pad}}"> ''Content goes here.'' </div> {{Robelbox-close}} |{{Robelbox|theme=11|title=Theme 11|width=200px|iconwidth=48px}}<div style="{{Robelbox/pad}}"> ''Content goes here.'' </div> {{Robelbox-close}} |{{Robelbox|theme=12|title=Theme 12|width=200px|iconwidth=48px}}<div style="{{Robelbox/pad}}"> ''Content goes here.'' </div> {{Robelbox-close}} |- |{{Robelbox|theme=13|title=Theme 13|width=200px|iconwidth=48px}}<div style="{{Robelbox/pad}}"> ''Content goes here.'' </div> {{Robelbox-close}} |{{Robelbox|theme=14|title=Theme 14|width=200px|iconwidth=48px}}<div style="{{Robelbox/pad}}"> ''Content goes here.'' </div> {{Robelbox-close}} |} [[Category:Design templates]]</noinclude> 755a9aa4cdafc9d728aef2887ec597baea4d9cfa 10 6 10 2010-04-25T21:28:54Z Duck 2 Created page with '|}<noinclude>[[Category:Design templates]]</noinclude>' wikitext text/x-wiki |}<noinclude>[[Category:Design templates]]</noinclude> 703fe1b4d0ad60f4ca451d4b907c9c5661a05e4d 11 10 2010-04-25T21:29:01Z Duck 2 Protected "[[Template:Robelbox/close]]" ([edit=sysop] (indefinite) [move=sysop] (indefinite)) wikitext text/x-wiki |}<noinclude>[[Category:Design templates]]</noinclude> 703fe1b4d0ad60f4ca451d4b907c9c5661a05e4d 10 7 12 2010-04-25T21:29:33Z Duck 2 Created page with '{{#switch:{{{1|1}}} |1=<nowiki>#ffFcF1</nowiki> |2=MintCream |3=AliceBlue |4=MistyRose |5=LavenderBlush |6=Ivory |7=Azure |8=Seashell |9=<nowiki>#f6fff1</nowiki> |10=<n…' wikitext text/x-wiki {{#switch:{{{1|1}}} |1=<nowiki>#ffFcF1</nowiki> |2=MintCream |3=AliceBlue |4=MistyRose |5=LavenderBlush |6=Ivory |7=Azure |8=Seashell |9=<nowiki>#f6fff1</nowiki> |10=<nowiki>#f4faff</nowiki> |11=<nowiki>#FFF8FF</nowiki> |12=<nowiki>#FFF6F8</nowiki> |13=<nowiki>#F5F5FF</nowiki> |14=<nowiki>#ffffff</nowiki> |15=Thistle }}<noinclude><!-- WARNING: DON'T INTRODUCE ANY NEWLINES INTO THIS TEMPLATE BY ACCIDENT!!!! --> [[Category:Design templates]] </noinclude> a1aab6ade7f389085cea1474c4eaa86d2280b044 13 12 2010-04-25T21:29:39Z Duck 2 Protected "[[Template:Robelbox/C1]]" ([edit=sysop] (indefinite) [move=sysop] (indefinite)) wikitext text/x-wiki {{#switch:{{{1|1}}} |1=<nowiki>#ffFcF1</nowiki> |2=MintCream |3=AliceBlue |4=MistyRose |5=LavenderBlush |6=Ivory |7=Azure |8=Seashell |9=<nowiki>#f6fff1</nowiki> |10=<nowiki>#f4faff</nowiki> |11=<nowiki>#FFF8FF</nowiki> |12=<nowiki>#FFF6F8</nowiki> |13=<nowiki>#F5F5FF</nowiki> |14=<nowiki>#ffffff</nowiki> |15=Thistle }}<noinclude><!-- WARNING: DON'T INTRODUCE ANY NEWLINES INTO THIS TEMPLATE BY ACCIDENT!!!! --> [[Category:Design templates]] </noinclude> a1aab6ade7f389085cea1474c4eaa86d2280b044 10 8 14 2010-04-25T21:29:54Z Duck 2 Created page with '{{#switch:{{{1|1}}} |1=<nowiki>#E39C79</nowiki> |2=ForestGreen |3=SteelBlue |4=IndianRed |5=MediumPurple |6=Gold |7=RoyalBlue |8=<nowiki>#E78A69</nowiki> |9=<nowiki>#71b…' wikitext text/x-wiki {{#switch:{{{1|1}}} |1=<nowiki>#E39C79</nowiki> |2=ForestGreen |3=SteelBlue |4=IndianRed |5=MediumPurple |6=Gold |7=RoyalBlue |8=<nowiki>#E78A69</nowiki> |9=<nowiki>#71be3f</nowiki> |10=<nowiki>#4290bc</nowiki> |11=<nowiki>#C289C3</nowiki> |12=<nowiki>#C56B74</nowiki> |13=<nowiki>#8488DC</nowiki> |14=<nowiki>#aaaaaa</nowiki> |15=Thistle }}<noinclude><!-- WARNING: DON'T INTRODUCE ANY NEWLINES INTO THIS TEMPLATE BY ACCIDENT!!!! --> [[Category:Design templates]] </noinclude> ad5c8d543da0c84fe3e756d6a646cc2445ec7b3b 15 14 2010-04-25T21:30:01Z Duck 2 Protected "[[Template:Robelbox/C2]]" ([edit=sysop] (indefinite) [move=sysop] (indefinite)) wikitext text/x-wiki {{#switch:{{{1|1}}} |1=<nowiki>#E39C79</nowiki> |2=ForestGreen |3=SteelBlue |4=IndianRed |5=MediumPurple |6=Gold |7=RoyalBlue |8=<nowiki>#E78A69</nowiki> |9=<nowiki>#71be3f</nowiki> |10=<nowiki>#4290bc</nowiki> |11=<nowiki>#C289C3</nowiki> |12=<nowiki>#C56B74</nowiki> |13=<nowiki>#8488DC</nowiki> |14=<nowiki>#aaaaaa</nowiki> |15=Thistle }}<noinclude><!-- WARNING: DON'T INTRODUCE ANY NEWLINES INTO THIS TEMPLATE BY ACCIDENT!!!! --> [[Category:Design templates]] </noinclude> ad5c8d543da0c84fe3e756d6a646cc2445ec7b3b 10 9 16 2010-04-25T21:30:17Z Duck 2 Created page with '{{#switch:{{{1|1}}} |1=Wheat |2=LightGreen |3=LightSteelBlue |4=LightCoral |5=Thistle |6=<nowiki>#ff9</nowiki> |7=LightSkyBlue |8=Peachpuff |9=<nowiki>#c0eaa6</nowiki> …' wikitext text/x-wiki {{#switch:{{{1|1}}} |1=Wheat |2=LightGreen |3=LightSteelBlue |4=LightCoral |5=Thistle |6=<nowiki>#ff9</nowiki> |7=LightSkyBlue |8=Peachpuff |9=<nowiki>#c0eaa6</nowiki> |10=<nowiki>#9AD4F6</nowiki> |11=<nowiki>#E6C6E6</nowiki> |12=<nowiki>#F4B8BF</nowiki> |13=<nowiki>#CED1FA</nowiki> |14=<nowiki>#e4e4e4</nowiki> |15=Thistle }}<noinclude><!-- WARNING: DON'T INTRODUCE ANY NEWLINES INTO THIS TEMPLATE BY ACCIDENT!!!! --> [[Category:Design templates]] </noinclude> 7fb37bd3831fdd3117081f5031858fae05c4ff59 17 16 2010-04-25T21:30:24Z Duck 2 Protected "[[Template:Robelbox/C3]]" ([edit=sysop] (indefinite) [move=sysop] (indefinite)) wikitext text/x-wiki {{#switch:{{{1|1}}} |1=Wheat |2=LightGreen |3=LightSteelBlue |4=LightCoral |5=Thistle |6=<nowiki>#ff9</nowiki> |7=LightSkyBlue |8=Peachpuff |9=<nowiki>#c0eaa6</nowiki> |10=<nowiki>#9AD4F6</nowiki> |11=<nowiki>#E6C6E6</nowiki> |12=<nowiki>#F4B8BF</nowiki> |13=<nowiki>#CED1FA</nowiki> |14=<nowiki>#e4e4e4</nowiki> |15=Thistle }}<noinclude><!-- WARNING: DON'T INTRODUCE ANY NEWLINES INTO THIS TEMPLATE BY ACCIDENT!!!! --> [[Category:Design templates]] </noinclude> 7fb37bd3831fdd3117081f5031858fae05c4ff59 10 10 18 2010-04-25T21:30:41Z Duck 2 Created page with 'padding-top:0.25em; padding-bottom:0.2em; padding-left:0.5em; padding-right:0.5em;' wikitext text/x-wiki padding-top:0.25em; padding-bottom:0.2em; padding-left:0.5em; padding-right:0.5em; 121a8e49e6354060886bca7cf539e2db0b6f92bf 19 18 2010-04-25T21:31:22Z Duck 2 Protected "[[Template:Robelbox/pad]]" ([edit=sysop] (indefinite) [move=sysop] (indefinite)) wikitext text/x-wiki padding-top:0.25em; padding-bottom:0.2em; padding-left:0.5em; padding-right:0.5em; 121a8e49e6354060886bca7cf539e2db0b6f92bf 10 11 20 2010-04-25T21:33:16Z Duck 2 Created page with ':# tan (default) :# mid green :# slate blue :# red :# mauve :# yellow :# mid blue :# orange :# grey-green :# sky blue :# better mauve :# light red :# blue :# grey' wikitext text/x-wiki :# tan (default) :# mid green :# slate blue :# red :# mauve :# yellow :# mid blue :# orange :# grey-green :# sky blue :# better mauve :# light red :# blue :# grey 43a29fb05c4518a1694ebb0c1ac42c0936d5783c 21 20 2010-04-25T21:33:22Z Duck 2 Protected "[[Template:Robelbox/theme]]" ([edit=sysop] (indefinite) [move=sysop] (indefinite)) wikitext text/x-wiki :# tan (default) :# mid green :# slate blue :# red :# mauve :# yellow :# mid blue :# orange :# grey-green :# sky blue :# better mauve :# light red :# blue :# grey 43a29fb05c4518a1694ebb0c1ac42c0936d5783c 10 12 24 2010-04-25T21:36:28Z Duck 2 Created page with '[[image:warning.gif|Warning!]]<span style="color: red;">{{{1|}}}</span>' wikitext text/x-wiki [[image:warning.gif|Warning!]]<span style="color: red;">{{{1|}}}</span> 56734cbe5324c1eddf3642fff4d5cf682b5d283a 26 24 2010-04-25T21:37:12Z Duck 2 Protected "[[Template:Warning]]" ([edit=sysop] (indefinite) [move=sysop] (indefinite)) wikitext text/x-wiki [[image:warning.gif|Warning!]]<span style="color: red;">{{{1|}}}</span> 56734cbe5324c1eddf3642fff4d5cf682b5d283a 6 13 25 2010-04-25T21:37:01Z Duck 2 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 10 14 27 2010-04-25T21:37:49Z Duck 2 Created page with '[[Image:Stock todo.png|Something to do...]] TODO:' wikitext text/x-wiki [[Image:Stock todo.png|Something to do...]] TODO: 470b04b01324c21b3d16dd8be23851fd05831b46 28 27 2010-04-25T21:37:56Z Duck 2 Protected "[[Template:Todo]]" ([edit=sysop] (indefinite) [move=sysop] (indefinite)) wikitext text/x-wiki [[Image:Stock todo.png|Something to do...]] TODO: 470b04b01324c21b3d16dd8be23851fd05831b46 6 15 29 2010-04-25T21:38:05Z Duck 2 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 10 16 30 2010-04-25T21:38:51Z Duck 2 Created page with '[http://bugs.debian.org/{{{1}}} debian#{{{1}}}]' wikitext text/x-wiki [http://bugs.debian.org/{{{1}}} debian#{{{1}}}] 6d0cc680a0b152cc5dd84d7083ddaf3dc5167b55 31 30 2010-04-25T21:38:57Z Duck 2 Protected "[[Template:Debian-bug]]" ([edit=sysop] (indefinite) [move=sysop] (indefinite)) wikitext text/x-wiki [http://bugs.debian.org/{{{1}}} debian#{{{1}}}] 6d0cc680a0b152cc5dd84d7083ddaf3dc5167b55 10 17 32 2010-04-25T21:40:21Z Duck 2 Created page with '[[image:status_deactivated.png|Status: Deactivated]]' wikitext text/x-wiki [[image:status_deactivated.png|Status: Deactivated]] 12fa9ed9439f52f9849e20476acbd93773315bce 34 32 2010-04-25T21:40:40Z Duck 2 Protected "[[Template:Status deactivated]]" ([edit=sysop] (indefinite) [move=sysop] (indefinite)) wikitext text/x-wiki [[image:status_deactivated.png|Status: Deactivated]] 12fa9ed9439f52f9849e20476acbd93773315bce 6 18 33 2010-04-25T21:40:33Z Duck 2 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 10 19 35 2010-04-25T21:41:56Z Duck 2 Created page with '[[image:status_down.png|Status: Unusuable/Down]]' wikitext text/x-wiki [[image:status_down.png|Status: Unusuable/Down]] e96e0ea14ed06b54c6b51d13ba101b054e18ef31 37 35 2010-04-25T21:42:20Z Duck 2 Protected "[[Template:Status down]]" ([edit=sysop] (indefinite) [move=sysop] (indefinite)) wikitext text/x-wiki [[image:status_down.png|Status: Unusuable/Down]] e96e0ea14ed06b54c6b51d13ba101b054e18ef31 6 20 36 2010-04-25T21:42:12Z Duck 2 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 10 21 38 2010-04-25T21:42:39Z Duck 2 Created page with '[[image:status_ok.png|Status: Ok]]' wikitext text/x-wiki [[image:status_ok.png|Status: Ok]] 249932a4d9c6213a8e24e47105a97020e5c25eb0 40 38 2010-04-25T21:42:57Z Duck 2 Protected "[[Template:Status ok]]" ([edit=sysop] (indefinite) [move=sysop] (indefinite)) wikitext text/x-wiki [[image:status_ok.png|Status: Ok]] 249932a4d9c6213a8e24e47105a97020e5c25eb0 6 22 39 2010-04-25T21:42:47Z Duck 2 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 10 23 41 2010-04-25T21:43:37Z Duck 2 Created page with '[[image:status_problems.png|Status: Problems]]' wikitext text/x-wiki [[image:status_problems.png|Status: Problems]] 5810c09693091af8ccf3ebac0996534ea8aae16a 43 41 2010-04-25T21:43:57Z Duck 2 Protected "[[Template:Status problems]]" ([edit=sysop] (indefinite) [move=sysop] (indefinite)) wikitext text/x-wiki [[image:status_problems.png|Status: Problems]] 5810c09693091af8ccf3ebac0996534ea8aae16a 6 24 42 2010-04-25T21:43:50Z Duck 2 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 10 25 44 2010-04-25T21:44:31Z Duck 2 Created page with '[[image:status_unknown.png|Status: Unknown]]' wikitext text/x-wiki [[image:status_unknown.png|Status: Unknown]] a5c92abd052be3a116aee7330a9ff9d5f1c78c50 46 44 2010-04-25T21:44:51Z Duck 2 Protected "[[Template:Status unknown]]" ([edit=sysop] (indefinite) [move=sysop] (indefinite)) wikitext text/x-wiki [[image:status_unknown.png|Status: Unknown]] a5c92abd052be3a116aee7330a9ff9d5f1c78c50 6 26 45 2010-04-25T21:44:44Z Duck 2 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 27 47 2010-04-25T21:45:49Z Duck 2 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 28 48 2010-04-25T21:46:13Z Duck 2 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 6 29 49 2010-04-25T21:46:50Z Duck 2 wikitext text/x-wiki da39a3ee5e6b4b0d3255bfef95601890afd80709 0 30 50 2010-04-25T21:47:41Z Duck 2 Created page with '== The DuckCorp Story == DuckCorp was born in 2000, from Duck's will to construct something more personal out of the CoinNetwork student house's LAN. At that time, it was merely…' wikitext text/x-wiki == The DuckCorp Story == DuckCorp was born in 2000, from Duck's will to construct something more personal out of the CoinNetwork student house's LAN. At that time, it was merely a simple website, advertising a few personal projects. Later, several machines, gathered with various parts from people willing to dispose of them, used the 'duckcorp.org' domain name and provided services for CoinNetwork; this was the begining of the DC's sponsoring mission. Duck then met Rtp, and they began sharing about system administration topics. As they were willing to administrate CoinNetwork better, they began working on the infrastructure and tools together. Rtp created RtpNet, and received the magical SSH key to be a full DC administrator (so do Duck for Rtpnet indeed). They developed a software prototype aimed at managing the most important services of a distributed web of servers (LMS, LDAP Management System), which helped reducing the daily burden of CoinNetwork's administration a lot. After a while working hand in hand, they both found a job and moved to a new home, still helping each other when possible. Currently, RtpNet and DuckCorp have different goals, and follow their own path. On the way, DC found friendly sponsors (in order of appearance): * Nerim (first Orfeo's housing, IPv6 block, indirect sponsor via Hivane) * Hivane (global connectivity, secondary NS and MX) * Sivit (special accomodations for Toushirou's housing and connectivity) (now Nerim again, as it was acquired recently) * Alionis (Orfeo's housing) Thanks a lot pals :-). == The MilkyPond Project == MP is an historical share of an IRC network between DC and RN when they both stopped working on the CoinNetwork project. They were willing to cooperate but with the important changes that occurred in their lives, only IRC was kept as a communication link. With time going, DC began recreating services, with the main server Orfeo being kindly sponsored by Nerim, which was used by RN and later by other associations or individuals. Nothing much is done in the name of MP until 2007, besides adding a Jabber server. In early 2007, RN hired a server, Lechat (Dédibox), and was willing to participate more in the share. At the end of the year, T1R joined to help improving the IRC Network. In September 2007, RN was not able to provide services anymore, as it was too much of a burden. Nevertheless, it is still sponsoring the ''milkypond.org'' domain since then. == Key Dates == * 2000-05-22: DuckCorp is created * 2003-04-25: IANA PEN 16829 * 2003-07-09: RtpNet is created * ~2003-10-20: RSA key exchanged between DC and RN (date is from the exif info, but Photoshop is in the way) * 2004-06-12: MilkyPond is created (after DC and RN stopped working on the CoinNetwork project) * 2005-04/05: Orfeo RAM upgraded (512Mo->1.5Go) (blocked to ~800Mo [[Media:Orfeo.duckcorp.org-memory-day.png|until highmem in kernel]]) * 2005-11-17: the users' mailing-list started * 2005-11: major mail system improvements (SMTP auth, improved antispam, webdesk) * 2005-12-08: Orfeo moved from the Nerim's Ivry datacenter to the Nerim suite in the LDCOM Courbevoie datacenter * 2006-01 to 2006-06: Orfeo problems due to an [http://xfs.org/index.php/XFS_FAQ#Q:_What_is_the_issue_with_directory_corruption_in_Linux_2.6.17.3F XFS bug] * 2007-04: IPv6 Ready * 2007-07: Tōshirō bought and being prepared * 2007-08-08: Nerim's boss shutdown Orfeo violently; quickly repaired and setup behind a mere ADSL (helped by Nerim friends), but BLACKOUT for most services * 2007-08-13: Tōshirō installed in the Sivit suite of the Redbus datacenter, services progressively back online * 2007-09: LDAP infrastructure (again) * 2007-12: Orfeo-NG bough and installed in Alionis suite in EQX (Equinix) datacenter * 2007-12: T1R enters MilkyPond (for the IRC network) * 2008-07: VCS rework, Portal (Restricted Access Helper), Projects Manager (Redmine) * 2009-03: Banya bot (mail gateway for DNS modification, part of the CyborgHood project) * 2009-09: Orfeo moved to [http://www.alionis.net/infra/VBO.html Alionis VBO datacenter] * 2010-03: Thorfinn acquired (Nerim VDS) * 2010-04-24: stratum 2 NTP server [http://support.ntp.org/bin/view/Servers/NtpDuckCorpOrg publicly advertised] and in the [http://www.pool.ntp.org/user/DuckCorp pool] == Admins == * Arnau [~2004-12 to now] * Duck [begining to now] (leader) * Finger [2006-07-05 to 2008-02-04] (assistant) * Mmenal [~2004-12 to ~2006-07] * Rtp [2003-10 to 2007-07-15] == Evolution == No real traces were kept, so old numbers are mere rough guess. * 2000 -> 2004 ** more than 60 users served in the [[Media:Coinnetwork resal 2001-2002.png|CoinNetwork LAN]], nearly no external services besides a basic website and IRC ** services targeted for the CoinNetwork LAN * 2004 -> 2007 ** a few users (probably around 20) and 2 entities (RtpNet and [http://www.hurdfr.org/ HurdFr]) hosted ** more Internet-oriented services (complete mail software suite, MLs, Web hosting, DBs, RCS, ...) * 2007 -> 2010 ** more users (nearly 70 users in 2010, a few not very active) and 2 more entity hosted ([http://thebrain.lautre.net/ TheBrain] and [http://www.andesi.org/ Andesi]) ** more services (Jabber, user-friendly antispam, LDAP, IPv6, ...) == Photos == Look at the [http://photos.duckcorp.org/v/duckcorp/ gallery]. 94f9ebb918775e592fab0af7ad559f1fcf1618db 0 30 51 50 2010-04-25T21:48:33Z Duck 2 Protected "[[A bit of History]]" ([edit=sysop] (indefinite) [move=sysop] (indefinite)) wikitext text/x-wiki == The DuckCorp Story == DuckCorp was born in 2000, from Duck's will to construct something more personal out of the CoinNetwork student house's LAN. At that time, it was merely a simple website, advertising a few personal projects. Later, several machines, gathered with various parts from people willing to dispose of them, used the 'duckcorp.org' domain name and provided services for CoinNetwork; this was the begining of the DC's sponsoring mission. Duck then met Rtp, and they began sharing about system administration topics. As they were willing to administrate CoinNetwork better, they began working on the infrastructure and tools together. Rtp created RtpNet, and received the magical SSH key to be a full DC administrator (so do Duck for Rtpnet indeed). They developed a software prototype aimed at managing the most important services of a distributed web of servers (LMS, LDAP Management System), which helped reducing the daily burden of CoinNetwork's administration a lot. After a while working hand in hand, they both found a job and moved to a new home, still helping each other when possible. Currently, RtpNet and DuckCorp have different goals, and follow their own path. On the way, DC found friendly sponsors (in order of appearance): * Nerim (first Orfeo's housing, IPv6 block, indirect sponsor via Hivane) * Hivane (global connectivity, secondary NS and MX) * Sivit (special accomodations for Toushirou's housing and connectivity) (now Nerim again, as it was acquired recently) * Alionis (Orfeo's housing) Thanks a lot pals :-). == The MilkyPond Project == MP is an historical share of an IRC network between DC and RN when they both stopped working on the CoinNetwork project. They were willing to cooperate but with the important changes that occurred in their lives, only IRC was kept as a communication link. With time going, DC began recreating services, with the main server Orfeo being kindly sponsored by Nerim, which was used by RN and later by other associations or individuals. Nothing much is done in the name of MP until 2007, besides adding a Jabber server. In early 2007, RN hired a server, Lechat (Dédibox), and was willing to participate more in the share. At the end of the year, T1R joined to help improving the IRC Network. In September 2007, RN was not able to provide services anymore, as it was too much of a burden. Nevertheless, it is still sponsoring the ''milkypond.org'' domain since then. == Key Dates == * 2000-05-22: DuckCorp is created * 2003-04-25: IANA PEN 16829 * 2003-07-09: RtpNet is created * ~2003-10-20: RSA key exchanged between DC and RN (date is from the exif info, but Photoshop is in the way) * 2004-06-12: MilkyPond is created (after DC and RN stopped working on the CoinNetwork project) * 2005-04/05: Orfeo RAM upgraded (512Mo->1.5Go) (blocked to ~800Mo [[Media:Orfeo.duckcorp.org-memory-day.png|until highmem in kernel]]) * 2005-11-17: the users' mailing-list started * 2005-11: major mail system improvements (SMTP auth, improved antispam, webdesk) * 2005-12-08: Orfeo moved from the Nerim's Ivry datacenter to the Nerim suite in the LDCOM Courbevoie datacenter * 2006-01 to 2006-06: Orfeo problems due to an [http://xfs.org/index.php/XFS_FAQ#Q:_What_is_the_issue_with_directory_corruption_in_Linux_2.6.17.3F XFS bug] * 2007-04: IPv6 Ready * 2007-07: Tōshirō bought and being prepared * 2007-08-08: Nerim's boss shutdown Orfeo violently; quickly repaired and setup behind a mere ADSL (helped by Nerim friends), but BLACKOUT for most services * 2007-08-13: Tōshirō installed in the Sivit suite of the Redbus datacenter, services progressively back online * 2007-09: LDAP infrastructure (again) * 2007-12: Orfeo-NG bough and installed in Alionis suite in EQX (Equinix) datacenter * 2007-12: T1R enters MilkyPond (for the IRC network) * 2008-07: VCS rework, Portal (Restricted Access Helper), Projects Manager (Redmine) * 2009-03: Banya bot (mail gateway for DNS modification, part of the CyborgHood project) * 2009-09: Orfeo moved to [http://www.alionis.net/infra/VBO.html Alionis VBO datacenter] * 2010-03: Thorfinn acquired (Nerim VDS) * 2010-04-24: stratum 2 NTP server [http://support.ntp.org/bin/view/Servers/NtpDuckCorpOrg publicly advertised] and in the [http://www.pool.ntp.org/user/DuckCorp pool] == Admins == * Arnau [~2004-12 to now] * Duck [begining to now] (leader) * Finger [2006-07-05 to 2008-02-04] (assistant) * Mmenal [~2004-12 to ~2006-07] * Rtp [2003-10 to 2007-07-15] == Evolution == No real traces were kept, so old numbers are mere rough guess. * 2000 -> 2004 ** more than 60 users served in the [[Media:Coinnetwork resal 2001-2002.png|CoinNetwork LAN]], nearly no external services besides a basic website and IRC ** services targeted for the CoinNetwork LAN * 2004 -> 2007 ** a few users (probably around 20) and 2 entities (RtpNet and [http://www.hurdfr.org/ HurdFr]) hosted ** more Internet-oriented services (complete mail software suite, MLs, Web hosting, DBs, RCS, ...) * 2007 -> 2010 ** more users (nearly 70 users in 2010, a few not very active) and 2 more entity hosted ([http://thebrain.lautre.net/ TheBrain] and [http://www.andesi.org/ Andesi]) ** more services (Jabber, user-friendly antispam, LDAP, IPv6, ...) == Photos == Look at the [http://photos.duckcorp.org/v/duckcorp/ gallery]. 94f9ebb918775e592fab0af7ad559f1fcf1618db 57 51 2010-04-26T13:14:19Z Duck 2 /* Key Dates */ wikitext text/x-wiki == The DuckCorp Story == DuckCorp was born in 2000, from Duck's will to construct something more personal out of the CoinNetwork student house's LAN. At that time, it was merely a simple website, advertising a few personal projects. Later, several machines, gathered with various parts from people willing to dispose of them, used the 'duckcorp.org' domain name and provided services for CoinNetwork; this was the begining of the DC's sponsoring mission. Duck then met Rtp, and they began sharing about system administration topics. As they were willing to administrate CoinNetwork better, they began working on the infrastructure and tools together. Rtp created RtpNet, and received the magical SSH key to be a full DC administrator (so do Duck for Rtpnet indeed). They developed a software prototype aimed at managing the most important services of a distributed web of servers (LMS, LDAP Management System), which helped reducing the daily burden of CoinNetwork's administration a lot. After a while working hand in hand, they both found a job and moved to a new home, still helping each other when possible. Currently, RtpNet and DuckCorp have different goals, and follow their own path. On the way, DC found friendly sponsors (in order of appearance): * Nerim (first Orfeo's housing, IPv6 block, indirect sponsor via Hivane) * Hivane (global connectivity, secondary NS and MX) * Sivit (special accomodations for Toushirou's housing and connectivity) (now Nerim again, as it was acquired recently) * Alionis (Orfeo's housing) Thanks a lot pals :-). == The MilkyPond Project == MP is an historical share of an IRC network between DC and RN when they both stopped working on the CoinNetwork project. They were willing to cooperate but with the important changes that occurred in their lives, only IRC was kept as a communication link. With time going, DC began recreating services, with the main server Orfeo being kindly sponsored by Nerim, which was used by RN and later by other associations or individuals. Nothing much is done in the name of MP until 2007, besides adding a Jabber server. In early 2007, RN hired a server, Lechat (Dédibox), and was willing to participate more in the share. At the end of the year, T1R joined to help improving the IRC Network. In September 2007, RN was not able to provide services anymore, as it was too much of a burden. Nevertheless, it is still sponsoring the ''milkypond.org'' domain since then. == Key Dates == * 2000-05-22: DuckCorp is created * 2003-04-25: IANA PEN 16829 * 2003-07-09: RtpNet is created * ~2003-10-20: RSA key exchanged between DC and RN (date is from the exif info, but Photoshop is in the way) * 2004-06-12: MilkyPond is created (after DC and RN stopped working on the CoinNetwork project) * 2005-04/05: Orfeo RAM upgraded (512Mo->1.5Go) (blocked to ~800Mo [[Media:Orfeo.duckcorp.org-memory-day.png|until highmem in kernel]]) * 2005-11-17: the users' mailing-list started * 2005-11: major mail system improvements (SMTP auth, improved antispam, webdesk) * 2005-12-08: Orfeo moved from the Nerim's Ivry datacenter to the Nerim suite in the LDCOM Courbevoie datacenter * 2006-01 to 2006-06: Orfeo problems due to an [http://xfs.org/index.php/XFS_FAQ#Q:_What_is_the_issue_with_directory_corruption_in_Linux_2.6.17.3F XFS bug] * 2007-04: IPv6 Ready * 2007-07: Tōshirō bought and being prepared * 2007-08-08: Nerim's boss shutdown Orfeo violently; quickly repaired and setup behind a mere ADSL (helped by Nerim friends), but BLACKOUT for most services * 2007-08-13: Tōshirō installed in the Sivit suite of the Redbus datacenter, services progressively back online * 2007-09: LDAP infrastructure (again) * 2007-12: Orfeo-NG bough and installed in Alionis suite in EQX (Equinix) datacenter * 2007-12: T1R enters MilkyPond (for the IRC network) * 2008-07: VCS rework, Portal (Restricted Access Helper), Projects Manager (Redmine) * 2009-03: Banya bot (mail gateway for DNS modification, part of the CyborgHood project) * 2009-09: Orfeo moved to [http://www.alionis.net/infra/VBO.html Alionis VBO datacenter] * 2010-03: Thorfinn acquired (Nerim VDS) * 2010-04-24: stratum 2 NTP server [http://support.ntp.org/bin/view/Servers/NtpDuckCorpOrg publicly advertised] and in the [http://www.pool.ntp.org/user/DuckCorp pool] To come: * 2010-05-22: 10th Anniversary !!! * 2010-05-29: 10th Anniversary party with users/sponsors/friends == Admins == * Arnau [~2004-12 to now] * Duck [begining to now] (leader) * Finger [2006-07-05 to 2008-02-04] (assistant) * Mmenal [~2004-12 to ~2006-07] * Rtp [2003-10 to 2007-07-15] == Evolution == No real traces were kept, so old numbers are mere rough guess. * 2000 -> 2004 ** more than 60 users served in the [[Media:Coinnetwork resal 2001-2002.png|CoinNetwork LAN]], nearly no external services besides a basic website and IRC ** services targeted for the CoinNetwork LAN * 2004 -> 2007 ** a few users (probably around 20) and 2 entities (RtpNet and [http://www.hurdfr.org/ HurdFr]) hosted ** more Internet-oriented services (complete mail software suite, MLs, Web hosting, DBs, RCS, ...) * 2007 -> 2010 ** more users (nearly 70 users in 2010, a few not very active) and 2 more entity hosted ([http://thebrain.lautre.net/ TheBrain] and [http://www.andesi.org/ Andesi]) ** more services (Jabber, user-friendly antispam, LDAP, IPv6, ...) == Photos == Look at the [http://photos.duckcorp.org/v/duckcorp/ gallery]. 93feebbfb9321c531474fff8b0f76032afec0f2f 58 57 2010-04-27T19:52:21Z Duck 2 /* Key Dates */ wikitext text/x-wiki == The DuckCorp Story == DuckCorp was born in 2000, from Duck's will to construct something more personal out of the CoinNetwork student house's LAN. At that time, it was merely a simple website, advertising a few personal projects. Later, several machines, gathered with various parts from people willing to dispose of them, used the 'duckcorp.org' domain name and provided services for CoinNetwork; this was the begining of the DC's sponsoring mission. Duck then met Rtp, and they began sharing about system administration topics. As they were willing to administrate CoinNetwork better, they began working on the infrastructure and tools together. Rtp created RtpNet, and received the magical SSH key to be a full DC administrator (so do Duck for Rtpnet indeed). They developed a software prototype aimed at managing the most important services of a distributed web of servers (LMS, LDAP Management System), which helped reducing the daily burden of CoinNetwork's administration a lot. After a while working hand in hand, they both found a job and moved to a new home, still helping each other when possible. Currently, RtpNet and DuckCorp have different goals, and follow their own path. On the way, DC found friendly sponsors (in order of appearance): * Nerim (first Orfeo's housing, IPv6 block, indirect sponsor via Hivane) * Hivane (global connectivity, secondary NS and MX) * Sivit (special accomodations for Toushirou's housing and connectivity) (now Nerim again, as it was acquired recently) * Alionis (Orfeo's housing) Thanks a lot pals :-). == The MilkyPond Project == MP is an historical share of an IRC network between DC and RN when they both stopped working on the CoinNetwork project. They were willing to cooperate but with the important changes that occurred in their lives, only IRC was kept as a communication link. With time going, DC began recreating services, with the main server Orfeo being kindly sponsored by Nerim, which was used by RN and later by other associations or individuals. Nothing much is done in the name of MP until 2007, besides adding a Jabber server. In early 2007, RN hired a server, Lechat (Dédibox), and was willing to participate more in the share. At the end of the year, T1R joined to help improving the IRC Network. In September 2007, RN was not able to provide services anymore, as it was too much of a burden. Nevertheless, it is still sponsoring the ''milkypond.org'' domain since then. == Key Dates == * 2000-05-22: DuckCorp is created * 2003-04-25: IANA PEN 16829 * 2003-07-09: RtpNet is created * ~2003-10-20: RSA key exchanged between DC and RN (date is from the exif info, but Photoshop is in the way) * 2004-06-12: MilkyPond is created (after DC and RN stopped working on the CoinNetwork project) * 2005-04/05: Orfeo RAM upgraded (512Mo->1.5Go) (blocked to ~800Mo [[Media:Orfeo.duckcorp.org-memory-day.png|until highmem in kernel]]) * 2005-05: IPv6 Ready (using a tunnel) * 2005-11-17: the users' mailing-list started * 2005-11: major mail system improvements (SMTP auth, improved antispam, webdesk) * 2005-12-08: Orfeo moved from the Nerim's Ivry datacenter to the Nerim suite in the LDCOM Courbevoie datacenter * 2006-01 to 2006-06: Orfeo problems due to an [http://xfs.org/index.php/XFS_FAQ#Q:_What_is_the_issue_with_directory_corruption_in_Linux_2.6.17.3F XFS bug] * 2007-04: IPv6 Ready (native IPv6) * 2007-07: Tōshirō bought and being prepared * 2007-08-08: Nerim's boss shutdown Orfeo violently; quickly repaired and setup behind a mere ADSL (helped by Nerim friends), but BLACKOUT for most services * 2007-08-13: Tōshirō installed in the Sivit suite of the Redbus datacenter, services progressively back online * 2007-09: LDAP infrastructure (again) * 2007-12: Orfeo-NG bough and installed in Alionis suite in EQX (Equinix) datacenter * 2007-12: T1R enters MilkyPond (for the IRC network) * 2008-07: VCS rework, Portal (Restricted Access Helper), Projects Manager (Redmine) * 2009-03: Banya bot (mail gateway for DNS modification, part of the CyborgHood project) * 2009-09: Orfeo moved to [http://www.alionis.net/infra/VBO.html Alionis VBO datacenter] * 2010-03: Thorfinn acquired (Nerim VDS) * 2010-04-24: stratum 2 NTP server [http://support.ntp.org/bin/view/Servers/NtpDuckCorpOrg publicly advertised] and in the [http://www.pool.ntp.org/user/DuckCorp pool] To come: * 2010-05-22: 10th Anniversary !!! * 2010-05-29: 10th Anniversary party with users/sponsors/friends == Admins == * Arnau [~2004-12 to now] * Duck [begining to now] (leader) * Finger [2006-07-05 to 2008-02-04] (assistant) * Mmenal [~2004-12 to ~2006-07] * Rtp [2003-10 to 2007-07-15] == Evolution == No real traces were kept, so old numbers are mere rough guess. * 2000 -> 2004 ** more than 60 users served in the [[Media:Coinnetwork resal 2001-2002.png|CoinNetwork LAN]], nearly no external services besides a basic website and IRC ** services targeted for the CoinNetwork LAN * 2004 -> 2007 ** a few users (probably around 20) and 2 entities (RtpNet and [http://www.hurdfr.org/ HurdFr]) hosted ** more Internet-oriented services (complete mail software suite, MLs, Web hosting, DBs, RCS, ...) * 2007 -> 2010 ** more users (nearly 70 users in 2010, a few not very active) and 2 more entity hosted ([http://thebrain.lautre.net/ TheBrain] and [http://www.andesi.org/ Andesi]) ** more services (Jabber, user-friendly antispam, LDAP, IPv6, ...) == Photos == Look at the [http://photos.duckcorp.org/v/duckcorp/ gallery]. b744cae4054535cf2b778bd0377621c27ced8719 59 58 2010-05-01T01:25:26Z Duck 2 /* Admins */ wikitext text/x-wiki == The DuckCorp Story == DuckCorp was born in 2000, from Duck's will to construct something more personal out of the CoinNetwork student house's LAN. At that time, it was merely a simple website, advertising a few personal projects. Later, several machines, gathered with various parts from people willing to dispose of them, used the 'duckcorp.org' domain name and provided services for CoinNetwork; this was the begining of the DC's sponsoring mission. Duck then met Rtp, and they began sharing about system administration topics. As they were willing to administrate CoinNetwork better, they began working on the infrastructure and tools together. Rtp created RtpNet, and received the magical SSH key to be a full DC administrator (so do Duck for Rtpnet indeed). They developed a software prototype aimed at managing the most important services of a distributed web of servers (LMS, LDAP Management System), which helped reducing the daily burden of CoinNetwork's administration a lot. After a while working hand in hand, they both found a job and moved to a new home, still helping each other when possible. Currently, RtpNet and DuckCorp have different goals, and follow their own path. On the way, DC found friendly sponsors (in order of appearance): * Nerim (first Orfeo's housing, IPv6 block, indirect sponsor via Hivane) * Hivane (global connectivity, secondary NS and MX) * Sivit (special accomodations for Toushirou's housing and connectivity) (now Nerim again, as it was acquired recently) * Alionis (Orfeo's housing) Thanks a lot pals :-). == The MilkyPond Project == MP is an historical share of an IRC network between DC and RN when they both stopped working on the CoinNetwork project. They were willing to cooperate but with the important changes that occurred in their lives, only IRC was kept as a communication link. With time going, DC began recreating services, with the main server Orfeo being kindly sponsored by Nerim, which was used by RN and later by other associations or individuals. Nothing much is done in the name of MP until 2007, besides adding a Jabber server. In early 2007, RN hired a server, Lechat (Dédibox), and was willing to participate more in the share. At the end of the year, T1R joined to help improving the IRC Network. In September 2007, RN was not able to provide services anymore, as it was too much of a burden. Nevertheless, it is still sponsoring the ''milkypond.org'' domain since then. == Key Dates == * 2000-05-22: DuckCorp is created * 2003-04-25: IANA PEN 16829 * 2003-07-09: RtpNet is created * ~2003-10-20: RSA key exchanged between DC and RN (date is from the exif info, but Photoshop is in the way) * 2004-06-12: MilkyPond is created (after DC and RN stopped working on the CoinNetwork project) * 2005-04/05: Orfeo RAM upgraded (512Mo->1.5Go) (blocked to ~800Mo [[Media:Orfeo.duckcorp.org-memory-day.png|until highmem in kernel]]) * 2005-05: IPv6 Ready (using a tunnel) * 2005-11-17: the users' mailing-list started * 2005-11: major mail system improvements (SMTP auth, improved antispam, webdesk) * 2005-12-08: Orfeo moved from the Nerim's Ivry datacenter to the Nerim suite in the LDCOM Courbevoie datacenter * 2006-01 to 2006-06: Orfeo problems due to an [http://xfs.org/index.php/XFS_FAQ#Q:_What_is_the_issue_with_directory_corruption_in_Linux_2.6.17.3F XFS bug] * 2007-04: IPv6 Ready (native IPv6) * 2007-07: Tōshirō bought and being prepared * 2007-08-08: Nerim's boss shutdown Orfeo violently; quickly repaired and setup behind a mere ADSL (helped by Nerim friends), but BLACKOUT for most services * 2007-08-13: Tōshirō installed in the Sivit suite of the Redbus datacenter, services progressively back online * 2007-09: LDAP infrastructure (again) * 2007-12: Orfeo-NG bough and installed in Alionis suite in EQX (Equinix) datacenter * 2007-12: T1R enters MilkyPond (for the IRC network) * 2008-07: VCS rework, Portal (Restricted Access Helper), Projects Manager (Redmine) * 2009-03: Banya bot (mail gateway for DNS modification, part of the CyborgHood project) * 2009-09: Orfeo moved to [http://www.alionis.net/infra/VBO.html Alionis VBO datacenter] * 2010-03: Thorfinn acquired (Nerim VDS) * 2010-04-24: stratum 2 NTP server [http://support.ntp.org/bin/view/Servers/NtpDuckCorpOrg publicly advertised] and in the [http://www.pool.ntp.org/user/DuckCorp pool] To come: * 2010-05-22: 10th Anniversary !!! * 2010-05-29: 10th Anniversary party with users/sponsors/friends == Admins == * Arnau [~2004-12 to now] (fallback admin since 2010-04-27) * Duck [begining to now] (leader) * Finger [2006-07-05 to 2008-02-04] (assistant) * Mmenal [~2004-12 to ~2006-07] * Rtp [2003-10 to 2007-07-15] == Evolution == No real traces were kept, so old numbers are mere rough guess. * 2000 -> 2004 ** more than 60 users served in the [[Media:Coinnetwork resal 2001-2002.png|CoinNetwork LAN]], nearly no external services besides a basic website and IRC ** services targeted for the CoinNetwork LAN * 2004 -> 2007 ** a few users (probably around 20) and 2 entities (RtpNet and [http://www.hurdfr.org/ HurdFr]) hosted ** more Internet-oriented services (complete mail software suite, MLs, Web hosting, DBs, RCS, ...) * 2007 -> 2010 ** more users (nearly 70 users in 2010, a few not very active) and 2 more entity hosted ([http://thebrain.lautre.net/ TheBrain] and [http://www.andesi.org/ Andesi]) ** more services (Jabber, user-friendly antispam, LDAP, IPv6, ...) == Photos == Look at the [http://photos.duckcorp.org/v/duckcorp/ gallery]. d63d679d1925a0a4ed6a808897d7b4979b122d88 0 2 52 22 2010-04-25T21:49:17Z Duck 2 wikitext text/x-wiki {{Robelbox|title=Introduction|theme={{{theme|1}}}}} {{Padbox}} Coin ! * [[A bit of History]] {{Padbox/close}} {{Robelbox/close}} 8368d68b04ab99a5e7edda7db33277d473e9599c 54 52 2010-04-25T22:00:39Z Duck 2 wikitext text/x-wiki {{Robelbox|title=Introduction|theme={{{theme|1}}}}} {{Padbox}} Coin ! * [[DcArchitecture|Architecture]] * [[A bit of History]] {{Padbox/close}} {{Robelbox/close}} 761d629b55badc284b0d3af0b2f6c6684f0517b2 55 54 2010-04-25T22:08:54Z Duck 2 wikitext text/x-wiki {{Robelbox|title=Introduction|theme={{{theme|1}}}}} {{Padbox}} Coin ! DuckCorp is a non-profit Magical Organization providing services to individuals and associations, for not-for-profit usage. Here are bits of information about us: * [[DcArchitecture|Architecture]] * [[A bit of History]] \_o< {{Padbox/close}} {{Robelbox/close}} 29a3e5d72bfcaf08079a57b9e1b8ed475bb2d83f 56 55 2010-04-25T22:09:06Z Duck 2 Protected "[[Main Page/Introduction]]" ([edit=sysop] (indefinite) [move=sysop] (indefinite)) wikitext text/x-wiki {{Robelbox|title=Introduction|theme={{{theme|1}}}}} {{Padbox}} Coin ! DuckCorp is a non-profit Magical Organization providing services to individuals and associations, for not-for-profit usage. Here are bits of information about us: * [[DcArchitecture|Architecture]] * [[A bit of History]] \_o< {{Padbox/close}} {{Robelbox/close}} 29a3e5d72bfcaf08079a57b9e1b8ed475bb2d83f 80 56 2010-05-17T18:49:40Z Duck 2 wikitext text/x-wiki {{Robelbox|title=Introduction|theme={{{theme|1}}}}} {{Padbox}} Coin ! [https://www.duckcorp.org/ DuckCorp] is a non-profit Magical Organization providing services to individuals and associations, for not-for-profit usage. See more details about our mission and how to contact us in the [https://www.duckcorp.org/ institutional site]. Here are bits of information about us: * [[DcArchitecture|Architecture]] * [[A bit of History]] \_o< {{Padbox/close}} {{Robelbox/close}} 21565c7598b110a33c58ca23398a7768b69013b6 90 80 2010-05-17T19:00:52Z Duck 2 wikitext text/x-wiki {{Robelbox|title=Introduction|theme={{{theme|1}}}}} {{Padbox}} Coin ! [https://www.duckcorp.org/ DuckCorp] is a non-profit Magical Organization providing services to individuals and associations, for not-for-profit usage. See more details about our mission and how to contact us in the [https://www.duckcorp.org/ institutional site]. \_o< {{Padbox/close}} {{Robelbox/close}} 82b70d88c965ba734cd6abcfd5ea36a999a40b48 0 31 53 2010-04-25T21:59:53Z Duck 2 Created page with '<fdp_graph> graph DcMap { label = "DuckCorp Architecture"; fontsize = 14; overlap = false; splines = true; edge [fontsize=10.0]; labelloc = "t"; subgraph cluster_h…' wikitext text/x-wiki <fdp_graph> graph DcMap { label = "DuckCorp Architecture"; fontsize = 14; overlap = false; splines = true; edge [fontsize=10.0]; labelloc = "t"; subgraph cluster_hq { label = "DuckCorp HQ (DuckLand)"; color = green; labeljust = "l"; elwing [label="Elwing", URL="DcArchitecture/Elwing"]; daneel [label="Daneel", URL="DcArchitecture/Daneel"]; earendil [label="Eärendil", URL="DcArchitecture/Eärendil"]; modem_dc [label="ADSL Modem\n(Linksys ADSL2MUE)", shape=box]; sw_dc [label="Switch", shape=box]; sw_dc -- {elwing earendil daneel}; elwing -- {modem_dc}; subgraph cluster_hurdfr { label = "HurdFr (DuckLand part)"; color = darkviolet; labeljust = "l"; amroth [label="Amroth", URL="DcArchitecture/Amroth"]; } amroth -- sw_dc; } internet [label="Internet", shape=tripleoctagon]; modem_dc -- internet [label="Nerim / Hivane\nADSL", style=dashed]; subgraph cluster_sivit { label = "Sivit Suite\n(TelecityGroup Datacenter)"; color = blue; labeljust = "l"; toushirou [label="Tōshirō", URL="DcArchitecture/Tōshirō"]; } toushirou -- internet [label="Sivit / Hivane\nTransit", style=dashed]; subgraph cluster_alionis { label = "Alionis Suite\n(Villebon Datacenter)"; URL = "http://maps.google.com/maps/ms?ie=UTF8&hl=en&msa=0&msid=105368272885926046620.0004600d15bf1a76aa1a9&t=h&z=15"; color = black; labeljust = "l"; orfeo [label="Orfeo", URL="DcArchitecture/Orfeo"]; } orfeo -- internet [label="Hivane\nTransit", style=dashed]; subgraph cluster_nerim_vds { label = "Nerim VDS"; URL = "http://root.nerim.net/"; color = orange; labeljust = "l"; thorfinn [label="Thorfinn", URL="DcArchitecture/Thorfinn"]; } thorfinn -- internet [label="Nerim\nTransit", style=dashed]; } <fdp_graph> b0802eb9f65b7656258af0ef5edc327b548711ca 0 32 60 2010-05-15T11:53:51Z Duck 2 Created page with 'Let's be transparent about money too. == Regular Expenses == {{todo}} == Exceptional Expenses == === Improvement Expenses === {{todo}} === Failure Expenses === {{todo}}' wikitext text/x-wiki Let's be transparent about money too. == Regular Expenses == {{todo}} == Exceptional Expenses == === Improvement Expenses === {{todo}} === Failure Expenses === {{todo}} 5699f2a9823e4b1adf68d8bf6ed156e23dc4b8c0 63 60 2010-05-15T12:38:28Z Duck 2 /* Regular Expenses */ wikitext text/x-wiki Let's be transparent about money too. == Regular Expenses == {{todo}} {| class="wikitable" style="text-align: center; width: 100%;" ! Object !! Amount !! Sponsor |- | DuckCorp DNS domain || ~15€/year || Duck |} == Exceptional Expenses == === Improvement Expenses === {{todo}} === Failure Expenses === {{todo}} 04fd74c3002190dc1cec0cc5b6a8fa16cb816cf4 65 63 2010-05-15T12:50:52Z Duck 2 /* Regular Expenses */ wikitext text/x-wiki Let's be transparent about money too. == Regular Expenses == This does not account for external sponsorship, but contributions by members. {| class="wikitable" style="text-align: center; width: 100%;" ! Object !! Amount !! Sponsor !! Comment |- | DuckCorp DNS domain || ~15€/year || Duck |- | MilkyPond DNS domain || ~15€/year || Rtp |- | Toushirou's housing || 41.56€/month || Duck || collocation with Yok (considering network switch and APC powerswitch rack space) |} Note: this does not take into account the ADSL line used by Elwing and Daneel, coupled in the same offer providing the VM Thorfinn, as it is used privately. == Exceptional Expenses == === Improvement Expenses === {{todo}} === Failure Expenses === {{todo}} 79e31ce06069c4c2e170f156a585f357c9de0a21 66 65 2010-05-15T12:51:08Z Duck 2 /* Regular Expenses */ wikitext text/x-wiki Let's be transparent about money too. == Regular Expenses == This does not account for external sponsorship, but contributions by members. {| class="wikitable" style="text-align: center; width: 100%;" ! Object !! Amount !! Sponsor !! Comments |- | DuckCorp DNS domain || ~15€/year || Duck |- | MilkyPond DNS domain || ~15€/year || Rtp |- | Toushirou's housing || 41.56€/month || Duck || collocation with Yok (considering network switch and APC powerswitch rack space) |} Note: this does not take into account the ADSL line used by Elwing and Daneel, coupled in the same offer providing the VM Thorfinn, as it is used privately. == Exceptional Expenses == === Improvement Expenses === {{todo}} === Failure Expenses === {{todo}} 1c851464c074c65ff8fdb1a099dcc4a671442b92 69 66 2010-05-15T14:06:16Z Duck 2 /* Exceptional Expenses */ wikitext text/x-wiki Let's be transparent about money too. == Regular Expenses == This does not account for external sponsorship, but contributions by members. {| class="wikitable" style="text-align: center; width: 100%;" ! Object !! Amount !! Sponsor !! Comments |- | DuckCorp DNS domain || ~15€/year || Duck |- | MilkyPond DNS domain || ~15€/year || Rtp |- | Toushirou's housing || 41.56€/month || Duck || collocation with Yok (considering network switch and APC powerswitch rack space) |} Note: this does not take into account the ADSL line used by Elwing and Daneel, coupled in the same offer providing the VM Thorfinn, as it is used privately. == Exceptional Expenses == === Improvement Expenses === {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Object !! Amount !! Sponsor !! Comments |- | 2007-05 || new server (Toushirou) || 1709.08€ || Duck |} === Failure Expenses === {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Object !! Amount !! Sponsor !! Comments |- | 2006-01 || HD for Daneel (backup) || || AnonymousDonnor1 || replaced since then |} f0bd244192f801def2567cb9e7fd1f167b788df2 71 69 2010-05-15T14:40:37Z Duck 2 /* Failure Expenses */ wikitext text/x-wiki Let's be transparent about money too. == Regular Expenses == This does not account for external sponsorship, but contributions by members. {| class="wikitable" style="text-align: center; width: 100%;" ! Object !! Amount !! Sponsor !! Comments |- | DuckCorp DNS domain || ~15€/year || Duck |- | MilkyPond DNS domain || ~15€/year || Rtp |- | Toushirou's housing || 41.56€/month || Duck || collocation with Yok (considering network switch and APC powerswitch rack space) |} Note: this does not take into account the ADSL line used by Elwing and Daneel, coupled in the same offer providing the VM Thorfinn, as it is used privately. == Exceptional Expenses == === Improvement Expenses === {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Object !! Amount !! Sponsor !! Comments |- | 2007-05 || new server (Toushirou) || 1709.08€ || Duck |} === Failure Expenses === {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Object !! Amount !! Sponsor !! Comments |- | 2006-01 || 300GB HD for Daneel (backup) || || AnonymousDonnor1 || replaced since then |} e03b6ac4ca0e5738e8eb4a6beedef651a141690c 72 71 2010-05-15T15:48:39Z Duck 2 /* Exceptional Expenses */ wikitext text/x-wiki Let's be transparent about money too. == Regular Expenses == This does not account for external sponsorship, but contributions by members. {| class="wikitable" style="text-align: center; width: 100%;" ! Object !! Amount !! Sponsor !! Comments |- | DuckCorp DNS domain || ~15€/year || Duck |- | MilkyPond DNS domain || ~15€/year || Rtp |- | Toushirou's housing || 41.56€/month || Duck || collocation with Yok (considering network switch and APC powerswitch rack space) |} Note: this does not take into account the ADSL line used by Elwing and Daneel, coupled in the same offer providing the VM Thorfinn, as it is used privately. == Exceptional Expenses == === Improvement Expenses === {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Object !! Amount !! Sponsor !! Comments |- | 2007-05 || new server (Toushirou) || 1709.08€ || Duck |} {{todo}} finish === Failure Expenses === {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Object !! Amount !! Sponsor !! Comments |- | 2006-01 || 300GB HD for Daneel (backup) || || AnonymousDonnor1 || replaced since then |} {{todo}} finish fe8a15a714aac6ca212f34e8f3a925f7a7790f3f 73 72 2010-05-16T18:56:19Z Duck 2 /* Improvement Expenses */ wikitext text/x-wiki Let's be transparent about money too. == Regular Expenses == This does not account for external sponsorship, but contributions by members. {| class="wikitable" style="text-align: center; width: 100%;" ! Object !! Amount !! Sponsor !! Comments |- | DuckCorp DNS domain || ~15€/year || Duck |- | MilkyPond DNS domain || ~15€/year || Rtp |- | Toushirou's housing || 41.56€/month || Duck || collocation with Yok (considering network switch and APC powerswitch rack space) |} Note: this does not take into account the ADSL line used by Elwing and Daneel, coupled in the same offer providing the VM Thorfinn, as it is used privately. == Exceptional Expenses == === Improvement Expenses === {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Object !! Amount !! Sponsor !! Comments |- | 2007-10 || replacement server (Orfeo-NG) || 1210€ || Duck |- | 2007-05 || new server (Toushirou) || 1709.08€ || Duck |} {{todo}} finish === Failure Expenses === {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Object !! Amount !! Sponsor !! Comments |- | 2006-01 || 300GB HD for Daneel (backup) || || AnonymousDonnor1 || replaced since then |} {{todo}} finish c7bf26be220616abe49eb0b8a882cd0d1a75801e 74 73 2010-05-16T19:03:09Z Duck 2 /* Improvement Expenses */ wikitext text/x-wiki Let's be transparent about money too. == Regular Expenses == This does not account for external sponsorship, but contributions by members. {| class="wikitable" style="text-align: center; width: 100%;" ! Object !! Amount !! Sponsor !! Comments |- | DuckCorp DNS domain || ~15€/year || Duck |- | MilkyPond DNS domain || ~15€/year || Rtp |- | Toushirou's housing || 41.56€/month || Duck || collocation with Yok (considering network switch and APC powerswitch rack space) |} Note: this does not take into account the ADSL line used by Elwing and Daneel, coupled in the same offer providing the VM Thorfinn, as it is used privately. == Exceptional Expenses == === Improvement Expenses === {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Object !! Amount !! Sponsor !! Comments |- | 2007-10 || replacement server (Orfeo-NG) || 1210€ || Duck || Sun Fire X4100 |- | 2007-05 || new server (Toushirou) || 1709.08€ || Duck || Supermicro PDSMI+ / Core 2 Duo E6600 / 2GB PC5400 / 3ware 9550SX4LP |} {{todo}} finish === Failure Expenses === {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Object !! Amount !! Sponsor !! Comments |- | 2006-01 || 300GB HD for Daneel (backup) || || AnonymousDonnor1 || replaced since then |} {{todo}} finish 4f0921996ddf18c52faeacdb6e1f8e9284ba6916 75 74 2010-05-17T18:38:22Z Duck 2 Protected "[[DcExpenses]]" ([edit=sysop] (indefinite) [move=sysop] (indefinite)) wikitext text/x-wiki Let's be transparent about money too. == Regular Expenses == This does not account for external sponsorship, but contributions by members. {| class="wikitable" style="text-align: center; width: 100%;" ! Object !! Amount !! Sponsor !! Comments |- | DuckCorp DNS domain || ~15€/year || Duck |- | MilkyPond DNS domain || ~15€/year || Rtp |- | Toushirou's housing || 41.56€/month || Duck || collocation with Yok (considering network switch and APC powerswitch rack space) |} Note: this does not take into account the ADSL line used by Elwing and Daneel, coupled in the same offer providing the VM Thorfinn, as it is used privately. == Exceptional Expenses == === Improvement Expenses === {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Object !! Amount !! Sponsor !! Comments |- | 2007-10 || replacement server (Orfeo-NG) || 1210€ || Duck || Sun Fire X4100 |- | 2007-05 || new server (Toushirou) || 1709.08€ || Duck || Supermicro PDSMI+ / Core 2 Duo E6600 / 2GB PC5400 / 3ware 9550SX4LP |} {{todo}} finish === Failure Expenses === {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Object !! Amount !! Sponsor !! Comments |- | 2006-01 || 300GB HD for Daneel (backup) || || AnonymousDonnor1 || replaced since then |} {{todo}} finish 4f0921996ddf18c52faeacdb6e1f8e9284ba6916 78 75 2010-05-17T18:42:18Z Duck 2 wikitext text/x-wiki Let's be transparent about money too. Pure financial contributions are not listed here, but in the [[DcDonation|donation page]]. == Regular Expenses == This does not account for external sponsorship, but contributions by members. {| class="wikitable" style="text-align: center; width: 100%;" ! Object !! Amount !! Sponsor !! Comments |- | DuckCorp DNS domain || ~15€/year || Duck |- | MilkyPond DNS domain || ~15€/year || Rtp |- | Toushirou's housing || 41.56€/month || Duck || collocation with Yok (considering network switch and APC powerswitch rack space) |} Note: this does not take into account the ADSL line used by Elwing and Daneel, coupled in the same offer providing the VM Thorfinn, as it is used privately. == Exceptional Expenses == === Improvement Expenses === {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Object !! Amount !! Sponsor !! Comments |- | 2007-10 || replacement server (Orfeo-NG) || 1210€ || Duck || Sun Fire X4100 |- | 2007-05 || new server (Toushirou) || 1709.08€ || Duck || Supermicro PDSMI+ / Core 2 Duo E6600 / 2GB PC5400 / 3ware 9550SX4LP |} {{todo}} finish === Failure Expenses === {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Object !! Amount !! Sponsor !! Comments |- | 2006-01 || 300GB HD for Daneel (backup) || || AnonymousDonnor1 || replaced since then |} {{todo}} finish da9c957724ab82640ff9f44d72a3d0f62332b38e 92 78 2010-05-17T19:09:01Z Duck 2 /* Improvement Expenses */ wikitext text/x-wiki Let's be transparent about money too. Pure financial contributions are not listed here, but in the [[DcDonation|donation page]]. == Regular Expenses == This does not account for external sponsorship, but contributions by members. {| class="wikitable" style="text-align: center; width: 100%;" ! Object !! Amount !! Sponsor !! Comments |- | DuckCorp DNS domain || ~15€/year || Duck |- | MilkyPond DNS domain || ~15€/year || Rtp |- | Toushirou's housing || 41.56€/month || Duck || collocation with Yok (considering network switch and APC powerswitch rack space) |} Note: this does not take into account the ADSL line used by Elwing and Daneel, coupled in the same offer providing the VM Thorfinn, as it is used privately. == Exceptional Expenses == === Improvement Expenses === {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Object !! Amount !! Sponsor !! Comments |- | 2007-10 || replacement server (Orfeo-NG) || 1210€ || Duck || Sun Fire X4100 |- | 2007-05 || new server (Toushirou) || 1709.08€ || Duck || Supermicro PDSMI+ / Core 2 Duo E6600 / 2GB PC5400 / 3ware 9550SX4LP / 4x HD SATA II 250GB |} {{todo}} finish === Failure Expenses === {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Object !! Amount !! Sponsor !! Comments |- | 2006-01 || 300GB HD for Daneel (backup) || || AnonymousDonnor1 || replaced since then |} {{todo}} finish eb6541bcc5eed35b4a82472dee988951b74a8194 93 92 2010-05-22T21:38:00Z Duck 2 /* Improvement Expenses */ wikitext text/x-wiki Let's be transparent about money too. Pure financial contributions are not listed here, but in the [[DcDonation|donation page]]. == Regular Expenses == This does not account for external sponsorship, but contributions by members. {| class="wikitable" style="text-align: center; width: 100%;" ! Object !! Amount !! Sponsor !! Comments |- | DuckCorp DNS domain || ~15€/year || Duck |- | MilkyPond DNS domain || ~15€/year || Rtp |- | Toushirou's housing || 41.56€/month || Duck || collocation with Yok (considering network switch and APC powerswitch rack space) |} Note: this does not take into account the ADSL line used by Elwing and Daneel, coupled in the same offer providing the VM Thorfinn, as it is used privately. == Exceptional Expenses == === Improvement Expenses === {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Object !! Amount !! Sponsor !! Comments |- | 2010-05-22 || more memory for Toushirou (2*2GB) || 105€ || Duck || PC2-5300/5400 2*2GB memory in a correct brand could not be found, so we had to take PC2-6400 instead |- | 2007-10 || replacement server (Orfeo-NG) || 1210€ || Duck || Sun Fire X4100 |- | 2007-05 || new server (Toushirou) || 1709.08€ || Duck || Supermicro PDSMI+ / Core 2 Duo E6600 / 2GB PC5400 / 3ware 9550SX4LP / 4x HD SATA II 250GB |} {{todo}} finish === Failure Expenses === {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Object !! Amount !! Sponsor !! Comments |- | 2006-01 || 300GB HD for Daneel (backup) || || AnonymousDonnor1 || replaced since then |} {{todo}} finish fe8edc6c1cebc1183cec50e083c33d1ec8f9bd0c 94 93 2010-05-22T21:42:01Z Duck 2 /* Exceptional Expenses */ wikitext text/x-wiki Let's be transparent about money too. Pure financial contributions are not listed here, but in the [[DcDonation|donation page]]. == Regular Expenses == This does not account for external sponsorship, but contributions by members. {| class="wikitable" style="text-align: center; width: 100%;" ! Object !! Amount !! Sponsor !! Comments |- | DuckCorp DNS domain || ~15€/year || Duck |- | MilkyPond DNS domain || ~15€/year || Rtp |- | Toushirou's housing || 41.56€/month || Duck || collocation with Yok (considering network switch and APC powerswitch rack space) |} Note: this does not take into account the ADSL line used by Elwing and Daneel, coupled in the same offer providing the VM Thorfinn, as it is used privately. == Exceptional Expenses == Note: this does not take into account expenses before 2007 because most historical data were lost. === Improvement Expenses === {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Object !! Amount !! Sponsor !! Comments |- | 2010-05-22 || more memory for Toushirou (2*2GB) || 105€ || Duck || PC2-5300/5400 2*2GB memory in a correct brand could not be found, so we had to take PC2-6400 instead |- | 2007-10 || replacement server (Orfeo-NG) || 1210€ || Duck || Sun Fire X4100 |- | 2007-05 || new server (Toushirou) || 1709.08€ || Duck || Supermicro PDSMI+ / Core 2 Duo E6600 / 2GB PC5400 / 3ware 9550SX4LP / 4x HD SATA II 250GB |} {{todo}} finish === Failure Expenses === {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Object !! Amount !! Sponsor !! Comments |- | 2006-01 || 300GB HD for Daneel (backup) || || AnonymousDonnor1 || replaced since then |} {{todo}} finish f09a964c19d68d36ae967678b8bab2aeb60f3ca8 95 94 2010-05-22T21:42:38Z Duck 2 /* Regular Expenses */ wikitext text/x-wiki Let's be transparent about money too. Pure financial contributions are not listed here, but in the [[DcDonation|donation page]]. == Regular Expenses == This does not account for external sponsorship, but contributions by members. {| class="wikitable" style="text-align: center; width: 100%;" ! Object !! Amount !! Sponsor !! Comments |- | DuckCorp DNS domain || ~15€/year || Duck |- | MilkyPond DNS domain || ~15€/year || Rtp |- | Toushirou's housing || 41.56€/month || Duck || collocation with Yok (considering network switch and APC powerswitch shared rack space) |} Note: this does not take into account the ADSL line used by Elwing and Daneel, coupled in the same offer providing the VM Thorfinn, as it is used privately. == Exceptional Expenses == Note: this does not take into account expenses before 2007 because most historical data were lost. === Improvement Expenses === {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Object !! Amount !! Sponsor !! Comments |- | 2010-05-22 || more memory for Toushirou (2*2GB) || 105€ || Duck || PC2-5300/5400 2*2GB memory in a correct brand could not be found, so we had to take PC2-6400 instead |- | 2007-10 || replacement server (Orfeo-NG) || 1210€ || Duck || Sun Fire X4100 |- | 2007-05 || new server (Toushirou) || 1709.08€ || Duck || Supermicro PDSMI+ / Core 2 Duo E6600 / 2GB PC5400 / 3ware 9550SX4LP / 4x HD SATA II 250GB |} {{todo}} finish === Failure Expenses === {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Object !! Amount !! Sponsor !! Comments |- | 2006-01 || 300GB HD for Daneel (backup) || || AnonymousDonnor1 || replaced since then |} {{todo}} finish f0be37d9337fa909f1782b61561bbde9faef15f2 96 95 2010-05-22T21:43:18Z Duck 2 /* Exceptional Expenses */ wikitext text/x-wiki Let's be transparent about money too. Pure financial contributions are not listed here, but in the [[DcDonation|donation page]]. == Regular Expenses == This does not account for external sponsorship, but contributions by members. {| class="wikitable" style="text-align: center; width: 100%;" ! Object !! Amount !! Sponsor !! Comments |- | DuckCorp DNS domain || ~15€/year || Duck |- | MilkyPond DNS domain || ~15€/year || Rtp |- | Toushirou's housing || 41.56€/month || Duck || collocation with Yok (considering network switch and APC powerswitch shared rack space) |} Note: this does not take into account the ADSL line used by Elwing and Daneel, coupled in the same offer providing the VM Thorfinn, as it is used privately. == Exceptional Expenses == Note: this does not take into account expenses before 2006 because most historical data were lost. === Improvement Expenses === {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Object !! Amount !! Sponsor !! Comments |- | 2010-05-22 || more memory for Toushirou (2*2GB) || 105€ || Duck || PC2-5300/5400 2*2GB memory in a correct brand could not be found, so we had to take PC2-6400 instead |- | 2007-10 || replacement server (Orfeo-NG) || 1210€ || Duck || Sun Fire X4100 |- | 2007-05 || new server (Toushirou) || 1709.08€ || Duck || Supermicro PDSMI+ / Core 2 Duo E6600 / 2GB PC5400 / 3ware 9550SX4LP / 4x HD SATA II 250GB |} {{todo}} finish === Failure Expenses === {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Object !! Amount !! Sponsor !! Comments |- | 2006-01 || 300GB HD for Daneel (backup) || || AnonymousDonnor1 || replaced since then |} {{todo}} finish e5f49f91847ebbe4493158ea072f409bbb84c36f 97 96 2010-05-22T21:44:27Z Duck 2 /* Improvement Expenses */ wikitext text/x-wiki Let's be transparent about money too. Pure financial contributions are not listed here, but in the [[DcDonation|donation page]]. == Regular Expenses == This does not account for external sponsorship, but contributions by members. {| class="wikitable" style="text-align: center; width: 100%;" ! Object !! Amount !! Sponsor !! Comments |- | DuckCorp DNS domain || ~15€/year || Duck |- | MilkyPond DNS domain || ~15€/year || Rtp |- | Toushirou's housing || 41.56€/month || Duck || collocation with Yok (considering network switch and APC powerswitch shared rack space) |} Note: this does not take into account the ADSL line used by Elwing and Daneel, coupled in the same offer providing the VM Thorfinn, as it is used privately. == Exceptional Expenses == Note: this does not take into account expenses before 2006 because most historical data were lost. === Improvement Expenses === {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Object !! Amount !! Sponsor !! Comments |- | 2010-05-22 || more memory for Toushirou (2*2GB) || 105€ || Duck || PC2-5300/5400 2*2GB memory in a correct brand could not be found anymore, so we had to take PC2-6400 instead |- | 2007-10 || replacement server (Orfeo-NG) || 1210€ || Duck || Sun Fire X4100 |- | 2007-05 || new server (Toushirou) || 1709.08€ || Duck || Supermicro PDSMI+ / Core 2 Duo E6600 / 2GB PC5400 / 3ware 9550SX4LP / 4x HD SATA II 250GB |} {{todo}} finish === Failure Expenses === {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Object !! Amount !! Sponsor !! Comments |- | 2006-01 || 300GB HD for Daneel (backup) || || AnonymousDonnor1 || replaced since then |} {{todo}} finish 01aa82e3562ad9d89f3528c1bf9675162f94917a 0 33 61 2010-05-15T12:15:38Z Duck 2 Created page with '== How to Contribute ? == For those who'd like to contribute, we are investigating donations via PayPal. == What can you Contribute ? == Here are ideas on which to contribute:…' wikitext text/x-wiki == How to Contribute ? == For those who'd like to contribute, we are investigating donations via PayPal. == What can you Contribute ? == Here are ideas on which to contribute: * [[DcExpenses#Regular_Expenses|regular expenses]] * [~90€] add/replace memory on Toushirou (2GB is too low, and even if memtest did not find any problem with the current one, it is still not sure it is not at fault, so we could then test it and later readd it if ok), planned 2x2GB * [??? (quite expensive)] change Orfeo's backplane to have 4 disks slot instead of 2, and add 2 new disks (in a new RAID 1 array), planned at least 120GB capacity (2.5″ 10000 RPM SAS, like the other ones) (can be bought anywhere, but proprietary braquets needed) * [???] buy a new machine, to provide: VMs, more services redondancy, ... (hardware needed not yet evaluated, more on this later) e4663074aa31cf1562df98b1394c3357e696c7c9 67 61 2010-05-15T13:37:25Z Duck 2 wikitext text/x-wiki == How to Contribute ? == For those who'd like to contribute, we are investigating donations via PayPal. == What can you Contribute ? == Here are ideas on which to contribute: * [[DcExpenses#Regular_Expenses|regular expenses]] * [~90€] add/replace memory on Toushirou (2GB is too low, and even if memtest did not find any problem with the current one, it is still not sure it is not at fault, so we could then test it and later readd it if ok), planned 2x2GB * [??? (quite expensive)] change Orfeo's backplane to have 4 disks slot instead of 2, and add 2 new disks (in a new RAID 1 array), planned at least 120GB capacity (2.5″ 10000 RPM SAS, like the other ones) (can be bought anywhere, but proprietary braquets needed) * [???] buy a new machine, to provide: VMs, more services redondancy, ... (hardware needed not yet evaluated, more on this later) == List of Previous Contributions == {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Object !! Donnor !! Comments |- | 2006-01 || HD for Daneel (backup) || AnonymousDonnor1 || replaced since then |} Note: early contributions in the CoinNetwork projects are not taken into account, as most information is lost. 95cdf07509c44bff1974ba196737a4d51cd1f73e 68 67 2010-05-15T13:54:26Z Duck 2 /* List of Previous Contributions */ wikitext text/x-wiki == How to Contribute ? == For those who'd like to contribute, we are investigating donations via PayPal. == What can you Contribute ? == Here are ideas on which to contribute: * [[DcExpenses#Regular_Expenses|regular expenses]] * [~90€] add/replace memory on Toushirou (2GB is too low, and even if memtest did not find any problem with the current one, it is still not sure it is not at fault, so we could then test it and later readd it if ok), planned 2x2GB * [??? (quite expensive)] change Orfeo's backplane to have 4 disks slot instead of 2, and add 2 new disks (in a new RAID 1 array), planned at least 120GB capacity (2.5″ 10000 RPM SAS, like the other ones) (can be bought anywhere, but proprietary braquets needed) * [???] buy a new machine, to provide: VMs, more services redondancy, ... (hardware needed not yet evaluated, more on this later) == List of Previous Contributions == {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Object / Amount !! Donnor !! Comments |- | 2007-05 || Toushirou (1709.08€) || Duck |- | 2006-01 || HD for Daneel (backup) || AnonymousDonnor1 || replaced since then |} Note: early contributions in the CoinNetwork projects are not taken into account, as most information is lost. 31c4949f2a6caf7695c7d84acd5adfd17af089aa 70 68 2010-05-15T14:11:13Z Duck 2 /* List of Previous Contributions */ wikitext text/x-wiki == How to Contribute ? == For those who'd like to contribute, we are investigating donations via PayPal. == What can you Contribute ? == Here are ideas on which to contribute: * [[DcExpenses#Regular_Expenses|regular expenses]] * [~90€] add/replace memory on Toushirou (2GB is too low, and even if memtest did not find any problem with the current one, it is still not sure it is not at fault, so we could then test it and later readd it if ok), planned 2x2GB * [??? (quite expensive)] change Orfeo's backplane to have 4 disks slot instead of 2, and add 2 new disks (in a new RAID 1 array), planned at least 120GB capacity (2.5″ 10000 RPM SAS, like the other ones) (can be bought anywhere, but proprietary braquets needed) * [???] buy a new machine, to provide: VMs, more services redondancy, ... (hardware needed not yet evaluated, more on this later) == List of Previous Contributions == Only pure financial contributions are listed here; equipments and sponsored purchases are listed on the [[DcExpenses|DuckCorp expenses page]]. {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Amount !! Donnor !! Comments |} Note: early contributions in the CoinNetwork projects are not taken into account, as most information is lost. 30fc4ce0482fba01c3b51bb0a3650135f6269d2e 76 70 2010-05-17T18:38:31Z Duck 2 Protected "[[DcDonation]]" ([edit=sysop] (indefinite) [move=sysop] (indefinite)) wikitext text/x-wiki == How to Contribute ? == For those who'd like to contribute, we are investigating donations via PayPal. == What can you Contribute ? == Here are ideas on which to contribute: * [[DcExpenses#Regular_Expenses|regular expenses]] * [~90€] add/replace memory on Toushirou (2GB is too low, and even if memtest did not find any problem with the current one, it is still not sure it is not at fault, so we could then test it and later readd it if ok), planned 2x2GB * [??? (quite expensive)] change Orfeo's backplane to have 4 disks slot instead of 2, and add 2 new disks (in a new RAID 1 array), planned at least 120GB capacity (2.5″ 10000 RPM SAS, like the other ones) (can be bought anywhere, but proprietary braquets needed) * [???] buy a new machine, to provide: VMs, more services redondancy, ... (hardware needed not yet evaluated, more on this later) == List of Previous Contributions == Only pure financial contributions are listed here; equipments and sponsored purchases are listed on the [[DcExpenses|DuckCorp expenses page]]. {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Amount !! Donnor !! Comments |} Note: early contributions in the CoinNetwork projects are not taken into account, as most information is lost. 30fc4ce0482fba01c3b51bb0a3650135f6269d2e 77 76 2010-05-17T18:39:14Z Duck 2 /* List of Previous Contributions */ wikitext text/x-wiki == How to Contribute ? == For those who'd like to contribute, we are investigating donations via PayPal. == What can you Contribute ? == Here are ideas on which to contribute: * [[DcExpenses#Regular_Expenses|regular expenses]] * [~90€] add/replace memory on Toushirou (2GB is too low, and even if memtest did not find any problem with the current one, it is still not sure it is not at fault, so we could then test it and later readd it if ok), planned 2x2GB * [??? (quite expensive)] change Orfeo's backplane to have 4 disks slot instead of 2, and add 2 new disks (in a new RAID 1 array), planned at least 120GB capacity (2.5″ 10000 RPM SAS, like the other ones) (can be bought anywhere, but proprietary braquets needed) * [???] buy a new machine, to provide: VMs, more services redondancy, ... (hardware needed not yet evaluated, more on this later) == List of Previous Contributions == Only pure financial contributions are listed here; equipments and sponsored purchases are listed on the [[DcExpenses|DuckCorp expenses page]]. {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Amount !! Donnor !! Comments |- | 2010-05-16 || 42€ || Chloé |} Note: early contributions in the CoinNetwork projects are not taken into account, as most information is lost. 53a5e433a69e6dc788878b5e96bade5f3ad21049 79 77 2010-05-17T18:46:35Z Duck 2 /* How to Contribute ? */ wikitext text/x-wiki == How to Contribute ? == You can help us with: * sponsoring: if you can host a machine and/or provide connectivity * equipements: see the list of possible improvements below * money: you can send us money which will be used in the association: ** by check (see the duckcorp.org whois for Duck's postal address, or ask him by mail or IRC) ** by Paypal to duck@duckcorp.org == What can you Contribute ? == Here are ideas on which to contribute: * [[DcExpenses#Regular_Expenses|regular expenses]] * [~90€] add/replace memory on Toushirou (2GB is too low, and even if memtest did not find any problem with the current one, it is still not sure it is not at fault, so we could then test it and later readd it if ok), planned 2x2GB * [??? (quite expensive)] change Orfeo's backplane to have 4 disks slot instead of 2, and add 2 new disks (in a new RAID 1 array), planned at least 120GB capacity (2.5″ 10000 RPM SAS, like the other ones) (can be bought anywhere, but proprietary braquets needed) * [???] buy a new machine, to provide: VMs, more services redondancy, ... (hardware needed not yet evaluated, more on this later) == List of Previous Contributions == Only pure financial contributions are listed here; equipments and sponsored purchases are listed on the [[DcExpenses|DuckCorp expenses page]]. {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Amount !! Donnor !! Comments |- | 2010-05-16 || 42€ || Chloé |} Note: early contributions in the CoinNetwork projects are not taken into account, as most information is lost. bb81d16716b1e11583937f3ea55db4019372e1a3 85 79 2010-05-17T18:56:46Z Duck 2 wikitext text/x-wiki DuckCorp is built and maintained by volunteers, mostly with their own money. The services are totaly free of charge for all users, but you may wish to contribute to help us keep it working well and improve. == How to Contribute ? == You can help us with: * sponsoring: if you can host a machine and/or provide connectivity * equipements: see the list of possible improvements below * money: you can send us money which will be used in the association: ** by check (see the duckcorp.org whois for Duck's postal address, or ask him by mail or IRC) ** by Paypal to duck@duckcorp.org == What can you Contribute ? == Here are ideas on which to contribute: * [[DcExpenses#Regular_Expenses|regular expenses]] * [~90€] add/replace memory on Toushirou (2GB is too low, and even if memtest did not find any problem with the current one, it is still not sure it is not at fault, so we could then test it and later readd it if ok), planned 2x2GB * [??? (quite expensive)] change Orfeo's backplane to have 4 disks slot instead of 2, and add 2 new disks (in a new RAID 1 array), planned at least 120GB capacity (2.5″ 10000 RPM SAS, like the other ones) (can be bought anywhere, but proprietary braquets needed) * [???] buy a new machine, to provide: VMs, more services redondancy, ... (hardware needed not yet evaluated, more on this later) == List of Previous Contributions == Only pure financial contributions are listed here; equipments and sponsored purchases are listed on the [[DcExpenses|DuckCorp expenses page]]. {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Amount !! Donnor !! Comments |- | 2010-05-16 || 42€ || Chloé |} Note: early contributions in the CoinNetwork projects are not taken into account, as most information is lost. 0a0060e6b62a12aa1c6753bb113249fddbfcb34a 8 34 62 2010-05-15T12:38:12Z Duck 2 Created page with '/* CSS placed here will be applied to all skins */ .hiddenStructure {display: none} .if {display: none} /* wikitable/prettytable class for skinning normal tables */ table.wi…' css text/css /* CSS placed here will be applied to all skins */ .hiddenStructure {display: none} .if {display: none} /* wikitable/prettytable class for skinning normal tables */ table.wikitable, table.prettytable { margin: 1em 1em 1em 0; background: #f9f9f9; border: 1px #aaaaaa solid; border-collapse: collapse; } table.wikitable th, table.wikitable td, table.prettytable th, table.prettytable td { border: 1px #aaaaaa solid; padding: 0.2em; } table.wikitable th, table.prettytable th { background: #f2f2f2; text-align: center; } table.wikitable caption, table.prettytable caption { margin-left: inherit; margin-right: inherit; font-weight: bold; } .allpagesredirect { font-style: italic; } /*-----------------------------------------*/ /* COULEUR DE FOND */ /*-----------------------------------------*/ /* par défaut : la couleur des pages de discussion (ce qui évite donc d'avoir à redéfinir la couleur de la moitié des namespace) */ #content, #p-cactions li, #p-cactions li a { background: #FFFFEE; } /* Special: (bleu ciel) */ .ns--1 #content, .ns--1 #p-cactions li, .ns--1 #p-cactions li a { background: #F8FCFF; } /* (main) */ .ns-0 * #content, .ns-0 * #p-cactions li, .ns-0 * #p-cactions li a { background : white; } /* Utilisateur: */ .ns-2 * #content, .ns-2 * #p-cactions li, .ns-2 * #p-cactions li a { background : white; } /* Wikipédia: */ .ns-4 * #content, .ns-4 * #p-cactions li, .ns-4 * #p-cactions li a { background: #F4F4F4; } /* Image: */ .ns-6 * #content, .ns-6 * #p-cactions li, .ns-6 * #p-cactions li a { background: white; } /* MediaWiki: */ .ns-8 * #content, .ns-8 * #p-cactions li, .ns-8 * #p-cactions li a { background: #EEEEFF; } /* Modèle: */ .ns-10 * #content, .ns-10 * #p-cactions li, .ns-10 * #p-cactions li a { background: white; } /* Aide: */ .ns-12 * #content, .ns-12 * #p-cactions li, .ns-12 * #p-cactions li a { background: #FFEEEE; } /* Catégorie: */ .ns-14 * #content, .ns-14 * #p-cactions li, .ns-14 * #p-cactions li a { background: white; } /* Portail: */ .ns-100 * #content, .ns-100 * #p-cactions li, .ns-100 * #p-cactions li a { background: white; } /* Projet: */ .ns-102 * #content, .ns-102 * #p-cactions li, .ns-102 * #p-cactions li a { background: #F6F6F6;; } /* Référence: */ .ns-104 * #content, .ns-104 * #p-cactions li, .ns-104 * #p-cactions li a { background: #EEFFEE; } /* Style pour les pages de discussion ; gestion de la coloration indentative */ .ns-1 dd, .ns-3 dd, .ns-5 dd, .ns-7 dd, .ns-9 dd, .ns-11 dd, .ns-13 dd,.ns-15 dd, .ns-101 dd, .ns-103 dd, .ns-105 dd { margin: 0; padding: 0; } .ns-1 dl, .ns-3 dl, .ns-5 dl, .ns-7 dl, .ns-9 dl, .ns-11 dl, .ns-13 dl, .ns-15 dl, .ns-101 dl, .ns-103 dl, .ns-105 dl { border-top: solid 1px #F0F080; border-left: solid 1px #F0F080; padding-top: 0.5em; padding-left: 0.5em; margin-left: 1em; } .ns-1 dl, .ns-3 dl, .ns-5 dl, .ns-7 dl, .ns-9 dl, .ns-11 dl, .ns-13 dl, .ns-15 dl, .ns-101 dl, .ns-103 dl, .ns-105 dl { background-color: #FFFFE0; } .ns-1 dl dl, .ns-3 dl dl, .ns-5 dl dl, .ns-7 dl dl, .ns-9 dl dl, .ns-11 dl dl, .ns-13 dl dl, .ns-15 dl dl, .ns-101 dl dl, .ns-103 dl dl, .ns-105 dl dl { background-color: #FFFFEE; } .ns-1 dl dl dl, .ns-3 dl dl dl, .ns-5 dl dl dl, .ns-7 dl dl dl, .ns-9 dl dl dl, .ns-11 dl dl dl, .ns-13 dl dl dl, .ns-15 dl dl dl, .ns-101 dl dl dl, .ns-103 dl dl dl, .ns-105 dl dl dl { background-color: #FFFFE0; } .ns-1 dl dl dl dl, .ns-3 dl dl dl dl, .ns-5 dl dl dl dl, .ns-7 dl dl dl dl, .ns-9 dl dl dl dl, .ns-11 dl dl dl dl, .ns-13 dl dl dl dl, .ns-15 dl dl dl dl, .ns-101 dl dl dl dl, .ns-103 dl dl dl dl, .ns-105 dl dl dl dl { background-color: #FFFFEE; } .ns-1 dl dl dl dl dl, .ns-3 dl dl dl dl dl, .ns-5 dl dl dl dl dl, .ns-7 dl dl dl dl dl, .ns-9 dl dl dl dl dl, .ns-11 dl dl dl dl dl, .ns-13 dl dl dl dl dl, .ns-15 dl dl dl dl dl, .ns-101 dl dl dl dl dl, .ns-103 dl dl dl dl dl, .ns-105 dl dl dl dl dl { background-color: #FFFFE0; } .ns-1 dl dl dl dl dl dl, .ns-3 dl dl dl dl dl dl, .ns-5 dl dl dl dl dl dl, .ns-7 dl dl dl dl dl dl, .ns-9 dl dl dl dl dl dl, .ns-11 dl dl dl dl dl dl, .ns-13 dl dl dl dl dl dl, .ns-15 dl dl dl dl dl dl, .ns-101 dl dl dl dl dl dl, .ns-103 dl dl dl dl dl dl, .ns-105 dl dl dl dl dl dl { background-color: #FFFFEE; } .ns-1 dl dl dl dl dl dl dl, .ns-3 dl dl dl dl dl dl dl, .ns-5 dl dl dl dl dl dl dl, .ns-7 dl dl dl dl dl dl dl, .ns-9 dl dl dl dl dl dl dl, .ns-11 dl dl dl dl dl dl dl, .ns-13 dl dl dl dl dl dl dl, .ns-15 dl dl dl dl dl dl dl, .ns-101 dl dl dl dl dl dl dl, .ns-103 dl dl dl dl dl dl dl, .ns-105 dl dl dl dl dl dl dl { background-color: #FFFFE0; } .ns-1 dl dl dl dl dl dl dl dl, .ns-3 dl dl dl dl dl dl dl dl, .ns-5 dl dl dl dl dl dl dl dl, .ns-7 dl dl dl dl dl dl dl dl, .ns-9 dl dl dl dl dl dl dl dl, .ns-11 dl dl dl dl dl dl dl dl, .ns-13 dl dl dl dl dl dl dl dl, .ns-15 dl dl dl dl dl dl dl dl, .ns-101 dl dl dl dl dl dl dl dl, .ns-103 dl dl dl dl dl dl dl dl, .ns-105 dl dl dl dl dl dl dl dl { background-color: #FFFFEE; } .ns-1 dl dl dl dl dl dl dl dl dl, .ns-3 dl dl dl dl dl dl dl dl dl, .ns-5 dl dl dl dl dl dl dl dl dl, .ns-7 dl dl dl dl dl dl dl dl dl, .ns-9 dl dl dl dl dl dl dl dl dl, .ns-11 dl dl dl dl dl dl dl dl dl, .ns-13 dl dl dl dl dl dl dl dl dl, .ns-15 dl dl dl dl dl dl dl dl dl, .ns-101 dl dl dl dl dl dl dl dl dl, .ns-103 dl dl dl dl dl dl dl dl dl, .ns-105 dl dl dl dl dl dl dl dl dl { background-color: #FFFFE0; } .ns-1 dl dl dl dl dl dl dl dl dl dl, .ns-3 dl dl dl dl dl dl dl dl dl dl, .ns-5 dl dl dl dl dl dl dl dl dl dl, .ns-7 dl dl dl dl dl dl dl dl dl dl, .ns-9 dl dl dl dl dl dl dl dl dl dl, .ns-11 dl dl dl dl dl dl dl dl dl dl, .ns-13 dl dl dl dl dl dl dl dl dl dl, .ns-15 dl dl dl dl dl dl dl dl dl dl, .ns-101 dl dl dl dl dl dl dl dl dl dl, .ns-103 dl dl dl dl dl dl dl dl dl dl, .ns-105 dl dl dl dl dl dl dl dl dl dl { background-color: #FFFFEE; } /************************************************************ * Style de l'interface de Wikipédia ************************************************************/ /* Soulignement léger pour les sous-parties */ h3 { border-bottom: dotted 1px #aaa; } h4, h5, h6 { border-bottom: dotted 1px #ddd; } /* Fenêtres arrondies (pour les navigateurs moz/firefox/gecko) */ .pBody { padding: 0.3em 0.1em; -moz-border-radius-topright: 0.5em; } .portlet h5 { background-color: #e0e3e6; border: thin solid silver; -moz-border-radius-topright: 0.5em; } #p-cactions ul li, #p-cactions ul li a { -moz-border-radius-topright: 0.5em; -moz-border-radius-topleft: 0.5em; } /* interlignage des titres de pages : utile pour les titres « à rallonge » */ .firstHeading {line-height: 1.2em} fieldset.tiny { width: auto; margin: 2px 5px 2px 5px; } c95b178b127b1aa4d426d84f81e042bdd7bac21f 8 35 64 2010-05-15T12:39:55Z Duck 2 Created page with '/* Any JavaScript here will be loaded for all users on every page load. */ /* Test if an element has a certain class ************************************** * * Description: Us…' javascript text/javascript /* Any JavaScript here will be loaded for all users on every page load. */ /* Test if an element has a certain class ************************************** * * Description: Uses regular expressions and caching for better performance. * Maintainers: [[User:Mike Dillon]], [[User:R. Koot]], [[User:SG]] */ var hasClass = (function () { var reCache = {}; return function (element, className) { return (reCache[className] ? reCache[className] : (reCache[className] = new RegExp("(?:\\s|^)" + className + "(?:\\s|$)"))).test(element.className); }; })(); /** Collapsible tables ********************************************************* * * Description: Allows tables to be collapsed, showing only the header. See * [[Wikipedia:NavFrame]]. * Maintainers: [[User:R. Koot]] * * Modified by Proformatique */ var autoCollapse = 3; var collapseCaption = "hide"; var expandCaption = "show"; function collapseTable( tableIndex ) { var Button = document.getElementById( "collapseButton" + tableIndex ); var Table = document.getElementById( "collapsibleTable" + tableIndex ); if ( !Table || !Button ) { return false; } var i; var Rows = Table.rows; var TitleRowSpans = Rows[0].getElementsByTagName( "span" ); if ( Button.firstChild.data == collapseCaption ) { if (TitleRowSpans) { for ( i = 0; i < TitleRowSpans.length; i++ ) { if (hasClass(TitleRowSpans[i], "hideExpanded")) { TitleRowSpans[i].style.display = Rows[0].style.display; } if (hasClass(TitleRowSpans[i], "hideCollapsed")) { TitleRowSpans[i].style.display = "none"; } } } for ( i = 1; i < Rows.length; i++ ) { Rows[i].style.display = "none"; } Button.firstChild.data = expandCaption; } else { if (TitleRowSpans) { for ( i = 0; i < TitleRowSpans.length; i++ ) { if (hasClass(TitleRowSpans[i], "hideExpanded")) { TitleRowSpans[i].style.display = "none"; } if (hasClass(TitleRowSpans[i], "hideCollapsed")) { TitleRowSpans[i].style.display = Rows[0].style.display; } } } for ( i = 1; i < Rows.length; i++ ) { Rows[i].style.display = Rows[0].style.display; } Button.firstChild.data = collapseCaption; } } function createCollapseButtons() { var tableIndex = 0; var NavigationBoxes = new Object(); var Tables = document.getElementsByTagName( "table" ); for ( var i = 0; i < Tables.length; i++ ) { if ( hasClass( Tables[i], "collapsible" ) ) { /* only add button and increment count if there is a header row to work with */ var HeaderRow = Tables[i].getElementsByTagName( "tr" )[0]; if (!HeaderRow) continue; var Header = HeaderRow.getElementsByTagName( "th" )[0]; if (!Header) continue; var TitleRowSpans = Tables[i].rows[0].getElementsByTagName( "span" ); for ( j = 0; j < TitleRowSpans.length; j++ ) { if (hasClass(TitleRowSpans[j], "hideExpanded")) { TitleRowSpans[j].style.display = "none"; } } NavigationBoxes[ tableIndex ] = Tables[i]; Tables[i].setAttribute( "id", "collapsibleTable" + tableIndex ); var Button = document.createElement( "span" ); var ButtonLink = document.createElement( "a" ); var ButtonText = document.createTextNode( collapseCaption ); Button.className = "collapseButton"; //Styles are declared in Common.css ButtonLink.style.color = Header.style.color; ButtonLink.setAttribute( "id", "collapseButton" + tableIndex ); ButtonLink.setAttribute( "href", "javascript:collapseTable(" + tableIndex + ");" ); ButtonLink.appendChild( ButtonText ); Button.appendChild( document.createTextNode( "[" ) ); Button.appendChild( ButtonLink ); Button.appendChild( document.createTextNode( "]" ) ); Header.insertBefore( Button, Header.childNodes[0] ); tableIndex++; } } for ( var i = 0; i < tableIndex; i++ ) { if ( hasClass( NavigationBoxes[i], "collapsed" ) || ( i >= autoCollapse && hasClass( NavigationBoxes[i], "autocollapse" ) ) ) { collapseTable( i ); } else if ( hasClass( NavigationBoxes[i], "innercollapse" ) ) { var element = NavigationBoxes[i]; while (element = element.parentNode) { if ( hasClass( element, "outercollapse" ) ) { collapseTable ( i ); break; } } } } } addOnloadHook( createCollapseButtons ); be2121a573b48b460fb3a91d4b08046f251561b1 0 1 81 23 2010-05-17T18:50:07Z Duck 2 wikitext text/x-wiki {{:Main Page/Introduction}} {{:Main Page/Association}} aa3c842adaf36f7ea7144aee730d84e97e13bca1 86 81 2010-05-17T18:58:08Z Duck 2 wikitext text/x-wiki {{:Main Page/Introduction}} {{:Main Page/Association}} {{:Main Page/Technical}} e36dfb1af5fd4ed10a712080779c0b30251f925c 91 86 2010-05-17T19:07:38Z Duck 2 wikitext text/x-wiki {|border="0" cellspacing="0" cellpadding="0" style="padding:0px; margin:0px; height:100%; background:transparent; " | {{:Main Page/Introduction}} |- {| width=100% | width=50% valign=top style="height:100%;" | {{:Main Page/Association}} | width=50% valign=top style="height:100%;" | {{:Main Page/Technical}} |} 339f8647b8860580fa17aaa28398279caaeb5a99 0 36 82 2010-05-17T18:52:19Z Duck 2 Created page with '{{Robelbox|title=Association|theme={{{theme|3}}}}} {{Padbox}} Here are bits of information about us: * [[A bit of History]] * [[DcExpenses|Association expenses]] * [[DcDonation|H…' wikitext text/x-wiki {{Robelbox|title=Association|theme={{{theme|3}}}}} {{Padbox}} Here are bits of information about us: * [[A bit of History]] * [[DcExpenses|Association expenses]] * [[DcDonation|How and why make a donation]] \_o< {{Padbox/close}} {{Robelbox/close}} 114709e0f25203e065d84badf8ba54e759eef322 83 82 2010-05-17T18:52:25Z Duck 2 Protected "[[Main Page/Association]]" ([edit=sysop] (indefinite) [move=sysop] (indefinite)) wikitext text/x-wiki {{Robelbox|title=Association|theme={{{theme|3}}}}} {{Padbox}} Here are bits of information about us: * [[A bit of History]] * [[DcExpenses|Association expenses]] * [[DcDonation|How and why make a donation]] \_o< {{Padbox/close}} {{Robelbox/close}} 114709e0f25203e065d84badf8ba54e759eef322 84 83 2010-05-17T18:52:37Z Duck 2 wikitext text/x-wiki {{Robelbox|title=Association|theme={{{theme|3}}}}} {{Padbox}} Here are bits of information about us: * [[A bit of History]] * [[DcExpenses|Association expenses]] * [[DcDonation|How and why make a donation]] {{Padbox/close}} {{Robelbox/close}} e7e89fe68f7ab4ca6fa0ad50aa9ab95b10eb2a77 0 37 87 2010-05-17T19:00:07Z Duck 2 Created page with '{{Robelbox|title=Introduction|theme={{{theme|9}}}}} {{Padbox}} * [[DcArchitecture|Architecture]] {{todo}} work in progress... {{Padbox/close}} {{Robelbox/close}}' wikitext text/x-wiki {{Robelbox|title=Introduction|theme={{{theme|9}}}}} {{Padbox}} * [[DcArchitecture|Architecture]] {{todo}} work in progress... {{Padbox/close}} {{Robelbox/close}} ab8de32beb92a86e9cac22a80c5a3e223586453b 88 87 2010-05-17T19:00:21Z Duck 2 Protected "[[Main Page/Technical]]" ([edit=sysop] (indefinite) [move=sysop] (indefinite)) wikitext text/x-wiki {{Robelbox|title=Introduction|theme={{{theme|9}}}}} {{Padbox}} * [[DcArchitecture|Architecture]] {{todo}} work in progress... {{Padbox/close}} {{Robelbox/close}} ab8de32beb92a86e9cac22a80c5a3e223586453b 89 88 2010-05-17T19:00:34Z Duck 2 wikitext text/x-wiki {{Robelbox|title=Technical Information|theme={{{theme|9}}}}} {{Padbox}} * [[DcArchitecture|Architecture]] {{todo}} work in progress... {{Padbox/close}} {{Robelbox/close}} 5822969cb32bce4328c39cb19c1cb9c210e1c629 98 89 2010-06-10T18:51:21Z Duck 2 wikitext text/x-wiki {{Robelbox|title=Technical Information|theme={{{theme|9}}}}} {{Padbox}} * [[DcArchitecture|Architecture]] * [[UserMagicalInterface|User Magical Interface]] {{todo}} work in progress... {{Padbox/close}} {{Robelbox/close}} a4d1a3b0225f8f4c7e22013b52b9bb5bba9a161e 0 38 99 2010-06-10T19:13:01Z Duck 2 Created page with 'We are working to give users more control on their own resources, but it is a difficult task. We are working on a tool, but it is still heavily work in progress. It works correct…' wikitext text/x-wiki We are working to give users more control on their own resources, but it is a difficult task. We are working on a tool, but it is still heavily work in progress. It works correctly, but its skill is currently limited to a few tasks. == Requirements == This tool is accessible through a mail interface (later, we might add other types of frontends), and does care about security and privacy. You need to get a GPG/PGP key, and get it registered in a safe manner in our database (contact an administrator for this). As you may send '''secret''' information in the mail, you would like to hide it. Use the key EF410567 (fingerprint: D0CC BBA5 5460 719D 515C 11E6 E770 C685 EF41 0567), signed by the DuckCorp Administrators, for encryption. This is an optional, but recommanded, feature. == Usage == Once it is done, you just need to send a signed mail to "MilkyPond Administration Officer" <banya=hATe=milkypond.org> with a list of commands in the body. Empty lines and comments (lines starting with "#") are ignored. The subject is purely informational, for you to identify the reply to the corresponding demand. == Available Commands == feab0cd989d7627ce82c7590273015f0cc659d86 100 99 2010-06-10T19:17:41Z Duck 2 /* Available Commands */ wikitext text/x-wiki We are working to give users more control on their own resources, but it is a difficult task. We are working on a tool, but it is still heavily work in progress. It works correctly, but its skill is currently limited to a few tasks. == Requirements == This tool is accessible through a mail interface (later, we might add other types of frontends), and does care about security and privacy. You need to get a GPG/PGP key, and get it registered in a safe manner in our database (contact an administrator for this). As you may send '''secret''' information in the mail, you would like to hide it. Use the key EF410567 (fingerprint: D0CC BBA5 5460 719D 515C 11E6 E770 C685 EF41 0567), signed by the DuckCorp Administrators, for encryption. This is an optional, but recommanded, feature. == Usage == Once it is done, you just need to send a signed mail to "MilkyPond Administration Officer" <banya=hATe=milkypond.org> with a list of commands in the body. Empty lines and comments (lines starting with "#") are ignored. The subject is purely informational, for you to identify the reply to the corresponding demand. == Available Commands == * DNS INFO : to get the list of DNS zones you can manage (and probably more in the future) * DNS GET ZONE &lt;zone&gt; : to get the DNS &lt;zone&gt; content (attached in the reply) * DNS SET ZONE &lt;zone&gt; @&lt;i&gt; : to replace the current DNS &lt;zone&gt; content with the &lt;i&gt;st/nd/rd/th attachment (text/plain accepted only) : the zone syntax is checked before replacement dd44c46a005df63feb8627a511445cabbc32c073 0 38 101 100 2010-06-10T19:20:33Z Duck 2 /* Requirements */ wikitext text/x-wiki We are working to give users more control on their own resources, but it is a difficult task. We are working on a tool, but it is still heavily work in progress. It works correctly, but its skill is currently limited to a few tasks. == Requirements == This tool is accessible through a mail interface (later, we might add other types of frontends), and does care about security and privacy. You need to get a GPG/PGP key, and get it registered in a safe manner in our database (contact an administrator for this). As you may send '''secret''' information in the mail, you would like to hide it. Use the key EF410567 (fingerprint: D0CC BBA5 5460 719D 515C 11E6 E770 C685 EF41 0567), signed by the DuckCorp Administrators, for encryption. This is an optional, but recommended, feature. == Usage == Once it is done, you just need to send a signed mail to "MilkyPond Administration Officer" <banya=hATe=milkypond.org> with a list of commands in the body. Empty lines and comments (lines starting with "#") are ignored. The subject is purely informational, for you to identify the reply to the corresponding demand. == Available Commands == * DNS INFO : to get the list of DNS zones you can manage (and probably more in the future) * DNS GET ZONE &lt;zone&gt; : to get the DNS &lt;zone&gt; content (attached in the reply) * DNS SET ZONE &lt;zone&gt; @&lt;i&gt; : to replace the current DNS &lt;zone&gt; content with the &lt;i&gt;st/nd/rd/th attachment (text/plain accepted only) : the zone syntax is checked before replacement 423d6d94fc87d7b05ef9bfaf60f69bd0f7f1d549 102 101 2010-06-10T19:21:04Z Duck 2 wikitext text/x-wiki We are working to give users more control on their own resources, but it is a difficult task. We are working on a tool, but it is still heavily work in progress. It works correctly, but its skill is currently limited to a few tasks. == Requirements == This tool is accessible through a mail interface (later, we might add other types of frontends), and does care about security and privacy. You need to get a GPG/PGP key, and get it registered in a safe manner in our database (contact an administrator for this). The mail should be RFC3156-compliant, and should not use the combined method described in chapter 6.2 of this RFC (not supported yet). == Usage == Once it is done, you just need to send a signed mail to "MilkyPond Administration Officer" <banya=hATe=milkypond.org> with a list of commands in the body. Empty lines and comments (lines starting with "#") are ignored. The subject is purely informational, for you to identify the reply to the corresponding demand. As you may send '''secret''' information in the mail, you would like to hide it. Use the key EF410567 (fingerprint: D0CC BBA5 5460 719D 515C 11E6 E770 C685 EF41 0567), signed by the DuckCorp Administrators, for encryption. This is an optional, but recommended, feature. == Available Commands == * DNS INFO : to get the list of DNS zones you can manage (and probably more in the future) * DNS GET ZONE &lt;zone&gt; : to get the DNS &lt;zone&gt; content (attached in the reply) * DNS SET ZONE &lt;zone&gt; @&lt;i&gt; : to replace the current DNS &lt;zone&gt; content with the &lt;i&gt;st/nd/rd/th attachment (text/plain accepted only) : the zone syntax is checked before replacement 66262a8761dbbb34021a50fd61a93b88d4a2a5fa 103 102 2010-06-10T19:25:37Z Duck 2 /* Requirements */ wikitext text/x-wiki We are working to give users more control on their own resources, but it is a difficult task. We are working on a tool, but it is still heavily work in progress. It works correctly, but its skill is currently limited to a few tasks. == Requirements == This tool is accessible through a mail interface (later, we might add other types of frontends), and does care about security and privacy. You need to get a GPG/PGP key, and get it registered in a safe manner in our database (contact an administrator for this). If you hate english, you might also ask an administration to change your language preferences. The mail should be RFC3156-compliant, and should not use the combined method described in chapter 6.2 of this RFC (not supported yet). == Usage == Once it is done, you just need to send a signed mail to "MilkyPond Administration Officer" <banya=hATe=milkypond.org> with a list of commands in the body. Empty lines and comments (lines starting with "#") are ignored. The subject is purely informational, for you to identify the reply to the corresponding demand. As you may send '''secret''' information in the mail, you would like to hide it. Use the key EF410567 (fingerprint: D0CC BBA5 5460 719D 515C 11E6 E770 C685 EF41 0567), signed by the DuckCorp Administrators, for encryption. This is an optional, but recommended, feature. == Available Commands == * DNS INFO : to get the list of DNS zones you can manage (and probably more in the future) * DNS GET ZONE &lt;zone&gt; : to get the DNS &lt;zone&gt; content (attached in the reply) * DNS SET ZONE &lt;zone&gt; @&lt;i&gt; : to replace the current DNS &lt;zone&gt; content with the &lt;i&gt;st/nd/rd/th attachment (text/plain accepted only) : the zone syntax is checked before replacement e5829ab072aa12f0c902c5ab908193554399fae3 104 103 2010-06-10T19:27:21Z Duck 2 wikitext text/x-wiki We are working to give users more control on their own resources, but it is a difficult task. We are working on a tool, but it is still heavily work in progress. It works correctly, but its skill is currently limited to a few tasks. == Requirements == This tool is accessible through a mail interface (later, we might add other types of frontends), and does care about security and privacy. You need to get a GPG/PGP key, and get it registered in a safe manner in our database (contact an administrator for this). If you hate english, you might also ask an administration to change your language preferences. The mail should be RFC3156-compliant, and should not use the combined method described in chapter 6.2 of this RFC (not supported yet). == Usage == Once it is done, you just need to send a signed mail to "MilkyPond Administration Officer" <banya=hATe=milkypond.org> with a list of commands in the body. Empty lines and comments (lines starting with "#") are ignored. The subject is purely informational, for you to identify the reply to the corresponding demand. As you may send '''secret''' information in the mail, you would like to hide it. Use the key EF410567 (fingerprint: D0CC BBA5 5460 719D 515C 11E6 E770 C685 EF41 0567), signed by the DuckCorp Administrators, for encryption. This is an optional, but recommended, feature. == Available Languages == * en * fr The setting follow the RFC 2616 Accept-Language field syntax. == Available Commands == * DNS INFO : to get the list of DNS zones you can manage (and probably more in the future) * DNS GET ZONE &lt;zone&gt; : to get the DNS &lt;zone&gt; content (attached in the reply) * DNS SET ZONE &lt;zone&gt; @&lt;i&gt; : to replace the current DNS &lt;zone&gt; content with the &lt;i&gt;st/nd/rd/th attachment (text/plain accepted only) : the zone syntax is checked before replacement 0e621d1eb7faf7fd0a71136ba4c21960bf6d569f 105 104 2010-06-10T19:29:20Z Duck 2 wikitext text/x-wiki We are working to give users more control on their own resources, but it is a difficult task. We are working on a tool, but it is still heavily work in progress. It works correctly, but its skill is currently limited to a few tasks. == Requirements == This tool is accessible through a mail interface (later, we might add other types of frontends), and does care about security and privacy. You need to get a GPG/PGP key, and get it registered in a safe manner in our database (contact an administrator for this). If you hate english, you might also ask an administration to change your language preferences. The mail should be RFC3156-compliant, and should not use the combined method described in chapter 6.2 of this RFC (not supported yet). == Usage == Once it is done, you just need to send a signed mail to "MilkyPond Administration Officer" <banya=hATe=milkypond.org> with a list of commands in the body. Empty lines and comments (lines starting with "#") are ignored. The subject is purely informational, for you to identify the reply to the corresponding demand. As you may send '''secret''' information in the mail, you would like to hide it. Use the key EF410567 (fingerprint: D0CC BBA5 5460 719D 515C 11E6 E770 C685 EF41 0567), signed by the DuckCorp Administrators, for encryption. This is an optional, but recommended, feature. == Available Languages == * en * fr The setting follow the RFC 2616 Accept-Language field syntax. == Available Commands == * DNS INFO : to get the list of DNS zones you can manage (and probably more in the future) * DNS GET ZONE &lt;zone&gt; : to get the DNS &lt;zone&gt; content (attached in the reply) * DNS SET ZONE &lt;zone&gt; @&lt;i&gt; : to replace the current DNS &lt;zone&gt; content with the &lt;i&gt;st/nd/rd/th attachment (text/plain accepted only) : the zone syntax is checked before replacement == Project Info == Please see https://projects.duckcorp.org/projects/cyborghood. 4ecdbb788fd1a539f994e02dd48bd01c83483920 128 105 2010-10-30T18:07:26Z Duck 2 /* Available Commands */ wikitext text/x-wiki We are working to give users more control on their own resources, but it is a difficult task. We are working on a tool, but it is still heavily work in progress. It works correctly, but its skill is currently limited to a few tasks. == Requirements == This tool is accessible through a mail interface (later, we might add other types of frontends), and does care about security and privacy. You need to get a GPG/PGP key, and get it registered in a safe manner in our database (contact an administrator for this). If you hate english, you might also ask an administration to change your language preferences. The mail should be RFC3156-compliant, and should not use the combined method described in chapter 6.2 of this RFC (not supported yet). == Usage == Once it is done, you just need to send a signed mail to "MilkyPond Administration Officer" <banya=hATe=milkypond.org> with a list of commands in the body. Empty lines and comments (lines starting with "#") are ignored. The subject is purely informational, for you to identify the reply to the corresponding demand. As you may send '''secret''' information in the mail, you would like to hide it. Use the key EF410567 (fingerprint: D0CC BBA5 5460 719D 515C 11E6 E770 C685 EF41 0567), signed by the DuckCorp Administrators, for encryption. This is an optional, but recommended, feature. == Available Languages == * en * fr The setting follow the RFC 2616 Accept-Language field syntax. == Available Commands == === DNS management === Beware to properly update the serial! Available commands: * DNS INFO : to get the list of DNS zones you can manage (and probably more in the future) * DNS GET ZONE &lt;zone&gt; : to get the DNS &lt;zone&gt; content (attached in the reply) * DNS SET ZONE &lt;zone&gt; @&lt;i&gt; : to replace the current DNS &lt;zone&gt; content with the &lt;i&gt;st/nd/rd/th attachment (text/plain accepted only) : the zone syntax is checked before replacement Notes for signed zones: * the support for signed zone is basic, no specific information or possibility to setup any parameter yet * the fetched zone (with the GET command) does not reflect the real serial, as the signer process update the serial automatically when resigning the zone, so you need to ask for the current serial with the following command: host -t soa <zone> == Project Info == Please see https://projects.duckcorp.org/projects/cyborghood. 2aea48e6e8f5a93921f06a2c6ce5aaa7ae89dc4a 0 37 106 98 2010-06-22T11:41:54Z Duck 2 wikitext text/x-wiki {{Robelbox|title=Technical Information|theme={{{theme|9}}}}} {{Padbox}} * [[DcArchitecture|Architecture]] * [[AvailableServices| Available Services]] * [[UserMagicalInterface|User Magical Interface]] {{todo}} work in progress... {{Padbox/close}} {{Robelbox/close}} a43d0e12a65fe6b91accebd9a788a4f20d718c97 145 106 2010-10-31T00:30:50Z Duck 2 wikitext text/x-wiki {{Robelbox|title=Technical Information|theme={{{theme|9}}}}} {{Padbox}} * [[DcArchitecture|Architecture]] * [[Services| Available Services]] * [[UserMagicalInterface|User Magical Interface]] {{todo}} work in progress... {{Padbox/close}} {{Robelbox/close}} 254ead0ea1675881fc2bfcb447f03b1d86df3117 0 39 107 2010-06-22T11:53:55Z Duck 2 Created page with 'Here is a short overview of the services provided by DuckCorp. Public services: * a stratum 2 NTP server, to setup time on your machines, and also part of the [http://www.pool.n…' wikitext text/x-wiki Here is a short overview of the services provided by DuckCorp. Public services: * a stratum 2 NTP server, to setup time on your machines, and also part of the [http://www.pool.ntp.org/en/ NTP Pool Project] * a dictionnary server, using the DICT protocol, and with a [http://dico.duckcorp.org/ web interface] Users services: e60d46420023a369f918fe3ffb3be94cb1223713 108 107 2010-06-22T12:01:58Z Duck 2 wikitext text/x-wiki Here is a short overview of the services provided by DuckCorp. Public services: * a stratum 2 NTP server, to setup time on your machines, and also part of the [http://www.pool.ntp.org/en/ NTP Pool Project] * a dictionnary server, using the DICT protocol, and with a [http://dico.duckcorp.org/ web interface] Users services: * web hosting, with various possibilities for web programming (SSI, PHP, Perl, Python, Ruby, ...) * DNS hosting (MX1/MX2) * communication facilities: ** mail hosting (user controlled antispam, antivirus, flexible quotas, SIEVE filtering, ...) ** IRC Network ** XMPP (Jabber) Network (using the 'milkypond.org' domain, or a user domain) ** Triboune Libre 73f96c0e2c0c6f9c61930bf36997da5e82d116aa 109 108 2010-06-22T12:06:49Z Duck 2 wikitext text/x-wiki Here is a short overview of the services provided by DuckCorp. Public services: * a stratum 2 NTP server, to setup time on your machines, and also part of the [http://www.pool.ntp.org/en/ NTP Pool Project] * a dictionnary server, using the DICT protocol, and with a [http://dico.duckcorp.org/ web interface] Users services: * Network facilities: ** DNS hosting (MX1/MX2) * Communication facilities: ** mail hosting (user controlled antispam, antivirus, flexible quotas, SIEVE filtering, ...) ** IRC Network ** XMPP (Jabber) Network (using the 'milkypond.org' domain, or a user domain) ** Triboune Libre * Application facilities: ** web hosting, with various possibilities for web programming (SSI, PHP, Perl, Python, Ruby, ...) ** VCS hosting: git, SVN, BZR ** shell access (site admin, run custom scripts, screen for text-mode geeks, ...) (for trusted users only) * Databases facilities: ** PostgreSQL ** MySQL ** LDAP 41d2247e875a034c62e8a6fdc39324db60166380 110 109 2010-06-22T12:20:50Z Duck 2 wikitext text/x-wiki Here is a short overview of the services provided by DuckCorp. Public services: * a stratum 2 NTP server, to setup time on your machines, and also part of the [http://www.pool.ntp.org/en/ NTP Pool Project] * a dictionnary server, using the DICT protocol, and with a [http://dico.duckcorp.org/ web interface] Users services: * Network facilities: ** DNS hosting (MX1/MX2) ** IPv6 tunnels * Communication facilities: ** mail hosting (user controlled antispam, antivirus, flexible quotas, SIEVE filtering, ...) ** IRC Network ** XMPP (Jabber) Network (using the 'milkypond.org' domain, or a user domain) ** Triboune Libre ** SAFT * Application facilities: ** web hosting, with various possibilities for web programming (SSI, PHP, Perl, Python, Ruby, ...) ** VCS hosting: git, SVN, BZR ** shell access (site admin, run custom scripts, screen for text-mode geeks, ...) (for trusted users only) * Databases facilities: ** PostgreSQL ** MySQL ** LDAP 5dc4d516df91ab95131932de09916d19c201f713 111 110 2010-06-22T12:22:49Z Duck 2 wikitext text/x-wiki Here is a short overview of the services provided by DuckCorp. Public services: * a stratum 2 NTP server, to setup time on your machines, and also part of the [http://www.pool.ntp.org/en/ NTP Pool Project] * a dictionnary server, using the DICT protocol, and with a [http://dico.duckcorp.org/ web interface] Users services: * Network facilities: ** DNS hosting (MX1/MX2) ** IPv6 tunnels * Communication facilities: ** mail hosting (user controlled antispam, antivirus, flexible quotas, SIEVE filtering, webmails, ...) ** FTP server ** IRC Network ** XMPP (Jabber) Network (using the 'milkypond.org' domain, or a user domain) ** Triboune Libre ** SAFT * Application facilities: ** web hosting, with various possibilities for web programming (SSI, PHP, Perl, Python, Ruby, ...) ** VCS hosting: git, SVN, BZR ** shell access (site admin, run custom scripts, screen for text-mode geeks, ...) (for trusted users only) * Databases facilities: ** PostgreSQL ** MySQL ** LDAP eec3dbe036d6261a56d2aba2d7bbba64e732bdde 112 111 2010-06-22T12:23:31Z Duck 2 wikitext text/x-wiki Here is a short overview of the services provided by DuckCorp. Public services: * a stratum 2 NTP server, to setup time on your machines, and also part of the [http://www.pool.ntp.org/en/ NTP Pool Project] * a dictionnary server, using the DICT protocol, and with a [http://dico.duckcorp.org/ web interface] Users services: * Network facilities: ** DNS hosting (MX1/MX2) ** IPv6 tunnels * Communication facilities: ** mail hosting (user controlled antispam, antivirus, flexible quotas, SIEVE filtering, webmails, ...) ** mailing-lists hosting ** FTP server ** IRC Network ** XMPP (Jabber) Network (using the 'milkypond.org' domain, or a user domain) ** Triboune Libre ** SAFT * Application facilities: ** web hosting, with various possibilities for web programming (SSI, PHP, Perl, Python, Ruby, ...) ** VCS hosting: git, SVN, BZR ** shell access (site admin, run custom scripts, screen for text-mode geeks, ...) (for trusted users only) * Databases facilities: ** PostgreSQL ** MySQL ** LDAP eb0854bc99f74c22111698b1510c7e4a1780e38c 113 112 2010-06-22T12:26:03Z Duck 2 wikitext text/x-wiki Here is a short overview of the services provided by DuckCorp. Public services: * a stratum 2 NTP server, to setup time on your machines, and also part of the [http://www.pool.ntp.org/en/ NTP Pool Project] * a dictionnary server, using the DICT protocol, and with a [http://dico.duckcorp.org/ web interface] Users services: * Network facilities: ** DNS hosting (MX1/MX2) ** IPv6 tunnels * Communication facilities: ** mail hosting (user controlled antispam, antivirus, flexible quotas, SIEVE filtering, webmails, ...) ** mailing-lists hosting ** FTP server ** IRC world: *** IRC Network (with web gateway) *** IRC bouncer *** IRC to IM gateway (to connect to ICQ/AIM/YM!/... through an IRC interface) ** XMPP (Jabber) Network (using the 'milkypond.org' domain, or a user domain) ** Triboune Libre ** SAFT * Application facilities: ** web hosting, with various possibilities for web programming (SSI, PHP, Perl, Python, Ruby, ...) ** VCS hosting: git, SVN, BZR ** shell access (site admin, run custom scripts, screen for text-mode geeks, ...) (for trusted users only) * Databases facilities: ** PostgreSQL ** MySQL ** LDAP ccab42657957807ba009c82339e396edaedf48e4 114 113 2010-06-22T12:32:27Z Duck 2 wikitext text/x-wiki Here is a short overview of the services provided by DuckCorp. Public Services: * a stratum 2 NTP server, to setup time on your machines, and also part of the [http://www.pool.ntp.org/en/ NTP Pool Project] * a dictionnary server, using the DICT protocol, and with a [http://dico.duckcorp.org/ web interface] Users Services: * Network facilities: ** DNS hosting (MX1/MX2) ** IPv6 tunnels * Communication facilities: ** mail hosting (user controlled antispam, antivirus, flexible quotas, SIEVE filtering, webmails, ...) ** mailing-lists hosting ** FTP server ** IRC world: *** IRC Network (with web gateway) *** IRC bouncer *** IRC to IM gateway (to connect to ICQ/AIM/YM!/... through an IRC interface) ** XMPP (Jabber) Network (using the 'milkypond.org' domain, or a user domain) ** Triboune Libre ** SAFT * Application facilities: ** web hosting, with various possibilities for web programming (SSI, PHP, Perl, Python, Ruby, ...), and stats ** VCS hosting: git, SVN, BZR ** shell access (site admin, run custom scripts, screen for text-mode geeks, ...) (for trusted users only) * Databases facilities: ** PostgreSQL ** MySQL ** LDAP Shared Users Services: * [https://wiki.duckcorp.org/ public wiki] (with ACLs) * [http://photos.duckcorp.org/ public photo gallery] (with ACLs) * [https://projects.duckcorp.org/ public issue tracker] (with ACLs) * [https://rcs.duckcorp.org/ public VCS accès] (with web viewers) * [http://debian.duckcorp.org/ public Debian repository] 30cbca5087d6fc694b9f2f0e4c36c64ae1ca52a9 115 114 2010-06-22T12:38:28Z Duck 2 wikitext text/x-wiki Here is a short overview of the services provided by DuckCorp. Our services are supervised and important data are saved regulary. == Public Services == * a stratum 2 NTP server, to setup time on your machines, and also part of the [http://www.pool.ntp.org/en/ NTP Pool Project] * a dictionnary server, using the DICT protocol, and with a [http://dico.duckcorp.org/ web interface] == Users Services == * Network facilities: ** DNS hosting (MX1/MX2) ** IPv6 tunnels * Communication facilities: ** mail hosting (user controlled antispam, antivirus, flexible quotas, SIEVE filtering, webmails, ...) ** mailing-lists hosting ** FTP server ** IRC world: *** IRC Network (with web gateway) *** IRC bouncer *** IRC to IM gateway (to connect to ICQ/AIM/YM!/... through an IRC interface) ** XMPP (Jabber) Network (using the 'milkypond.org' domain, or a user domain) ** Triboune Libre ** SAFT * Application facilities: ** web hosting, with various possibilities for web programming (SSI, PHP, Perl, Python, Ruby, ...), and stats ** VCS hosting: git, SVN, BZR ** shell access (site admin, run custom scripts, screen for text-mode geeks, ...) (for trusted users only) * Databases facilities: ** PostgreSQL ** MySQL ** LDAP == Shared Users Services == * [https://wiki.duckcorp.org/ public wiki] (with ACLs) * [http://photos.duckcorp.org/ public photo gallery] (with ACLs) * [https://projects.duckcorp.org/ public issue tracker] (with ACLs) * [https://rcs.duckcorp.org/ public VCS accès] (with web viewers) * [http://debian.duckcorp.org/ public Debian repository] 59e08492863de671703e9c163e328080b3ffc2c6 116 115 2010-06-22T12:40:29Z Duck 2 /* Shared Users Services */ wikitext text/x-wiki Here is a short overview of the services provided by DuckCorp. Our services are supervised and important data are saved regulary. == Public Services == * a stratum 2 NTP server, to setup time on your machines, and also part of the [http://www.pool.ntp.org/en/ NTP Pool Project] * a dictionnary server, using the DICT protocol, and with a [http://dico.duckcorp.org/ web interface] == Users Services == * Network facilities: ** DNS hosting (MX1/MX2) ** IPv6 tunnels * Communication facilities: ** mail hosting (user controlled antispam, antivirus, flexible quotas, SIEVE filtering, webmails, ...) ** mailing-lists hosting ** FTP server ** IRC world: *** IRC Network (with web gateway) *** IRC bouncer *** IRC to IM gateway (to connect to ICQ/AIM/YM!/... through an IRC interface) ** XMPP (Jabber) Network (using the 'milkypond.org' domain, or a user domain) ** Triboune Libre ** SAFT * Application facilities: ** web hosting, with various possibilities for web programming (SSI, PHP, Perl, Python, Ruby, ...), and stats ** VCS hosting: git, SVN, BZR ** shell access (site admin, run custom scripts, screen for text-mode geeks, ...) (for trusted users only) * Databases facilities: ** PostgreSQL ** MySQL ** LDAP == Shared Users Services == Even if the service is publicly accessible, and is used to share information with the world, parts of the it may be restricted by their respective owner. * [https://wiki.duckcorp.org/ public wiki] (with ACLs) * [http://photos.duckcorp.org/ public photo gallery] (with ACLs) * [https://projects.duckcorp.org/ public issue tracker] (with ACLs) * [https://rcs.duckcorp.org/ public VCS accès] (with web viewers) * [http://debian.duckcorp.org/ public Debian repository] 661c3ed7eb1714a1caa2ecc1481104df341e3263 117 116 2010-06-22T12:42:55Z Duck 2 wikitext text/x-wiki Here is a short overview of the services provided by DuckCorp. Our services are supervised and important data are saved regulary. == Shared Users Services == Even if the service is publicly accessible, and is used to share information with the world, parts of the it may be restricted by their respective owner. * [https://wiki.duckcorp.org/ public wiki] (with ACLs) * [http://photos.duckcorp.org/ public photo gallery] (with ACLs) * [https://projects.duckcorp.org/ public issue tracker] (with ACLs) * [https://rcs.duckcorp.org/ public VCS accès] (with web viewers) * [http://debian.duckcorp.org/ public Debian repository] == Public Services == * a stratum 2 NTP server, to setup time on your machines, and also part of the [http://www.pool.ntp.org/en/ NTP Pool Project] * a dictionnary server, using the DICT protocol, and with a [http://dico.duckcorp.org/ web interface] == Users Services == * Network facilities: ** DNS hosting (MX1/MX2) ** IPv6 tunnels * Communication facilities: ** mail hosting (user controlled antispam, antivirus, flexible quotas, SIEVE filtering, webmails, ...) ** mailing-lists hosting ** FTP server ** IRC world: *** IRC Network (with web gateway) *** IRC bouncer *** IRC to IM gateway (to connect to ICQ/AIM/YM!/... through an IRC interface) ** XMPP (Jabber) Network (using the 'milkypond.org' domain, or a user domain) ** Triboune Libre ** SAFT * Application facilities: ** web hosting, with various possibilities for web programming (SSI, PHP, Perl, Python, Ruby, ...), and stats ** VCS hosting: git, SVN, BZR ** shell access (site admin, run custom scripts, screen for text-mode geeks, ...) (for trusted users only) * Databases facilities: ** PostgreSQL ** MySQL ** LDAP c3c19a069247f5fa3ed01340ca7d83c8c824f4e4 118 117 2010-06-22T12:46:03Z Duck 2 wikitext text/x-wiki Here is a short overview of the services provided by DuckCorp. Our services are supervised and important data are saved regulary. == Public Services == * a stratum 2 NTP server, to setup time on your machines, and also part of the [http://www.pool.ntp.org/en/ NTP Pool Project] * a dictionnary server, using the DICT protocol, and with a [http://dico.duckcorp.org/ web interface] == Shared Users Services == Even if the service is publicly accessible, and is used to share information with the world, parts of the it may be restricted by their respective owner. * [https://wiki.duckcorp.org/ public wiki] (with ACLs) * [http://photos.duckcorp.org/ public photo gallery] (with ACLs) * [https://projects.duckcorp.org/ public issue tracker] (with ACLs) * [https://rcs.duckcorp.org/ public VCS accès] (with web viewers) * [http://debian.duckcorp.org/ public Debian repository] == Users Services == * Network facilities: ** DNS hosting (MX1/MX2) ** IPv6 tunnels * Communication facilities: ** mail hosting (user controlled antispam, antivirus, flexible quotas, SIEVE filtering, webmails, ...) ** mailing-lists hosting ** FTP server ** IRC world: *** IRC Network (with web gateway) *** IRC bouncer *** IRC to IM gateway (to connect to ICQ/AIM/YM!/... through an IRC interface) ** XMPP (Jabber) Network (using the 'milkypond.org' domain, or a user domain) ** Triboune Libre ** SAFT * Application facilities: ** web hosting, with various possibilities for web programming (SSI, PHP, Perl, Python, Ruby, ...), and stats ** VCS hosting: git, SVN, BZR ** shell access (site admin, run custom scripts, screen for text-mode geeks, ...) (for trusted users only) * Databases facilities: ** PostgreSQL ** MySQL ** LDAP ef57ea67c0913af6fcd770f563259297f4624449 119 118 2010-06-22T12:48:34Z Duck 2 wikitext text/x-wiki Here is a short overview of the services provided by DuckCorp. Our services are supervised and important data are saved regulary. == Public Services == * a stratum 2 NTP server, to setup time on your machines, and also part of the [http://www.pool.ntp.org/en/ NTP Pool Project] * a dictionnary server, using the DICT protocol, and with a [http://dico.duckcorp.org/ web interface] == Shared Users Services == Even if the service is publicly accessible, and is used to share information with the world, parts of the it may be restricted by their respective owner. * [ftp://ftp.duckcorp.org/ public FTP server] (with ACLs) * [https://wiki.duckcorp.org/ public wiki] (with ACLs) * [https://projects.duckcorp.org/ public issue tracker] (with ACLs) * [https://rcs.duckcorp.org/ public VCS accès] (with web viewers) * [http://debian.duckcorp.org/ public Debian repository] * [http://photos.duckcorp.org/ public photo gallery] (with ACLs) == Users Services == * Network facilities: ** DNS hosting (MX1/MX2) ** IPv6 tunnels * Communication facilities: ** mail hosting (user controlled antispam, antivirus, flexible quotas, SIEVE filtering, webmails, ...) ** mailing-lists hosting ** IRC world: *** IRC Network (with web gateway) *** IRC bouncer *** IRC to IM gateway (to connect to ICQ/AIM/YM!/... through an IRC interface) ** XMPP (Jabber) Network (using the 'milkypond.org' domain, or a user domain) ** Triboune Libre ** SAFT * Application facilities: ** web hosting, with various possibilities for web programming (SSI, PHP, Perl, Python, Ruby, ...), and stats ** VCS hosting: git, SVN, BZR ** shell access (site admin, run custom scripts, screen for text-mode geeks, ...) (for trusted users only) * Databases facilities: ** PostgreSQL ** MySQL ** LDAP 908bb6216446c499c12e6c885e5d3ae5e88f01c3 120 119 2010-06-22T12:48:51Z Duck 2 /* Shared Users Services */ wikitext text/x-wiki Here is a short overview of the services provided by DuckCorp. Our services are supervised and important data are saved regulary. == Public Services == * a stratum 2 NTP server, to setup time on your machines, and also part of the [http://www.pool.ntp.org/en/ NTP Pool Project] * a dictionnary server, using the DICT protocol, and with a [http://dico.duckcorp.org/ web interface] == Shared Users Services == Even if the service is publicly accessible, and is used to share information with the world, parts of the it may be restricted by their respective owner. * [ftp://ftp.duckcorp.org/ public FTP server] (with ACLs) * [https://wiki.duckcorp.org/ public wiki] (with ACLs) * [https://projects.duckcorp.org/ public issue tracker] (with ACLs) * [https://rcs.duckcorp.org/ public VCS access] (with web viewers) * [http://debian.duckcorp.org/ public Debian repository] * [http://photos.duckcorp.org/ public photo gallery] (with ACLs) == Users Services == * Network facilities: ** DNS hosting (MX1/MX2) ** IPv6 tunnels * Communication facilities: ** mail hosting (user controlled antispam, antivirus, flexible quotas, SIEVE filtering, webmails, ...) ** mailing-lists hosting ** IRC world: *** IRC Network (with web gateway) *** IRC bouncer *** IRC to IM gateway (to connect to ICQ/AIM/YM!/... through an IRC interface) ** XMPP (Jabber) Network (using the 'milkypond.org' domain, or a user domain) ** Triboune Libre ** SAFT * Application facilities: ** web hosting, with various possibilities for web programming (SSI, PHP, Perl, Python, Ruby, ...), and stats ** VCS hosting: git, SVN, BZR ** shell access (site admin, run custom scripts, screen for text-mode geeks, ...) (for trusted users only) * Databases facilities: ** PostgreSQL ** MySQL ** LDAP 3eaa0020b6f88289e3da95b759539fa11b59acf8 121 120 2010-06-22T12:56:23Z Duck 2 /* Users Services */ wikitext text/x-wiki Here is a short overview of the services provided by DuckCorp. Our services are supervised and important data are saved regulary. == Public Services == * a stratum 2 NTP server, to setup time on your machines, and also part of the [http://www.pool.ntp.org/en/ NTP Pool Project] * a dictionnary server, using the DICT protocol, and with a [http://dico.duckcorp.org/ web interface] == Shared Users Services == Even if the service is publicly accessible, and is used to share information with the world, parts of the it may be restricted by their respective owner. * [ftp://ftp.duckcorp.org/ public FTP server] (with ACLs) * [https://wiki.duckcorp.org/ public wiki] (with ACLs) * [https://projects.duckcorp.org/ public issue tracker] (with ACLs) * [https://rcs.duckcorp.org/ public VCS access] (with web viewers) * [http://debian.duckcorp.org/ public Debian repository] * [http://photos.duckcorp.org/ public photo gallery] (with ACLs) == Users Services == * Network facilities: ** DNS hosting (MX1/MX2) ** IPv6 tunnels ** IP over DNS tunnels * Communication facilities: ** mail hosting (user controlled antispam, antivirus, flexible quotas, SIEVE filtering, webmails, ...) ** mailing-lists hosting ** IRC world: *** IRC Network (with web gateway) *** IRC bouncer *** IRC to IM gateway (to connect to ICQ/AIM/YM!/... through an IRC interface) ** XMPP (Jabber) Network (using the 'milkypond.org' domain, or a user domain) ** Triboune Libre ** SAFT * Application facilities: ** web hosting, with various possibilities for web programming (SSI, PHP, Perl, Python, Ruby, ...), and stats ** VCS hosting: git, SVN, BZR ** shell access (site admin, run custom scripts, screen for text-mode geeks, ...) (for trusted users only) * Databases facilities: ** PostgreSQL ** MySQL ** LDAP 4f8cbfdd1696c2f10f8b80874f556355f81f1dfc 129 121 2010-10-30T20:58:44Z Duck 2 /* Users Services */ wikitext text/x-wiki Here is a short overview of the services provided by DuckCorp. Our services are supervised and important data are saved regulary. == Public Services == * a stratum 2 NTP server, to setup time on your machines, and also part of the [http://www.pool.ntp.org/en/ NTP Pool Project] * a dictionnary server, using the DICT protocol, and with a [http://dico.duckcorp.org/ web interface] == Shared Users Services == Even if the service is publicly accessible, and is used to share information with the world, parts of the it may be restricted by their respective owner. * [ftp://ftp.duckcorp.org/ public FTP server] (with ACLs) * [https://wiki.duckcorp.org/ public wiki] (with ACLs) * [https://projects.duckcorp.org/ public issue tracker] (with ACLs) * [https://rcs.duckcorp.org/ public VCS access] (with web viewers) * [http://debian.duckcorp.org/ public Debian repository] * [http://photos.duckcorp.org/ public photo gallery] (with ACLs) == Users Services == * Network facilities: ** DNS hosting (NS1/NS2) ** IPv6 tunnels ** IP over DNS tunnels * Communication facilities: ** mail hosting (MX1/MX2, user controlled antispam, antivirus, flexible quotas, SIEVE filtering, webmails, ...) ** mailing-lists hosting ** IRC world: *** IRC Network (with web gateway) *** IRC bouncer *** IRC to IM gateway (to connect to ICQ/AIM/YM!/... through an IRC interface) ** XMPP (Jabber) Network (using the 'milkypond.org' domain, or a user domain) ** Triboune Libre ** SAFT * Application facilities: ** web hosting, with various possibilities for web programming (SSI, PHP, Perl, Python, Ruby, ...), and stats ** VCS hosting: git, SVN, BZR ** shell access (site admin, run custom scripts, screen for text-mode geeks, ...) (for trusted users only) * Databases facilities: ** PostgreSQL ** MySQL ** LDAP 4c9bc580a335aa1d1ec66d3f8e31b899cab6c505 130 129 2010-10-30T21:45:20Z Duck 2 /* Users Services */ wikitext text/x-wiki Here is a short overview of the services provided by DuckCorp. Our services are supervised and important data are saved regulary. == Public Services == * a stratum 2 NTP server, to setup time on your machines, and also part of the [http://www.pool.ntp.org/en/ NTP Pool Project] * a dictionnary server, using the DICT protocol, and with a [http://dico.duckcorp.org/ web interface] == Shared Users Services == Even if the service is publicly accessible, and is used to share information with the world, parts of the it may be restricted by their respective owner. * [ftp://ftp.duckcorp.org/ public FTP server] (with ACLs) * [https://wiki.duckcorp.org/ public wiki] (with ACLs) * [https://projects.duckcorp.org/ public issue tracker] (with ACLs) * [https://rcs.duckcorp.org/ public VCS access] (with web viewers) * [http://debian.duckcorp.org/ public Debian repository] * [http://photos.duckcorp.org/ public photo gallery] (with ACLs) == Users Services == * Network facilities: ** DNS hosting (NS1/NS2, DNSSEC) ** IPv6 tunnels ** NSTX (IP over DNS tunnels) * Communication facilities: ** mail hosting (MX1/MX2, user controlled antispam, antivirus, flexible quotas, SIEVE filtering, webmails, ...) ** mailing-lists hosting ** IRC world: *** IRC Network (with web gateway) *** IRC bouncer *** IRC to IM gateway (to connect to ICQ/AIM/YM!/... through an IRC interface) ** XMPP (Jabber) Network (using the 'milkypond.org' domain, or a user domain) ** Triboune Libre ** SAFT * Application facilities: ** web hosting, with various possibilities for web programming (SSI, PHP, Perl, Python, Ruby, ...), and stats ** VCS hosting: git, SVN, BZR ** shell access (site admin, run custom scripts, screen for text-mode geeks, ...) (for trusted users only) * Databases facilities: ** PostgreSQL ** MySQL ** LDAP 38f81827be76f5684611a9b6a86dd4340b58d97f 131 130 2010-10-30T21:45:45Z Duck 2 /* Public Services */ wikitext text/x-wiki Here is a short overview of the services provided by DuckCorp. Our services are supervised and important data are saved regulary. == Public Services == * a stratum 2 NTP server, to setup time on your machines, and also part of the [http://www.pool.ntp.org/en/ NTP Pool Project] * a dictionnary server, using the DICT protocol, provided with a [http://dico.duckcorp.org/ web interface] == Shared Users Services == Even if the service is publicly accessible, and is used to share information with the world, parts of the it may be restricted by their respective owner. * [ftp://ftp.duckcorp.org/ public FTP server] (with ACLs) * [https://wiki.duckcorp.org/ public wiki] (with ACLs) * [https://projects.duckcorp.org/ public issue tracker] (with ACLs) * [https://rcs.duckcorp.org/ public VCS access] (with web viewers) * [http://debian.duckcorp.org/ public Debian repository] * [http://photos.duckcorp.org/ public photo gallery] (with ACLs) == Users Services == * Network facilities: ** DNS hosting (NS1/NS2, DNSSEC) ** IPv6 tunnels ** NSTX (IP over DNS tunnels) * Communication facilities: ** mail hosting (MX1/MX2, user controlled antispam, antivirus, flexible quotas, SIEVE filtering, webmails, ...) ** mailing-lists hosting ** IRC world: *** IRC Network (with web gateway) *** IRC bouncer *** IRC to IM gateway (to connect to ICQ/AIM/YM!/... through an IRC interface) ** XMPP (Jabber) Network (using the 'milkypond.org' domain, or a user domain) ** Triboune Libre ** SAFT * Application facilities: ** web hosting, with various possibilities for web programming (SSI, PHP, Perl, Python, Ruby, ...), and stats ** VCS hosting: git, SVN, BZR ** shell access (site admin, run custom scripts, screen for text-mode geeks, ...) (for trusted users only) * Databases facilities: ** PostgreSQL ** MySQL ** LDAP 3f16ea1cfe732604fe77357f502dc0ddd3df4397 144 131 2010-10-31T00:30:25Z Duck 2 moved [[AvailableServices]] to [[Services]] wikitext text/x-wiki Here is a short overview of the services provided by DuckCorp. Our services are supervised and important data are saved regulary. == Public Services == * a stratum 2 NTP server, to setup time on your machines, and also part of the [http://www.pool.ntp.org/en/ NTP Pool Project] * a dictionnary server, using the DICT protocol, provided with a [http://dico.duckcorp.org/ web interface] == Shared Users Services == Even if the service is publicly accessible, and is used to share information with the world, parts of the it may be restricted by their respective owner. * [ftp://ftp.duckcorp.org/ public FTP server] (with ACLs) * [https://wiki.duckcorp.org/ public wiki] (with ACLs) * [https://projects.duckcorp.org/ public issue tracker] (with ACLs) * [https://rcs.duckcorp.org/ public VCS access] (with web viewers) * [http://debian.duckcorp.org/ public Debian repository] * [http://photos.duckcorp.org/ public photo gallery] (with ACLs) == Users Services == * Network facilities: ** DNS hosting (NS1/NS2, DNSSEC) ** IPv6 tunnels ** NSTX (IP over DNS tunnels) * Communication facilities: ** mail hosting (MX1/MX2, user controlled antispam, antivirus, flexible quotas, SIEVE filtering, webmails, ...) ** mailing-lists hosting ** IRC world: *** IRC Network (with web gateway) *** IRC bouncer *** IRC to IM gateway (to connect to ICQ/AIM/YM!/... through an IRC interface) ** XMPP (Jabber) Network (using the 'milkypond.org' domain, or a user domain) ** Triboune Libre ** SAFT * Application facilities: ** web hosting, with various possibilities for web programming (SSI, PHP, Perl, Python, Ruby, ...), and stats ** VCS hosting: git, SVN, BZR ** shell access (site admin, run custom scripts, screen for text-mode geeks, ...) (for trusted users only) * Databases facilities: ** PostgreSQL ** MySQL ** LDAP 3f16ea1cfe732604fe77357f502dc0ddd3df4397 146 144 2010-10-31T00:31:39Z Duck 2 wikitext text/x-wiki Here is a short overview of the services provided by DuckCorp. Our services are supervised and important data are saved regulary. == Public Services == * a stratum 2 NTP server, to setup time on your machines, and also part of the [http://www.pool.ntp.org/en/ NTP Pool Project] * a dictionnary server, using the DICT protocol, provided with a [http://dico.duckcorp.org/ web interface] == Shared Users Services == Even if the service is publicly accessible, and is used to share information with the world, parts of the it may be restricted by their respective owner. * [ftp://ftp.duckcorp.org/ public FTP server] (with ACLs) * [https://wiki.duckcorp.org/ public wiki] (with ACLs) * [https://projects.duckcorp.org/ public issue tracker] (with ACLs) * [https://rcs.duckcorp.org/ public VCS access] (with web viewers) * [http://debian.duckcorp.org/ public Debian repository] * [http://photos.duckcorp.org/ public photo gallery] (with ACLs) == Users Services == * Network facilities: ** DNS hosting (NS1/NS2, DNSSEC) ** IPv6 tunnels ** [[Services/NSTX|NSTX (IP over DNS tunnels)]] * Communication facilities: ** mail hosting (MX1/MX2, user controlled antispam, antivirus, flexible quotas, SIEVE filtering, webmails, ...) ** mailing-lists hosting ** IRC world: *** IRC Network (with web gateway) *** IRC bouncer *** IRC to IM gateway (to connect to ICQ/AIM/YM!/... through an IRC interface) ** XMPP (Jabber) Network (using the 'milkypond.org' domain, or a user domain) ** Triboune Libre ** SAFT * Application facilities: ** web hosting, with various possibilities for web programming (SSI, PHP, Perl, Python, Ruby, ...), and stats ** VCS hosting: git, SVN, BZR ** shell access (site admin, run custom scripts, screen for text-mode geeks, ...) (for trusted users only) * Databases facilities: ** PostgreSQL ** MySQL ** LDAP c27323ac09494262db1d2149bc20ed6ab4e86207 148 146 2010-11-01T22:33:53Z Duck 2 /* Users Services */ wikitext text/x-wiki Here is a short overview of the services provided by DuckCorp. Our services are supervised and important data are saved regulary. == Public Services == * a stratum 2 NTP server, to setup time on your machines, and also part of the [http://www.pool.ntp.org/en/ NTP Pool Project] * a dictionnary server, using the DICT protocol, provided with a [http://dico.duckcorp.org/ web interface] == Shared Users Services == Even if the service is publicly accessible, and is used to share information with the world, parts of the it may be restricted by their respective owner. * [ftp://ftp.duckcorp.org/ public FTP server] (with ACLs) * [https://wiki.duckcorp.org/ public wiki] (with ACLs) * [https://projects.duckcorp.org/ public issue tracker] (with ACLs) * [https://rcs.duckcorp.org/ public VCS access] (with web viewers) * [http://debian.duckcorp.org/ public Debian repository] * [http://photos.duckcorp.org/ public photo gallery] (with ACLs) == Users Services == * Network facilities: ** [[Services/DNS|DNS hosting]] (NS1/NS2, DNSSEC) ** IPv6 tunnels ** [[Services/NSTX|NSTX]] (IP over DNS tunnels) * Communication facilities: ** mail hosting (MX1/MX2, user controlled antispam, antivirus, flexible quotas, SIEVE filtering, webmails, ...) ** mailing-lists hosting ** IRC world: *** IRC Network (with web gateway) *** IRC bouncer *** IRC to IM gateway (to connect to ICQ/AIM/YM!/... through an IRC interface) ** XMPP (Jabber) Network (using the 'milkypond.org' domain, or a user domain) ** Triboune Libre ** SAFT * Application facilities: ** web hosting, with various possibilities for web programming (SSI, PHP, Perl, Python, Ruby, ...), and stats ** VCS hosting: git, SVN, BZR ** shell access (site admin, run custom scripts, screen for text-mode geeks, ...) (for trusted users only) * Databases facilities: ** PostgreSQL ** MySQL ** LDAP 19f75fb379652456248de5192b7c8bc0c10e5228 0 32 122 97 2010-08-05T17:19:47Z Duck 2 /* Failure Expenses */ wikitext text/x-wiki Let's be transparent about money too. Pure financial contributions are not listed here, but in the [[DcDonation|donation page]]. == Regular Expenses == This does not account for external sponsorship, but contributions by members. {| class="wikitable" style="text-align: center; width: 100%;" ! Object !! Amount !! Sponsor !! Comments |- | DuckCorp DNS domain || ~15€/year || Duck |- | MilkyPond DNS domain || ~15€/year || Rtp |- | Toushirou's housing || 41.56€/month || Duck || collocation with Yok (considering network switch and APC powerswitch shared rack space) |} Note: this does not take into account the ADSL line used by Elwing and Daneel, coupled in the same offer providing the VM Thorfinn, as it is used privately. == Exceptional Expenses == Note: this does not take into account expenses before 2006 because most historical data were lost. === Improvement Expenses === {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Object !! Amount !! Sponsor !! Comments |- | 2010-05-22 || more memory for Toushirou (2*2GB) || 105€ || Duck || PC2-5300/5400 2*2GB memory in a correct brand could not be found anymore, so we had to take PC2-6400 instead |- | 2007-10 || replacement server (Orfeo-NG) || 1210€ || Duck || Sun Fire X4100 |- | 2007-05 || new server (Toushirou) || 1709.08€ || Duck || Supermicro PDSMI+ / Core 2 Duo E6600 / 2GB PC5400 / 3ware 9550SX4LP / 4x HD SATA II 250GB |} {{todo}} finish === Failure Expenses === {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Object !! Amount !! Sponsor !! Comments |- | 2010-01-06 || spare disk || 73€ || Duck || avoided tragedy when both disks in Daneel died at one week interval |- | 2007-09-29 || replacement server (Daneel-ng) || 534.90€ || Duck || machine too old and previous disk died horribly |- | 2006-01 || 300GB HD for Daneel (backup) || || AnonymousDonnor1 || replaced since then |} 6faa97eb68ba51ed386302a740299b2729cd5ce3 123 122 2010-08-05T17:21:08Z Duck 2 /* Improvement Expenses */ wikitext text/x-wiki Let's be transparent about money too. Pure financial contributions are not listed here, but in the [[DcDonation|donation page]]. == Regular Expenses == This does not account for external sponsorship, but contributions by members. {| class="wikitable" style="text-align: center; width: 100%;" ! Object !! Amount !! Sponsor !! Comments |- | DuckCorp DNS domain || ~15€/year || Duck |- | MilkyPond DNS domain || ~15€/year || Rtp |- | Toushirou's housing || 41.56€/month || Duck || collocation with Yok (considering network switch and APC powerswitch shared rack space) |} Note: this does not take into account the ADSL line used by Elwing and Daneel, coupled in the same offer providing the VM Thorfinn, as it is used privately. == Exceptional Expenses == Note: this does not take into account expenses before 2006 because most historical data were lost. === Improvement Expenses === {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Object !! Amount !! Sponsor !! Comments |- | 2010-05-22 || more memory for Toushirou (2*2GB) || 105€ || Duck || PC2-5300/5400 2*2GB memory in a correct brand could not be found anymore, so we had to take PC2-6400 instead |- | 2007-10 || replacement server (Orfeo-NG) || 1210€ || Duck || Sun Fire X4100 |- | 2007-05 || new server (Toushirou) || 1709.08€ || Duck || Supermicro PDSMI+ / Core 2 Duo E6600 / 2GB PC5400 / 3ware 9550SX4LP / 4x HD SATA II 250GB |} === Failure Expenses === {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Object !! Amount !! Sponsor !! Comments |- | 2010-01-06 || spare disk || 73€ || Duck || avoided tragedy when both disks in Daneel died at one week interval |- | 2007-09-29 || replacement server (Daneel-ng) || 534.90€ || Duck || machine too old and previous disk died horribly |- | 2006-01 || 300GB HD for Daneel (backup) || || AnonymousDonnor1 || replaced since then |} 7fdd00ba1a9488981409357822ef0a7eed826dbc 124 123 2010-08-05T17:24:57Z Duck 2 /* Exceptional Expenses */ wikitext text/x-wiki Let's be transparent about money too. Pure financial contributions are not listed here, but in the [[DcDonation|donation page]]. == Regular Expenses == This does not account for external sponsorship, but contributions by members. {| class="wikitable" style="text-align: center; width: 100%;" ! Object !! Amount !! Sponsor !! Comments |- | DuckCorp DNS domain || ~15€/year || Duck |- | MilkyPond DNS domain || ~15€/year || Rtp |- | Toushirou's housing || 41.56€/month || Duck || collocation with Yok (considering network switch and APC powerswitch shared rack space) |} Note: this does not take into account the ADSL line used by Elwing and Daneel, coupled in the same offer providing the VM Thorfinn, as it is used privately. == Exceptional Expenses == Note: this does not take into account expenses before 2006 because most historical data were lost. Note: Elwing and Daneel are used privately. Elwing is not taken into account, as most services are not used for DC (and since begining of 2010 are moving progresively elsewhere), but Daneel is, as a big part of the backup is for DC's machines. === Improvement Expenses === {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Object !! Amount !! Sponsor !! Comments |- | 2010-05-22 || more memory for Toushirou (2*2GB) || 105€ || Duck || PC2-5300/5400 2*2GB memory in a correct brand could not be found anymore, so we had to take PC2-6400 instead |- | 2007-10 || replacement server (Orfeo-NG) || 1210€ || Duck || Sun Fire X4100 |- | 2007-05 || new server (Toushirou) || 1709.08€ || Duck || Supermicro PDSMI+ / Core 2 Duo E6600 / 2GB PC5400 / 3ware 9550SX4LP / 4x HD SATA II 250GB |} === Failure Expenses === {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Object !! Amount !! Sponsor !! Comments |- | 2010-01-06 || spare disk || 73€ || Duck || avoided tragedy when both disks in Daneel died at one week interval |- | 2007-09-29 || replacement server (Daneel-ng) || 534.90€ || Duck || machine too old and previous disk died horribly |- | 2006-01 || 300GB HD for Daneel (backup) || || AnonymousDonnor1 || replaced since then |} 2710c910f8fa1b4b54761969cef88f4eec02dadd 125 124 2010-08-06T11:24:48Z Duck 2 /* Exceptional Expenses */ wikitext text/x-wiki Let's be transparent about money too. Pure financial contributions are not listed here, but in the [[DcDonation|donation page]]. == Regular Expenses == This does not account for external sponsorship, but contributions by members. {| class="wikitable" style="text-align: center; width: 100%;" ! Object !! Amount !! Sponsor !! Comments |- | DuckCorp DNS domain || ~15€/year || Duck |- | MilkyPond DNS domain || ~15€/year || Rtp |- | Toushirou's housing || 41.56€/month || Duck || collocation with Yok (considering network switch and APC powerswitch shared rack space) |} Note: this does not take into account the ADSL line used by Elwing and Daneel, coupled in the same offer providing the VM Thorfinn, as it is used privately. == Exceptional Expenses == Note: this does not take into account expenses before 2006 because most historical data were lost. Note: Elwing and Daneel are used privately. Elwing is not taken into account, as most services are not used for DC (and since begining of 2010 are moving progresively elsewhere), but Daneel is, as a big part of the backup is for DC's machines. === Improvement Expenses === {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Object !! Amount !! Sponsor !! Comments |- | 2010-05-22 || more memory for Toushirou (2*2GB) || 105€ || Duck || PC2-5300/5400 2*2GB memory in a correct brand could not be found anymore, so we had to take PC2-6400 instead |- | 2007-10 || replacement server (Orfeo-NG) || 1210€ || Duck || Sun Fire X4100 |- | 2007-05 || new server (Toushirou) || 1709.08€ || Duck || Supermicro PDSMI+ / Core 2 Duo E6600 / 2GB PC5400 / 3ware 9550SX4LP / 4x HD SATA II 250GB |} === Failure Expenses === {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Object !! Amount !! Sponsor !! Comments |- | 2010-01-06 || spare disk || 73€ || Duck || avoided tragedy when both disks in Daneel died at one week interval |- | 2007-09-29 || replacement server (Daneel-ng) || 534.90€ || Duck || machine too old and previous disk died horribly |- | 2006-01 || 300GB HD for Daneel (backup) || || AnonymousDonnor1 || replaced since then |} === Other Expenses === {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Object !! Amount !! Sponsor !! Comments |- | 2010-06-29 || taxi || 26.20€ || Duck || Nerim bought Sivit, moving Toushirou to their new suite at Equinix PA3 (CBV->STD) |} d83e176f327abc01a33bcb92a7c46bb8528ceb51 0 33 126 85 2010-10-23T11:45:44Z Duck 2 /* What can you Contribute ? */ wikitext text/x-wiki DuckCorp is built and maintained by volunteers, mostly with their own money. The services are totaly free of charge for all users, but you may wish to contribute to help us keep it working well and improve. == How to Contribute ? == You can help us with: * sponsoring: if you can host a machine and/or provide connectivity * equipements: see the list of possible improvements below * money: you can send us money which will be used in the association: ** by check (see the duckcorp.org whois for Duck's postal address, or ask him by mail or IRC) ** by Paypal to duck@duckcorp.org == What can you Contribute ? == Here are ideas on which to contribute: * [[DcExpenses#Regular_Expenses|regular expenses]] * [???] buy a new machine, to provide: VMs, more services redondancy, ... (hardware needed not yet evaluated, more on this later) * [~120€] add a battery backup unit for Toushirou's 3ware card (for more data security, as datacenters tends to be less and less reliable) * [??? (quite expensive)] change Orfeo's backplane to have 4 disks slot instead of 2, and add 2 new disks (in a new RAID 1 array), planned at least 120GB capacity (2.5″ 10000 RPM SAS, like the other ones) (can be bought anywhere, but proprietary braquets needed) == List of Previous Contributions == Only pure financial contributions are listed here; equipments and sponsored purchases are listed on the [[DcExpenses|DuckCorp expenses page]]. {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Amount !! Donnor !! Comments |- | 2010-05-16 || 42€ || Chloé |} Note: early contributions in the CoinNetwork projects are not taken into account, as most information is lost. 165f6f53a46a7aa5cce0ea817a954327ee3458d0 127 126 2010-10-23T12:27:39Z Duck 2 /* What can you Contribute ? */ wikitext text/x-wiki DuckCorp is built and maintained by volunteers, mostly with their own money. The services are totaly free of charge for all users, but you may wish to contribute to help us keep it working well and improve. == How to Contribute ? == You can help us with: * sponsoring: if you can host a machine and/or provide connectivity * equipements: see the list of possible improvements below * money: you can send us money which will be used in the association: ** by check (see the duckcorp.org whois for Duck's postal address, or ask him by mail or IRC) ** by Paypal to duck@duckcorp.org == What can you Contribute ? == Here are ideas on which to contribute: * [[DcExpenses#Regular_Expenses|regular expenses]] * [???] buy a new machine, to provide: VMs, more services redondancy, ... (needed hardware not yet evaluated, more on this later) * [~120€] add a battery backup unit for Toushirou's 3ware card (for more data security, as datacenters tends to be less and less reliable) * [??? (quite expensive)] change Orfeo's backplane to have 4 disks slot instead of 2, and add 2 new disks (in a new RAID 1 array), planned at least 120GB capacity (2.5″ 10000 RPM SAS, like the other ones) (can be bought anywhere, but proprietary braquets needed) == List of Previous Contributions == Only pure financial contributions are listed here; equipments and sponsored purchases are listed on the [[DcExpenses|DuckCorp expenses page]]. {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Amount !! Donnor !! Comments |- | 2010-05-16 || 42€ || Chloé |} Note: early contributions in the CoinNetwork projects are not taken into account, as most information is lost. 8334991f2ad103961582bfe8c6b17aab86ed22c2 0 1 132 91 2010-10-30T22:32:37Z Duck 2 wikitext text/x-wiki {|border="0" cellspacing="0" cellpadding="0" style="padding:0px; margin:0px; height:100%; background:transparent; " | {{:Main Page/Introduction}} |- {{#if: [[User:Duck|duck]]| {| width=100% | width=50% valign=top style="height:100%;" | {{:Main Page/Association}} | width=50% valign=top style="height:100%;" | {{:Main Page/Technical}} |} }} |} 06a35e5421aa006d970be8ea02c9ba436b90bc05 133 132 2010-10-30T23:24:11Z Duck 2 wikitext text/x-wiki {|border="0" cellspacing="0" cellpadding="0" style="padding:0px; margin:0px; height:100%; background:transparent; " | {{:Main Page/Introduction}} |- {{#if: {{#userid}}| {| width=100% | width=50% valign=top style="height:100%;" | {{:Main Page/Association}} | width=50% valign=top style="height:100%;" | {{:Main Page/Technical}} |} }} |} 1f2677a4610708d20fcc981e6d47203edc261ebf 135 133 2010-10-30T23:41:56Z Duck 2 wikitext text/x-wiki {|border="0" cellspacing="0" cellpadding="0" style="padding:0px; margin:0px; height:100%; background:transparent; " | {{:Main Page/Introduction}} |} {{:Main Page/UserPanel}} {{#if: {{#userid:}}|{{:Main Page/UserPanel}}|{{:Main Page/AlienPanel}}}} 8926083dc723f6c4aae83f7bb42ee7df0c975c4d 136 135 2010-10-30T23:42:09Z Duck 2 wikitext text/x-wiki {|border="0" cellspacing="0" cellpadding="0" style="padding:0px; margin:0px; height:100%; background:transparent; " | {{:Main Page/Introduction}} |} {{#if: {{#userid:}}|{{:Main Page/UserPanel}}|{{:Main Page/AlienPanel}}}} 2b0363ffab5175462a3627766bae970c53e549f4 139 136 2010-10-30T23:43:44Z Duck 2 wikitext text/x-wiki {|border="0" cellspacing="0" cellpadding="0" style="padding:0px; margin:0px; height:100%; background:transparent; width: 100%;" | {{:Main Page/Introduction}} |} {{#if: {{#userid:}}|{{:Main Page/UserPanel}}|{{:Main Page/AlienPanel}}}} 88390c9308fce0c67e8cdfe03e2ff3ac4be91aca 0 40 134 2010-10-30T23:40:51Z Duck 2 Created page with "{|border="0" cellspacing="0" cellpadding="0" style="padding:0px; margin:0px; height:100%; background:transparent; " | | width=50% valign=top style="height:100%;" | {{:Main Page/A…" wikitext text/x-wiki {|border="0" cellspacing="0" cellpadding="0" style="padding:0px; margin:0px; height:100%; background:transparent; " | | width=50% valign=top style="height:100%;" | {{:Main Page/Association}} | width=50% valign=top style="height:100%;" | {{:Main Page/Technical}} |} f59fc090ac6118b0892234388abc3d05688ab6f2 137 134 2010-10-30T23:42:56Z Duck 2 wikitext text/x-wiki {|border="0" cellspacing="0" cellpadding="0" style="padding:0px; margin:0px; height:100%; background:transparent; width: 100%;" | | width=50% valign=top style="height:100%;" | {{:Main Page/Association}} | width=50% valign=top style="height:100%;" | {{:Main Page/Technical}} |} 6db426c93f4fdd04ceeac7824e1a0de3e936e6b3 138 137 2010-10-30T23:43:11Z Duck 2 Protected "[[Main Page/UserPanel]]" ([edit=sysop] (indefinite) [move=sysop] (indefinite)) wikitext text/x-wiki {|border="0" cellspacing="0" cellpadding="0" style="padding:0px; margin:0px; height:100%; background:transparent; width: 100%;" | | width=50% valign=top style="height:100%;" | {{:Main Page/Association}} | width=50% valign=top style="height:100%;" | {{:Main Page/Technical}} |} 6db426c93f4fdd04ceeac7824e1a0de3e936e6b3 0 30 140 59 2010-10-30T23:49:27Z Duck 2 /* Key Dates */ wikitext text/x-wiki == The DuckCorp Story == DuckCorp was born in 2000, from Duck's will to construct something more personal out of the CoinNetwork student house's LAN. At that time, it was merely a simple website, advertising a few personal projects. Later, several machines, gathered with various parts from people willing to dispose of them, used the 'duckcorp.org' domain name and provided services for CoinNetwork; this was the begining of the DC's sponsoring mission. Duck then met Rtp, and they began sharing about system administration topics. As they were willing to administrate CoinNetwork better, they began working on the infrastructure and tools together. Rtp created RtpNet, and received the magical SSH key to be a full DC administrator (so do Duck for Rtpnet indeed). They developed a software prototype aimed at managing the most important services of a distributed web of servers (LMS, LDAP Management System), which helped reducing the daily burden of CoinNetwork's administration a lot. After a while working hand in hand, they both found a job and moved to a new home, still helping each other when possible. Currently, RtpNet and DuckCorp have different goals, and follow their own path. On the way, DC found friendly sponsors (in order of appearance): * Nerim (first Orfeo's housing, IPv6 block, indirect sponsor via Hivane) * Hivane (global connectivity, secondary NS and MX) * Sivit (special accomodations for Toushirou's housing and connectivity) (now Nerim again, as it was acquired recently) * Alionis (Orfeo's housing) Thanks a lot pals :-). == The MilkyPond Project == MP is an historical share of an IRC network between DC and RN when they both stopped working on the CoinNetwork project. They were willing to cooperate but with the important changes that occurred in their lives, only IRC was kept as a communication link. With time going, DC began recreating services, with the main server Orfeo being kindly sponsored by Nerim, which was used by RN and later by other associations or individuals. Nothing much is done in the name of MP until 2007, besides adding a Jabber server. In early 2007, RN hired a server, Lechat (Dédibox), and was willing to participate more in the share. At the end of the year, T1R joined to help improving the IRC Network. In September 2007, RN was not able to provide services anymore, as it was too much of a burden. Nevertheless, it is still sponsoring the ''milkypond.org'' domain since then. == Key Dates == * 2000-05-22: DuckCorp is created * 2003-04-25: IANA PEN 16829 * 2003-07-09: RtpNet is created * ~2003-10-20: RSA key exchanged between DC and RN (date is from the exif info, but Photoshop is in the way) * 2004-06-12: MilkyPond is created (after DC and RN stopped working on the CoinNetwork project) * 2005-04/05: Orfeo RAM upgraded (512Mo->1.5Go) (blocked to ~800Mo [[Media:Orfeo.duckcorp.org-memory-day.png|until highmem in kernel]]) * 2005-05: IPv6 Ready (using a tunnel) * 2005-11-17: the users' mailing-list started * 2005-11: major mail system improvements (SMTP auth, improved antispam, webdesk) * 2005-12-08: Orfeo moved from the Nerim's Ivry datacenter to the Nerim suite in the LDCOM Courbevoie datacenter * 2006-01 to 2006-06: Orfeo problems due to an [http://xfs.org/index.php/XFS_FAQ#Q:_What_is_the_issue_with_directory_corruption_in_Linux_2.6.17.3F XFS bug] * 2007-04: IPv6 Ready (native IPv6) * 2007-07: Tōshirō bought and being prepared * 2007-08-08: Nerim's boss shutdown Orfeo violently; quickly repaired and setup behind a mere ADSL (helped by Nerim friends), but BLACKOUT for most services * 2007-08-13: Tōshirō installed in the Sivit suite of the Redbus datacenter, services progressively back online * 2007-09: LDAP infrastructure (again) * 2007-12: Orfeo-NG bough and installed in Alionis suite in EQX (Equinix) datacenter * 2007-12: T1R enters MilkyPond (for the IRC network) * 2008-07: VCS rework, Portal (Restricted Access Helper), Projects Manager (Redmine) * 2009-03: Banya bot (mail gateway for DNS modification, part of the CyborgHood project) * 2009-09: Orfeo moved to [http://www.alionis.net/infra/VBO.html Alionis VBO datacenter] * 2010-03: Thorfinn acquired (Nerim VDS) * 2010-04-24: stratum 2 NTP server [http://support.ntp.org/bin/view/Servers/NtpDuckCorpOrg publicly advertised] and in the [http://www.pool.ntp.org/user/DuckCorp pool] * 2010-05-22: 10th Anniversary !!! * 2010-05-29: 10th Anniversary party with users/sponsors/friends * 2010-10: DNS TSIG and DNSSEC == Admins == * Arnau [~2004-12 to now] (fallback admin since 2010-04-27) * Duck [begining to now] (leader) * Finger [2006-07-05 to 2008-02-04] (assistant) * Mmenal [~2004-12 to ~2006-07] * Rtp [2003-10 to 2007-07-15] == Evolution == No real traces were kept, so old numbers are mere rough guess. * 2000 -> 2004 ** more than 60 users served in the [[Media:Coinnetwork resal 2001-2002.png|CoinNetwork LAN]], nearly no external services besides a basic website and IRC ** services targeted for the CoinNetwork LAN * 2004 -> 2007 ** a few users (probably around 20) and 2 entities (RtpNet and [http://www.hurdfr.org/ HurdFr]) hosted ** more Internet-oriented services (complete mail software suite, MLs, Web hosting, DBs, RCS, ...) * 2007 -> 2010 ** more users (nearly 70 users in 2010, a few not very active) and 2 more entity hosted ([http://thebrain.lautre.net/ TheBrain] and [http://www.andesi.org/ Andesi]) ** more services (Jabber, user-friendly antispam, LDAP, IPv6, ...) == Photos == Look at the [http://photos.duckcorp.org/v/duckcorp/ gallery]. a316c5d8a8028f2196baafcd9a9eace2441348d0 0 31 141 53 2010-10-31T00:09:00Z Duck 2 wikitext text/x-wiki <fdp_graph> graph DcMap { label = "DuckCorp Architecture"; fontsize = 14; overlap = false; splines = true; edge [fontsize=10.0]; labelloc = "t"; internet [label="Internet", shape=tripleoctagon]; subgraph cluster_nerim { label = "Nerim Suite\n(Equinix PA3 Datacenter)"; color = blue; labeljust = "l"; toushirou [label="Tōshirō", URL="DcArchitecture/Tōshirō"]; thorfinn [label="Thorfinn\n(Nerim Root VDS)", URL="DcArchitecture/Thorfinn"]; } cluster_nerim -- internet [label="Nerim / Hivane\nTransit", style=dashed]; subgraph cluster_alionis { label = "Alionis Suite\n(Villebon Datacenter)"; URL = "http://maps.google.com/maps/ms?ie=UTF8&hl=en&msa=0&msid=105368272885926046620.0004600d15bf1a76aa1a9&t=h&z=15"; color = black; labeljust = "l"; orfeo [label="Orfeo", URL="DcArchitecture/Orfeo"]; } cluster_alionis -- internet [label="Hivane\nTransit", style=dashed]; subgraph cluster_hq { label = "DuckCorp HQ (DuckLand)"; color = green; labeljust = "l"; elwing [label="Elwing", URL="DcArchitecture/Elwing"]; daneel [label="Daneel", URL="DcArchitecture/Daneel"]; earendil [label="Eärendil", URL="DcArchitecture/Eärendil"]; modem_dc [label="ADSL Modem\n(Linksys ADSL2MUE)", shape=box]; sw_dc [label="Switch", shape=box]; sw_dc -- {elwing earendil daneel}; elwing -- {modem_dc}; subgraph cluster_hurdfr { label = "HurdFr (DuckLand part)"; URL = "http://www.hurdfr.org/"; color = darkviolet; labeljust = "l"; amroth [label="Amroth", URL="DcArchitecture/Amroth"]; } amroth -- sw_dc; } cluster_hq -- internet [label="Nerim / Hivane\nADSL", style=dashed]; } <fdp_graph> 5035d22389b21d6d62f5c12feca3319a18993207 0 41 142 2010-10-31T00:21:23Z Duck 2 Created page with "{{Robelbox|title=Entrance Hall|theme={{{theme|3}}}}} {{Padbox}} {{warning}} This site is reserved to DuckCorp's users. You can read more about [[A bit of History|our history]], …" wikitext text/x-wiki {{Robelbox|title=Entrance Hall|theme={{{theme|3}}}}} {{Padbox}} {{warning}} This site is reserved to DuckCorp's users. You can read more about [[A bit of History|our history]], but you need to [[Special:Userlogin|authenticate]] to go further. {{Padbox/close}} {{Robelbox/close}} 6195072d8d1b3dbc96e784c171ff0987f9233ce7 143 142 2010-10-31T00:23:53Z Duck 2 Protected "[[Main Page/AlienPanel]]" ([edit=sysop] (indefinite) [move=sysop] (indefinite)) wikitext text/x-wiki {{Robelbox|title=Entrance Hall|theme={{{theme|3}}}}} {{Padbox}} {{warning}} This site is reserved to DuckCorp's users. You can read more about [[A bit of History|our history]], but you need to [[Special:Userlogin|authenticate]] to go further. {{Padbox/close}} {{Robelbox/close}} 6195072d8d1b3dbc96e784c171ff0987f9233ce7 0 43 149 2010-11-01T23:06:57Z Duck 2 Created page with "== NS1 & NS2 == DC dans provide primary or secondary DNS servers for your zones. To have your master zone modified on our servers, you can: * use our [[UserMagicalInterface]] *…" wikitext text/x-wiki == NS1 & NS2 == DC dans provide primary or secondary DNS servers for your zones. To have your master zone modified on our servers, you can: * use our [[UserMagicalInterface]] * ask administrators == DNS Security == To provide as much security as possible, DC supports the following mechanisms. === TSIG === This protocol allows a secure transfer of zones between primary and secondary servers. The DC's DNS servers support TSIG and comminication between them are always secured. The following entities are known to support TSIG and can then securely transfer zones to/from DC: * [http://www.hivane.net/ Hivane] === DNSSEC === This protocol aims at establishing a chain of trust, from the root of the DNS, to ensure response to queries on a zone has not been altered on the way. With the root zone public key, it is possible to validate the replies step by step down to your zone, for example: root public key -> ''.'' -> NS for ''org.'' -> NS for ''milkypond.org.'' -> ''irc.milkypond.org.''. Unfortunately, many DNS providers do not support DNSSEC (Gandi is one of them :-/). In order to help people work on securing their zone, and be ready when their provider is, the [http://www.isc.org/ ISC] created a solution to validating your zone, using another secure path: by publishing security associations in a special zone (''dlv.isc.org'', called the DLV Registry), which itself can be validated the normal way. This is only a stopgap, but as providers seems not to be in a hurry to do their job, DC decided to use it. DC DNS servers are able to handle the complicated procedure needed to sign a zone for you. You can just modify it the classic way, and have it signed automatically. You just need to ask us to switch the zone to the secure mode. If your provider gladly support DNSSEC, we can provide the necessary information for the chain of trust; if not, we can use the DLV registry. Beware DNS always means propagation delays, so you may have to wait a few days before the switch is completed and your zone fully secured over the whole world. 5d9c099e592dcf8b246dfd225d0d43fe5ab00cd6 151 149 2010-11-01T23:27:03Z Duck 2 /* DNSSEC */ wikitext text/x-wiki == NS1 & NS2 == DC dans provide primary or secondary DNS servers for your zones. To have your master zone modified on our servers, you can: * use our [[UserMagicalInterface]] * ask administrators == DNS Security == To provide as much security as possible, DC supports the following mechanisms. === TSIG === This protocol allows a secure transfer of zones between primary and secondary servers. The DC's DNS servers support TSIG and comminication between them are always secured. The following entities are known to support TSIG and can then securely transfer zones to/from DC: * [http://www.hivane.net/ Hivane] === DNSSEC === ==== What is DNSSEC ? ==== This protocol aims at establishing a chain of trust, from the root of the DNS, to ensure response to queries on a zone has not been altered on the way. With the root zone public key, it is possible to validate the replies step by step down to your zone, for example: root public key -> ''.'' -> NS for ''org.'' -> NS for ''milkypond.org.'' -> ''irc.milkypond.org.''. Unfortunately, many DNS providers do not support DNSSEC (Gandi is one of them :-/). In order to help people work on securing their zone, and be ready when their provider is, the [http://www.isc.org/ ISC] created a solution to validating your zone, using another secure path: by publishing security associations in a special zone (''dlv.isc.org'', called the DLV Registry), which itself can be validated the normal way. This is only a stopgap, but as providers seems not to be in a hurry to do their job, DC decided to use it. ==== How to use it for my zones ? ==== DC DNS servers are able to handle the complicated procedure needed to sign a zone for you. You can just modify it the classic way, and have it signed automatically. You just need to ask us to switch the zone to the secure mode. If your provider gladly support DNSSEC, we can provide the necessary information for the chain of trust; if not, we can use the DLV registry. Beware DNS always means propagation delays, so you may have to wait a few days before the switch is completed and your zone fully secured over the whole world. ==== How to test my zone is secured ? ==== First, you need a validating DNS server (explanations for ''bind9'' on Debian): * get the root zone public key (using this script for example: [[File:Get dns root zone key.sh]]) * add the key to your configuration (in ''/etc/bind/named.conf''): include "/etc/bind/root.keys"; * add in your global options (''/etc/bind/named.conf.options''): dnssec-enable yes; dnssec-validation yes; dnssec-lookaside auto; * restart bind The DLV Registry public key is already provided in the ''bind9'' package. Then, you can check it with the ''dig'' tool (available in the ''dnsutils'' Debian package): dig +dnssec <zone> Look at the flags: it is secured if you find the ''ad'' flag. If there is the ''aa'' flag instead, then you are interrogating on of the authoritative DNS servers for the zone, it is also secure, but better test it on another server to be sure it is propagated. {{warning}} If you check an entry of your zone which is a CNAME, beware the CNAME is resolved and if the destination name cannot be validated, then your entry won't either. 8527c8eef92e0760556c388a7b67113f5f0d71d6 152 151 2010-11-01T23:28:59Z Duck 2 /* What is DNSSEC ? */ wikitext text/x-wiki == NS1 & NS2 == DC dans provide primary or secondary DNS servers for your zones. To have your master zone modified on our servers, you can: * use our [[UserMagicalInterface]] * ask administrators == DNS Security == To provide as much security as possible, DC supports the following mechanisms. === TSIG === This protocol allows a secure transfer of zones between primary and secondary servers. The DC's DNS servers support TSIG and comminication between them are always secured. The following entities are known to support TSIG and can then securely transfer zones to/from DC: * [http://www.hivane.net/ Hivane] === DNSSEC === ==== What is DNSSEC ? ==== This protocol aims at establishing a chain of trust, from the root of the DNS, to ensure response to queries on a zone has not been altered on the way. With the root zone public key, it is possible to validate the replies step by step down to your zone, for example: root public key -> ''.'' zone -> NS for ''org.'' -> ''org.'' zone -> NS for ''milkypond.org.'' -> ''milkypond.org'' zone -> ''irc.milkypond.org.''. Unfortunately, many DNS providers do not support DNSSEC (Gandi is one of them :-/). In order to help people work on securing their zone, and be ready when their provider is, the [http://www.isc.org/ ISC] created a solution to validating your zone, using another secure path: by publishing security associations in a special zone (''dlv.isc.org'', called the DLV Registry), which itself can be validated the normal way. This is only a stopgap, but as providers seems not to be in a hurry to do their job, DC decided to use it. ==== How to use it for my zones ? ==== DC DNS servers are able to handle the complicated procedure needed to sign a zone for you. You can just modify it the classic way, and have it signed automatically. You just need to ask us to switch the zone to the secure mode. If your provider gladly support DNSSEC, we can provide the necessary information for the chain of trust; if not, we can use the DLV registry. Beware DNS always means propagation delays, so you may have to wait a few days before the switch is completed and your zone fully secured over the whole world. ==== How to test my zone is secured ? ==== First, you need a validating DNS server (explanations for ''bind9'' on Debian): * get the root zone public key (using this script for example: [[File:Get dns root zone key.sh]]) * add the key to your configuration (in ''/etc/bind/named.conf''): include "/etc/bind/root.keys"; * add in your global options (''/etc/bind/named.conf.options''): dnssec-enable yes; dnssec-validation yes; dnssec-lookaside auto; * restart bind The DLV Registry public key is already provided in the ''bind9'' package. Then, you can check it with the ''dig'' tool (available in the ''dnsutils'' Debian package): dig +dnssec <zone> Look at the flags: it is secured if you find the ''ad'' flag. If there is the ''aa'' flag instead, then you are interrogating on of the authoritative DNS servers for the zone, it is also secure, but better test it on another server to be sure it is propagated. {{warning}} If you check an entry of your zone which is a CNAME, beware the CNAME is resolved and if the destination name cannot be validated, then your entry won't either. be0db02961e101c0968db210380fa62d2dc6369b 0 43 153 152 2010-11-01T23:29:34Z Duck 2 /* What is DNSSEC ? */ wikitext text/x-wiki == NS1 & NS2 == DC dans provide primary or secondary DNS servers for your zones. To have your master zone modified on our servers, you can: * use our [[UserMagicalInterface]] * ask administrators == DNS Security == To provide as much security as possible, DC supports the following mechanisms. === TSIG === This protocol allows a secure transfer of zones between primary and secondary servers. The DC's DNS servers support TSIG and comminication between them are always secured. The following entities are known to support TSIG and can then securely transfer zones to/from DC: * [http://www.hivane.net/ Hivane] === DNSSEC === ==== What is DNSSEC ? ==== This protocol aims at establishing a chain of trust, from the root of the DNS, to ensure response to queries on a zone has not been altered on the way. With the root zone public key, it is possible to validate the replies step by step down to your zone, for example: root public key -> ''.'' zone -> NS for ''org.'' -> ''org.'' zone -> NS for ''milkypond.org.'' -> ''milkypond.org'' zone -> ''irc.milkypond.org.'' entry. Unfortunately, many DNS providers do not support DNSSEC (Gandi is one of them :-/). In order to help people work on securing their zone, and be ready when their provider is, the [http://www.isc.org/ ISC] created a solution to validating your zone, using another secure path: by publishing security associations in a special zone (''dlv.isc.org'', called the DLV Registry), which itself can be validated the normal way. This is only a stopgap, but as providers seems not to be in a hurry to do their job, DC decided to use it. ==== How to use it for my zones ? ==== DC DNS servers are able to handle the complicated procedure needed to sign a zone for you. You can just modify it the classic way, and have it signed automatically. You just need to ask us to switch the zone to the secure mode. If your provider gladly support DNSSEC, we can provide the necessary information for the chain of trust; if not, we can use the DLV registry. Beware DNS always means propagation delays, so you may have to wait a few days before the switch is completed and your zone fully secured over the whole world. ==== How to test my zone is secured ? ==== First, you need a validating DNS server (explanations for ''bind9'' on Debian): * get the root zone public key (using this script for example: [[File:Get dns root zone key.sh]]) * add the key to your configuration (in ''/etc/bind/named.conf''): include "/etc/bind/root.keys"; * add in your global options (''/etc/bind/named.conf.options''): dnssec-enable yes; dnssec-validation yes; dnssec-lookaside auto; * restart bind The DLV Registry public key is already provided in the ''bind9'' package. Then, you can check it with the ''dig'' tool (available in the ''dnsutils'' Debian package): dig +dnssec <zone> Look at the flags: it is secured if you find the ''ad'' flag. If there is the ''aa'' flag instead, then you are interrogating on of the authoritative DNS servers for the zone, it is also secure, but better test it on another server to be sure it is propagated. {{warning}} If you check an entry of your zone which is a CNAME, beware the CNAME is resolved and if the destination name cannot be validated, then your entry won't either. 0eb8346b9b5dac58ba31376be6e467fd591e1a4b 154 153 2010-11-01T23:29:49Z Duck 2 /* What is DNSSEC ? */ wikitext text/x-wiki == NS1 & NS2 == DC dans provide primary or secondary DNS servers for your zones. To have your master zone modified on our servers, you can: * use our [[UserMagicalInterface]] * ask administrators == DNS Security == To provide as much security as possible, DC supports the following mechanisms. === TSIG === This protocol allows a secure transfer of zones between primary and secondary servers. The DC's DNS servers support TSIG and comminication between them are always secured. The following entities are known to support TSIG and can then securely transfer zones to/from DC: * [http://www.hivane.net/ Hivane] === DNSSEC === ==== What is DNSSEC ? ==== This protocol aims at establishing a chain of trust, from the root of the DNS, to ensure response to queries on a zone has not been altered on the way. With the root zone public key, it is possible to validate the replies step by step down to your zone, for example: root public key -> ''.'' zone -> NS for ''org.'' -> ''org.'' zone -> NS for ''milkypond.org.'' -> ''milkypond.org.'' zone -> ''irc.milkypond.org.'' entry. Unfortunately, many DNS providers do not support DNSSEC (Gandi is one of them :-/). In order to help people work on securing their zone, and be ready when their provider is, the [http://www.isc.org/ ISC] created a solution to validating your zone, using another secure path: by publishing security associations in a special zone (''dlv.isc.org'', called the DLV Registry), which itself can be validated the normal way. This is only a stopgap, but as providers seems not to be in a hurry to do their job, DC decided to use it. ==== How to use it for my zones ? ==== DC DNS servers are able to handle the complicated procedure needed to sign a zone for you. You can just modify it the classic way, and have it signed automatically. You just need to ask us to switch the zone to the secure mode. If your provider gladly support DNSSEC, we can provide the necessary information for the chain of trust; if not, we can use the DLV registry. Beware DNS always means propagation delays, so you may have to wait a few days before the switch is completed and your zone fully secured over the whole world. ==== How to test my zone is secured ? ==== First, you need a validating DNS server (explanations for ''bind9'' on Debian): * get the root zone public key (using this script for example: [[File:Get dns root zone key.sh]]) * add the key to your configuration (in ''/etc/bind/named.conf''): include "/etc/bind/root.keys"; * add in your global options (''/etc/bind/named.conf.options''): dnssec-enable yes; dnssec-validation yes; dnssec-lookaside auto; * restart bind The DLV Registry public key is already provided in the ''bind9'' package. Then, you can check it with the ''dig'' tool (available in the ''dnsutils'' Debian package): dig +dnssec <zone> Look at the flags: it is secured if you find the ''ad'' flag. If there is the ''aa'' flag instead, then you are interrogating on of the authoritative DNS servers for the zone, it is also secure, but better test it on another server to be sure it is propagated. {{warning}} If you check an entry of your zone which is a CNAME, beware the CNAME is resolved and if the destination name cannot be validated, then your entry won't either. 7a5eeb446e2efbbb50fcfe4636ce7fb58b2036aa 155 154 2010-11-01T23:30:46Z Duck 2 /* What is DNSSEC ? */ wikitext text/x-wiki == NS1 & NS2 == DC dans provide primary or secondary DNS servers for your zones. To have your master zone modified on our servers, you can: * use our [[UserMagicalInterface]] * ask administrators == DNS Security == To provide as much security as possible, DC supports the following mechanisms. === TSIG === This protocol allows a secure transfer of zones between primary and secondary servers. The DC's DNS servers support TSIG and comminication between them are always secured. The following entities are known to support TSIG and can then securely transfer zones to/from DC: * [http://www.hivane.net/ Hivane] === DNSSEC === ==== What is DNSSEC ? ==== This protocol aims at establishing a chain of trust, from the root of the DNS, to ensure response to queries on a zone has not been altered on the way. With the root zone public key, it is possible to validate the replies step by step down to your zone, for example: root public key -> ''.'' zone -> NS for ''org.'' -> ''org.'' zone -> NS for ''milkypond.org.'' -> ''milkypond.org.'' zone -> ''irc.milkypond.org.'' entry. Unfortunately, many DNS providers do not support DNSSEC (Gandi is one of them :-/). In order to help people work on securing their zone, and be ready when their provider is, the [http://www.isc.org/ ISC] created a solution to validate zones using another secure path: by publishing security associations in a special zone (''dlv.isc.org'', called the DLV Registry), which itself can be validated the normal way. This is only a stopgap, but as providers seems not to be in a hurry to do their job, DC decided to use it. ==== How to use it for my zones ? ==== DC DNS servers are able to handle the complicated procedure needed to sign a zone for you. You can just modify it the classic way, and have it signed automatically. You just need to ask us to switch the zone to the secure mode. If your provider gladly support DNSSEC, we can provide the necessary information for the chain of trust; if not, we can use the DLV registry. Beware DNS always means propagation delays, so you may have to wait a few days before the switch is completed and your zone fully secured over the whole world. ==== How to test my zone is secured ? ==== First, you need a validating DNS server (explanations for ''bind9'' on Debian): * get the root zone public key (using this script for example: [[File:Get dns root zone key.sh]]) * add the key to your configuration (in ''/etc/bind/named.conf''): include "/etc/bind/root.keys"; * add in your global options (''/etc/bind/named.conf.options''): dnssec-enable yes; dnssec-validation yes; dnssec-lookaside auto; * restart bind The DLV Registry public key is already provided in the ''bind9'' package. Then, you can check it with the ''dig'' tool (available in the ''dnsutils'' Debian package): dig +dnssec <zone> Look at the flags: it is secured if you find the ''ad'' flag. If there is the ''aa'' flag instead, then you are interrogating on of the authoritative DNS servers for the zone, it is also secure, but better test it on another server to be sure it is propagated. {{warning}} If you check an entry of your zone which is a CNAME, beware the CNAME is resolved and if the destination name cannot be validated, then your entry won't either. fde161b47563b613c74197c87f5902438f2206d0 156 155 2010-11-01T23:33:41Z Duck 2 /* What is DNSSEC ? */ wikitext text/x-wiki == NS1 & NS2 == DC dans provide primary or secondary DNS servers for your zones. To have your master zone modified on our servers, you can: * use our [[UserMagicalInterface]] * ask administrators == DNS Security == To provide as much security as possible, DC supports the following mechanisms. === TSIG === This protocol allows a secure transfer of zones between primary and secondary servers. The DC's DNS servers support TSIG and comminication between them are always secured. The following entities are known to support TSIG and can then securely transfer zones to/from DC: * [http://www.hivane.net/ Hivane] === DNSSEC === ==== What is [[wikipedia:Domain_Name_System_Security_Extensions|complicated procedure]]? ==== This protocol aims at establishing a chain of trust, from the root of the DNS, to ensure response to queries on a zone has not been altered on the way. With the root zone public key, it is possible to validate the replies step by step down to your zone, for example: root public key -> ''.'' zone -> NS for ''org.'' -> ''org.'' zone -> NS for ''milkypond.org.'' -> ''milkypond.org.'' zone -> ''irc.milkypond.org.'' entry. Unfortunately, many DNS providers do not support DNSSEC (Gandi is one of them :-/). In order to help people work on securing their zone, and be ready when their provider is, the [http://www.isc.org/ ISC] created a solution to validate zones using another secure path: by publishing security associations in a special zone (''dlv.isc.org'', called the DLV Registry), which itself can be validated the normal way. This is only a stopgap, but as providers seems not to be in a hurry to do their job, DC decided to use it. ==== How to use it for my zones ? ==== DC DNS servers are able to handle the complicated procedure needed to sign a zone for you. You can just modify it the classic way, and have it signed automatically. You just need to ask us to switch the zone to the secure mode. If your provider gladly support DNSSEC, we can provide the necessary information for the chain of trust; if not, we can use the DLV registry. Beware DNS always means propagation delays, so you may have to wait a few days before the switch is completed and your zone fully secured over the whole world. ==== How to test my zone is secured ? ==== First, you need a validating DNS server (explanations for ''bind9'' on Debian): * get the root zone public key (using this script for example: [[File:Get dns root zone key.sh]]) * add the key to your configuration (in ''/etc/bind/named.conf''): include "/etc/bind/root.keys"; * add in your global options (''/etc/bind/named.conf.options''): dnssec-enable yes; dnssec-validation yes; dnssec-lookaside auto; * restart bind The DLV Registry public key is already provided in the ''bind9'' package. Then, you can check it with the ''dig'' tool (available in the ''dnsutils'' Debian package): dig +dnssec <zone> Look at the flags: it is secured if you find the ''ad'' flag. If there is the ''aa'' flag instead, then you are interrogating on of the authoritative DNS servers for the zone, it is also secure, but better test it on another server to be sure it is propagated. {{warning}} If you check an entry of your zone which is a CNAME, beware the CNAME is resolved and if the destination name cannot be validated, then your entry won't either. 706449626ffaf054f234c9722a107f8b794e25b5 157 156 2010-11-01T23:34:04Z Duck 2 /* DNSSEC */ wikitext text/x-wiki == NS1 & NS2 == DC dans provide primary or secondary DNS servers for your zones. To have your master zone modified on our servers, you can: * use our [[UserMagicalInterface]] * ask administrators == DNS Security == To provide as much security as possible, DC supports the following mechanisms. === TSIG === This protocol allows a secure transfer of zones between primary and secondary servers. The DC's DNS servers support TSIG and comminication between them are always secured. The following entities are known to support TSIG and can then securely transfer zones to/from DC: * [http://www.hivane.net/ Hivane] === DNSSEC === ==== What is [[wikipedia:Domain_Name_System_Security_Extensions|DNSSEC]]? ==== This protocol aims at establishing a chain of trust, from the root of the DNS, to ensure response to queries on a zone has not been altered on the way. With the root zone public key, it is possible to validate the replies step by step down to your zone, for example: root public key -> ''.'' zone -> NS for ''org.'' -> ''org.'' zone -> NS for ''milkypond.org.'' -> ''milkypond.org.'' zone -> ''irc.milkypond.org.'' entry. Unfortunately, many DNS providers do not support DNSSEC (Gandi is one of them :-/). In order to help people work on securing their zone, and be ready when their provider is, the [http://www.isc.org/ ISC] created a solution to validate zones using another secure path: by publishing security associations in a special zone (''dlv.isc.org'', called the DLV Registry), which itself can be validated the normal way. This is only a stopgap, but as providers seems not to be in a hurry to do their job, DC decided to use it. ==== How to use it for my zones? ==== DC DNS servers are able to handle the complicated procedure needed to sign a zone for you. You can just modify it the classic way, and have it signed automatically. You just need to ask us to switch the zone to the secure mode. If your provider gladly support DNSSEC, we can provide the necessary information for the chain of trust; if not, we can use the DLV registry. Beware DNS always means propagation delays, so you may have to wait a few days before the switch is completed and your zone fully secured over the whole world. ==== How to test my zone is secured? ==== First, you need a validating DNS server (explanations for ''bind9'' on Debian): * get the root zone public key (using this script for example: [[File:Get dns root zone key.sh]]) * add the key to your configuration (in ''/etc/bind/named.conf''): include "/etc/bind/root.keys"; * add in your global options (''/etc/bind/named.conf.options''): dnssec-enable yes; dnssec-validation yes; dnssec-lookaside auto; * restart bind The DLV Registry public key is already provided in the ''bind9'' package. Then, you can check it with the ''dig'' tool (available in the ''dnsutils'' Debian package): dig +dnssec <zone> Look at the flags: it is secured if you find the ''ad'' flag. If there is the ''aa'' flag instead, then you are interrogating on of the authoritative DNS servers for the zone, it is also secure, but better test it on another server to be sure it is propagated. {{warning}} If you check an entry of your zone which is a CNAME, beware the CNAME is resolved and if the destination name cannot be validated, then your entry won't either. b10780603736af83f007c474805821a6de740053 158 157 2010-11-01T23:35:05Z Duck 2 /* TSIG */ wikitext text/x-wiki == NS1 & NS2 == DC dans provide primary or secondary DNS servers for your zones. To have your master zone modified on our servers, you can: * use our [[UserMagicalInterface]] * ask administrators == DNS Security == To provide as much security as possible, DC supports the following mechanisms. === [[wikipedia:TSIG|TSIG]] === This protocol allows a secure transfer of zones between primary and secondary servers. The DC's DNS servers support TSIG and comminication between them are always secured. The following entities are known to support TSIG and can then securely transfer zones to/from DC: * [http://www.hivane.net/ Hivane] === DNSSEC === ==== What is [[wikipedia:Domain_Name_System_Security_Extensions|DNSSEC]]? ==== This protocol aims at establishing a chain of trust, from the root of the DNS, to ensure response to queries on a zone has not been altered on the way. With the root zone public key, it is possible to validate the replies step by step down to your zone, for example: root public key -> ''.'' zone -> NS for ''org.'' -> ''org.'' zone -> NS for ''milkypond.org.'' -> ''milkypond.org.'' zone -> ''irc.milkypond.org.'' entry. Unfortunately, many DNS providers do not support DNSSEC (Gandi is one of them :-/). In order to help people work on securing their zone, and be ready when their provider is, the [http://www.isc.org/ ISC] created a solution to validate zones using another secure path: by publishing security associations in a special zone (''dlv.isc.org'', called the DLV Registry), which itself can be validated the normal way. This is only a stopgap, but as providers seems not to be in a hurry to do their job, DC decided to use it. ==== How to use it for my zones? ==== DC DNS servers are able to handle the complicated procedure needed to sign a zone for you. You can just modify it the classic way, and have it signed automatically. You just need to ask us to switch the zone to the secure mode. If your provider gladly support DNSSEC, we can provide the necessary information for the chain of trust; if not, we can use the DLV registry. Beware DNS always means propagation delays, so you may have to wait a few days before the switch is completed and your zone fully secured over the whole world. ==== How to test my zone is secured? ==== First, you need a validating DNS server (explanations for ''bind9'' on Debian): * get the root zone public key (using this script for example: [[File:Get dns root zone key.sh]]) * add the key to your configuration (in ''/etc/bind/named.conf''): include "/etc/bind/root.keys"; * add in your global options (''/etc/bind/named.conf.options''): dnssec-enable yes; dnssec-validation yes; dnssec-lookaside auto; * restart bind The DLV Registry public key is already provided in the ''bind9'' package. Then, you can check it with the ''dig'' tool (available in the ''dnsutils'' Debian package): dig +dnssec <zone> Look at the flags: it is secured if you find the ''ad'' flag. If there is the ''aa'' flag instead, then you are interrogating on of the authoritative DNS servers for the zone, it is also secure, but better test it on another server to be sure it is propagated. {{warning}} If you check an entry of your zone which is a CNAME, beware the CNAME is resolved and if the destination name cannot be validated, then your entry won't either. bd858c5a772ae814726b721c3930a966b9a6eb2e 159 158 2010-11-01T23:35:42Z Duck 2 /* DNSSEC */ wikitext text/x-wiki == NS1 & NS2 == DC dans provide primary or secondary DNS servers for your zones. To have your master zone modified on our servers, you can: * use our [[UserMagicalInterface]] * ask administrators == DNS Security == To provide as much security as possible, DC supports the following mechanisms. === [[wikipedia:TSIG|TSIG]] === This protocol allows a secure transfer of zones between primary and secondary servers. The DC's DNS servers support TSIG and comminication between them are always secured. The following entities are known to support TSIG and can then securely transfer zones to/from DC: * [http://www.hivane.net/ Hivane] === [[wikipedia:Domain_Name_System_Security_Extensions|DNSSEC]] === ==== What is DNSSEC? ==== This protocol aims at establishing a chain of trust, from the root of the DNS, to ensure response to queries on a zone has not been altered on the way. With the root zone public key, it is possible to validate the replies step by step down to your zone, for example: root public key -> ''.'' zone -> NS for ''org.'' -> ''org.'' zone -> NS for ''milkypond.org.'' -> ''milkypond.org.'' zone -> ''irc.milkypond.org.'' entry. Unfortunately, many DNS providers do not support DNSSEC (Gandi is one of them :-/). In order to help people work on securing their zone, and be ready when their provider is, the [http://www.isc.org/ ISC] created a solution to validate zones using another secure path: by publishing security associations in a special zone (''dlv.isc.org'', called the DLV Registry), which itself can be validated the normal way. This is only a stopgap, but as providers seems not to be in a hurry to do their job, DC decided to use it. ==== How to use it for my zones? ==== DC DNS servers are able to handle the complicated procedure needed to sign a zone for you. You can just modify it the classic way, and have it signed automatically. You just need to ask us to switch the zone to the secure mode. If your provider gladly support DNSSEC, we can provide the necessary information for the chain of trust; if not, we can use the DLV registry. Beware DNS always means propagation delays, so you may have to wait a few days before the switch is completed and your zone fully secured over the whole world. ==== How to test my zone is secured? ==== First, you need a validating DNS server (explanations for ''bind9'' on Debian): * get the root zone public key (using this script for example: [[File:Get dns root zone key.sh]]) * add the key to your configuration (in ''/etc/bind/named.conf''): include "/etc/bind/root.keys"; * add in your global options (''/etc/bind/named.conf.options''): dnssec-enable yes; dnssec-validation yes; dnssec-lookaside auto; * restart bind The DLV Registry public key is already provided in the ''bind9'' package. Then, you can check it with the ''dig'' tool (available in the ''dnsutils'' Debian package): dig +dnssec <zone> Look at the flags: it is secured if you find the ''ad'' flag. If there is the ''aa'' flag instead, then you are interrogating on of the authoritative DNS servers for the zone, it is also secure, but better test it on another server to be sure it is propagated. {{warning}} If you check an entry of your zone which is a CNAME, beware the CNAME is resolved and if the destination name cannot be validated, then your entry won't either. 2b015e2984a12d8ce4068caa3505a1d3e4b88d2a 0 39 160 148 2010-12-04T17:47:19Z Duck 2 wikitext text/x-wiki Here is a short overview of the services provided by DuckCorp. Our services are supervised and important data are saved regulary. {{warning}} [[Services/Security|Notes about security !]] == Public Services == * a stratum 2 NTP server, to setup time on your machines, and also part of the [http://www.pool.ntp.org/en/ NTP Pool Project] * a dictionnary server, using the DICT protocol, provided with a [http://dico.duckcorp.org/ web interface] == Shared Users Services == Even if the service is publicly accessible, and is used to share information with the world, parts of the it may be restricted by their respective owner. * [ftp://ftp.duckcorp.org/ public FTP server] (with ACLs) * [https://wiki.duckcorp.org/ public wiki] (with ACLs) * [https://projects.duckcorp.org/ public issue tracker] (with ACLs) * [https://rcs.duckcorp.org/ public VCS access] (with web viewers) * [http://debian.duckcorp.org/ public Debian repository] * [http://photos.duckcorp.org/ public photo gallery] (with ACLs) == Users Services == * Network facilities: ** [[Services/DNS|DNS hosting]] (NS1/NS2, DNSSEC) ** IPv6 tunnels ** [[Services/NSTX|NSTX]] (IP over DNS tunnels) * Communication facilities: ** mail hosting (MX1/MX2, user controlled antispam, antivirus, flexible quotas, SIEVE filtering, webmails, ...) ** mailing-lists hosting ** IRC world: *** IRC Network (with web gateway) *** IRC bouncer *** IRC to IM gateway (to connect to ICQ/AIM/YM!/... through an IRC interface) ** XMPP (Jabber) Network (using the 'milkypond.org' domain, or a user domain) ** Triboune Libre ** SAFT * Application facilities: ** web hosting, with various possibilities for web programming (SSI, PHP, Perl, Python, Ruby, ...), and stats ** VCS hosting: git, SVN, BZR ** shell access (site admin, run custom scripts, screen for text-mode geeks, ...) (for trusted users only) * Databases facilities: ** PostgreSQL ** MySQL ** LDAP 5e5f0f066a305b92d314a690cca030b008efaea7 188 160 2011-05-08T18:28:42Z Duck 2 wikitext text/x-wiki Here is a short overview of the services provided by DuckCorp. Our services are supervised and important data are saved regulary. {{warning}} [[Services/Security|Notes about security !]] == Public Services == * a stratum 2 NTP server, to setup time on your machines, and also part of the [http://www.pool.ntp.org/en/ NTP Pool Project] * a dictionnary server, using the DICT protocol, provided with a [http://dico.duckcorp.org/ web interface] == Shared Users Services == Even if the service is publicly accessible, and is used to share information with the world, parts of the it may be restricted by their respective owner. * [ftp://ftp.duckcorp.org/ public FTP server] (with ACLs) * [https://wiki.duckcorp.org/ public wiki] (with ACLs) * [https://projects.duckcorp.org/ public issue tracker] (with ACLs) * [https://rcs.duckcorp.org/ public VCS access] (with web viewers) * [http://debian.duckcorp.org/ public Debian repository] * [http://photos.duckcorp.org/ public photo gallery] (with ACLs) == Users Services == * Network facilities: ** [[Services/DNS|DNS hosting]] (NS1/NS2, DNSSEC) ** IPv6 tunnels ** [[Services/NSTX|NSTX]] (IP over DNS tunnels) * Communication facilities: ** mail hosting (MX1/MX2, user controlled antispam, antivirus, flexible quotas, SIEVE filtering, webmails, ...) ** mailing-lists hosting ** IRC world: *** IRC Network (with web gateway) *** IRC bouncer *** IRC to IM gateway (to connect to ICQ/AIM/YM!/... through an IRC interface) ** XMPP (Jabber) Network (using the 'milkypond.org' domain, or a user domain) ** Triboune Libre ** SAFT * Application facilities: ** web hosting, with various possibilities for web programming (SSI, PHP, Perl, Python, Ruby, ...), and stats ** VCS hosting: git, SVN, BZR ** shell access (site admin, run custom scripts, screen for text-mode geeks, ...) (for trusted users only) * Databases facilities: ** PostgreSQL ** MySQL ** LDAP * [[Services/Backup|Backup]] a11d0c9034ce85edadd29cb20e46547b5880622f 190 188 2011-05-14T18:57:11Z Duck 2 wikitext text/x-wiki Here is a short overview of the services provided by DuckCorp. Our services are supervised and important data are saved regulary. {{warning}} [[Services/Security|Notes about security !]] == Public Services == * a stratum 2 NTP server, to setup time on your machines, and also part of the [http://www.pool.ntp.org/en/ NTP Pool Project] * a dictionnary server, using the DICT protocol, provided with a [http://dico.duckcorp.org/ web interface] == Shared Users Services == Even if the service is publicly accessible, and is used to share information with the world, parts of the it may be restricted by their respective owner. * [ftp://ftp.duckcorp.org/ public FTP server] (with ACLs) * [https://wiki.duckcorp.org/ public wiki] (with ACLs) * [https://projects.duckcorp.org/ public issue tracker] (with ACLs) * [https://rcs.duckcorp.org/ public VCS access] (with web viewers) * [http://debian.duckcorp.org/ public Debian repository] * [http://photos.duckcorp.org/ public photo gallery] (with ACLs) == Users Services == * Network facilities: ** [[Services/DNS|DNS hosting]] (NS1/NS2, DNSSEC) ** IPv6 tunnels ** [[Services/NSTX|NSTX]] (IP over DNS tunnels) * Communication facilities: ** [[Services/Mail|mail hosting]] (MX1/MX2, user controlled antispam, antivirus, flexible quotas, SIEVE filtering, webmails, ...) ** mailing-lists hosting ** IRC world: *** IRC Network (with web gateway) *** IRC bouncer *** IRC to IM gateway (to connect to ICQ/AIM/YM!/... through an IRC interface) ** XMPP (Jabber) Network (using the 'milkypond.org' domain, or a user domain) ** Triboune Libre ** SAFT * Application facilities: ** web hosting, with various possibilities for web programming (SSI, PHP, Perl, Python, Ruby, ...), and stats ** VCS hosting: git, SVN, BZR ** shell access (site admin, run custom scripts, screen for text-mode geeks, ...) (for trusted users only) * Databases facilities: ** PostgreSQL ** MySQL ** LDAP * [[Services/Backup|Backup]] 659d027184d0d1f1dea1968bb0596d6dfc0c7b4a 6 45 161 2010-12-04T17:54:33Z Duck 2 DuckCorp's Certificate Authority Certificate wikitext text/x-wiki DuckCorp's Certificate Authority Certificate 96073ec9125a4b0e24a9a3cfb940f10c41ec9a37 167 161 2010-12-04T18:28:08Z Duck 2 Protected "[[File:Duckcorp.crt]]" ([edit=sysop] (indefinite) [move=sysop] (indefinite)) wikitext text/x-wiki DuckCorp's Certificate Authority Certificate 96073ec9125a4b0e24a9a3cfb940f10c41ec9a37 0 46 162 2010-12-04T17:58:21Z Duck 2 Created page with "== Introduction == '''All''' services containing sensitive information are protected using cryptography. Whenever possible, we add the necessary configuration to ensure unsecure…" wikitext text/x-wiki == Introduction == '''All''' services containing sensitive information are protected using cryptography. Whenever possible, we add the necessary configuration to ensure unsecure usages are not possible, to protect your data. Nevertheless, a few things are needed on you side to improve security, that's why we are providing the following notes in order to help you configure your software in a secure fashion. == Areas of Security == === Web-based Services === To ensure you're talking to the right server, and noone pretend to be a DC's server to tricks you, you need to install the following certificate in your browser : [[File:Duckcorp.crt]] (clicking on the link should ask for installation, and you'll just need to confirm you trust it). 61bff8d58afa336781743c387cf257458a0720a8 164 162 2010-12-04T18:24:41Z Duck 2 /* Areas of Security */ wikitext text/x-wiki == Introduction == '''All''' services containing sensitive information are protected using cryptography. Whenever possible, we add the necessary configuration to ensure unsecure usages are not possible, to protect your data. Nevertheless, a few things are needed on you side to improve security, that's why we are providing the following notes in order to help you configure your software in a secure fashion. == Areas of Security == === Web-based Services === To ensure you're talking to the right server, and noone pretend to be a DC's server to tricks you, you need to install the following certificate in your browser : [[File:Duckcorp.crt]] (clicking on the link should ask for installation, and you'll just need to confirm you trust it). === Mails from DC's Administrators === You should not trust mails pretenting to come from us. The only way to be sure a mail is from someone, is to agree on exchanging cryptographically-protected messages. On [[Admins|this page]] you'll find the list of DC's administrators from which you may receive mails (on the users's mailing-list for example). You could trust their GPG keys directly, but that would not be secure at all. The best way is to meet, live, in a [[wikipedia:Key_signing_party|key signing party]]. If a friend has already signed our key, and is not too far from you, you may also propagate your trust to our key. Once done, you'll be sure what seems to come from us is really from us. bf7f8ff54165a7a4a066abaf1b4626a925ce29d1 165 164 2010-12-04T18:25:01Z Duck 2 /* Mails from DC's Administrators */ wikitext text/x-wiki == Introduction == '''All''' services containing sensitive information are protected using cryptography. Whenever possible, we add the necessary configuration to ensure unsecure usages are not possible, to protect your data. Nevertheless, a few things are needed on you side to improve security, that's why we are providing the following notes in order to help you configure your software in a secure fashion. == Areas of Security == === Web-based Services === To ensure you're talking to the right server, and noone pretend to be a DC's server to tricks you, you need to install the following certificate in your browser : [[File:Duckcorp.crt]] (clicking on the link should ask for installation, and you'll just need to confirm you trust it). === Mails from DC's Administrators === You should not trust mails pretenting to come from us. The only way to be sure a mail is from someone, is to agree on exchanging cryptographically-protected messages. On [[Admins|this page]] you'll find the list of DC's administrators from which you may receive mails (on the users's mailing-list for example). You could trust their GPG keys directly, but that would not be secure at all. The best way is to meet, live, in a [[wikipedia:Key_signing_party|key signing party]]. If a friend has already signed our key, and is not too far from you, you may also propagate your trust to our keys. Once done, you'll be sure what seems to come from us is really from us. edb5a760a744c4b4fc2c5e36240e9ee283d9db08 166 165 2010-12-04T18:27:38Z Duck 2 Protected "[[Services/Security]]" ([edit=sysop] (indefinite) [move=sysop] (indefinite)) wikitext text/x-wiki == Introduction == '''All''' services containing sensitive information are protected using cryptography. Whenever possible, we add the necessary configuration to ensure unsecure usages are not possible, to protect your data. Nevertheless, a few things are needed on you side to improve security, that's why we are providing the following notes in order to help you configure your software in a secure fashion. == Areas of Security == === Web-based Services === To ensure you're talking to the right server, and noone pretend to be a DC's server to tricks you, you need to install the following certificate in your browser : [[File:Duckcorp.crt]] (clicking on the link should ask for installation, and you'll just need to confirm you trust it). === Mails from DC's Administrators === You should not trust mails pretenting to come from us. The only way to be sure a mail is from someone, is to agree on exchanging cryptographically-protected messages. On [[Admins|this page]] you'll find the list of DC's administrators from which you may receive mails (on the users's mailing-list for example). You could trust their GPG keys directly, but that would not be secure at all. The best way is to meet, live, in a [[wikipedia:Key_signing_party|key signing party]]. If a friend has already signed our key, and is not too far from you, you may also propagate your trust to our keys. Once done, you'll be sure what seems to come from us is really from us. edb5a760a744c4b4fc2c5e36240e9ee283d9db08 170 166 2010-12-04T19:01:10Z Duck 2 /* Areas of Security */ wikitext text/x-wiki == Introduction == '''All''' services containing sensitive information are protected using cryptography. Whenever possible, we add the necessary configuration to ensure unsecure usages are not possible, to protect your data. Nevertheless, a few things are needed on you side to improve security, that's why we are providing the following notes in order to help you configure your software in a secure fashion. == Areas of Security == === Mails from DC's Administrators === You should not trust mails pretenting to come from us. The only way to be sure a mail is from someone, is to agree on exchanging cryptographically-protected messages. On [[Admins|this page]] you'll find the list of DC's administrators from which you may receive mails (on the users's mailing-list for example). You could trust their GPG keys directly, but that would not be secure at all. The best way is to meet, live, in a [[wikipedia:Key_signing_party|key signing party]]. If a friend has already signed our key, and is not too far from you, you may also propagate your trust to our keys. Once done, you'll be sure what seems to come from us is really from us. === Talking to the Right Machine/Service === All remote services use an address on the internet, like ''superservice.duckcorp.org'', but if you are connected through an untrusted network (like if you're using a third-party's WIFI), you cannot be sure you'll be connecting to the right machine, and you may disclose important information like your credentials. ==== Service Locator Security ==== One possible attack is to alter replies to the machine locator service (DNS) in order to redirect your communication to a nasty machine. Since November 2010, ''duckcorp.org'' and ''milkypond.org'' domains are cryptographically signed using the DNSSEC system, so you are now able to verify the address returned for the service is the right one. This system is not new, but has recently switched into production, so your operating system may not yet be properly configured to use this protection. Until it is pre-configured in most of them, you may configure it yourself using [[Services/DNS#How_to_test_my_zone_is_secured.3F|this procedure]]. {{warning}} Beware this protection solves certains security problems but is not sufficient to ensure you're talking to the right machine/service. Nevertheless it ensures: * the address of the machine/service is the right one * information related to the domain, list of mail servers, security information on hosts (SSHFP)… are not tampered ==== Remote TLS/SSL-based Services ==== To ensure you're talking to the right server, and noone pretend to be a DC's server to tricks you, you need to install the following certificate in your browser : [[File:Duckcorp.crt]] (clicking on the link should ask for installation, and you'll just need to confirm you trust it). 40d27cced4bc11436b0d4fbd6476d4dc0f903a21 171 170 2010-12-04T19:05:36Z Duck 2 /* Talking to the Right Machine/Service */ wikitext text/x-wiki == Introduction == '''All''' services containing sensitive information are protected using cryptography. Whenever possible, we add the necessary configuration to ensure unsecure usages are not possible, to protect your data. Nevertheless, a few things are needed on you side to improve security, that's why we are providing the following notes in order to help you configure your software in a secure fashion. == Areas of Security == === Mails from DC's Administrators === You should not trust mails pretenting to come from us. The only way to be sure a mail is from someone, is to agree on exchanging cryptographically-protected messages. On [[Admins|this page]] you'll find the list of DC's administrators from which you may receive mails (on the users's mailing-list for example). You could trust their GPG keys directly, but that would not be secure at all. The best way is to meet, live, in a [[wikipedia:Key_signing_party|key signing party]]. If a friend has already signed our key, and is not too far from you, you may also propagate your trust to our keys. Once done, you'll be sure what seems to come from us is really from us. === Talking to the Right Machine/Service === All remote services use an address on the internet, like ''superservice.duckcorp.org'', but if you are connected through an untrusted network (like if you're using a third-party's WIFI), you cannot be sure you'll be connecting to the right machine, and you may disclose important information like your credentials. ==== Remote TLS/SSL-based Services ==== To ensure you're talking to the right server, and noone pretend to be a DC's server to tricks you, you need to install the following certificate in your browser : [[File:Duckcorp.crt]] (clicking on the link should ask for installation, and you'll just need to confirm you trust it). ==== Service Locator Security ==== One possible attack is to alter replies to the machine locator service (DNS) in order to redirect your communication to a nasty machine. Since November 2010, ''duckcorp.org'' and ''milkypond.org'' domains are cryptographically signed using the DNSSEC system, so you are now able to verify the address returned for the service is the right one. This system is not new, but has recently switched into production, so your operating system may not yet be properly configured to use this protection. Until it is pre-configured in most of them, you may configure it yourself using [[Services/DNS#How_to_test_my_zone_is_secured.3F|this procedure]]. {{warning}} Beware this protection solves certains security problems but is not sufficient to ensure you're talking to the right machine/service. Nevertheless it ensures: * the address of the machine/service is the right one * information related to the domain, list of mail servers, security information on hosts (SSHFP)… are not tampered Using this security plus certificate verification (see previous section) would ensure full security. 3fa47d21742971b088f625c944a7197721e79424 172 171 2010-12-04T19:16:38Z Duck 2 /* Areas of Security */ wikitext text/x-wiki == Introduction == '''All''' services containing sensitive information are protected using cryptography. Whenever possible, we add the necessary configuration to ensure unsecure usages are not possible, to protect your data. Nevertheless, a few things are needed on you side to improve security, that's why we are providing the following notes in order to help you configure your software in a secure fashion. == Areas of Security == === Mails from DC's Administrators === You should not trust mails pretenting to come from us. The only way to be sure a mail is from someone, is to agree on exchanging cryptographically-protected messages. On [[Admins|this page]] you'll find the list of DC's administrators from which you may receive mails (on the users's mailing-list for example). You could trust their GPG keys directly, but that would not be secure at all. The best way is to meet, live, in a [[wikipedia:Key_signing_party|key signing party]]. If a friend has already signed our key, and is not too far from you, you may also propagate your trust to our keys. Once done, you'll be sure what seems to come from us is really from us. === Talking to the Right Machine/Service === All remote services use an address on the internet, like ''superservice.duckcorp.org'', but if you are connected through an untrusted network (like if you're using a third-party's WIFI), you cannot be sure you'll be connecting to the right machine, and you may disclose important information like your credentials. ==== Remote TLS/SSL-based Services ==== To ensure you're talking to the right server, and noone pretend to be a DC's server to tricks you, you need to install the following certificate in your browser : [[File:Duckcorp.crt]] (clicking on the link should ask for installation, and you'll just need to confirm you trust it). ==== Service Locator Security ==== One possible attack is to alter replies from the machine locator service (DNS) in order to redirect your communication to a nasty machine. Since November 2010, ''duckcorp.org'' and ''milkypond.org'' domains are cryptographically signed using the DNSSEC system, so you are now able to verify the address returned for the service is the right one. This system is not new, but has recently switched into production, so your operating system may not yet be properly configured to use this protection. Until it is pre-configured in most of them, you may configure it yourself using [[Services/DNS#How_to_test_my_zone_is_secured.3F|this procedure]]. {{warning}} Beware this protection solves certains security problems but is not sufficient to ensure you're talking to the right machine/service. Nevertheless it ensures: * the address of the machine/service is the right one * information related to the domain, list of mail servers, security information on hosts (SSHFP)… are not tampered Using this security plus certificate verification (see previous section) would ensure full security. === Secure SSH Connections === In order not to be tricked connecting to a fake server, or to a rooted server (just in case), it is possible to check the SSH key of the server. As this verification is quite boring both for administrators and users, almost nobody on earth does it. Fortunately, it is possible to publish this information in the DNS and have OpenSSH check it for you automatically. To add this security, you can edit your system configuration (''/etc/ssh/ssh_config'') or your personal one (''~/.ssh/config''), and add the folowing: Host * VerifyHostKeyDNS ask Of course, the DNS replies may be altered, so if you want full security, read the [[#Service Locator Security|section about Service Locator Security]]. 7a93be04e70b646c70aa445ca7fe1a42b80d3732 173 172 2010-12-04T19:17:31Z Duck 2 /* Secure SSH Connections */ wikitext text/x-wiki == Introduction == '''All''' services containing sensitive information are protected using cryptography. Whenever possible, we add the necessary configuration to ensure unsecure usages are not possible, to protect your data. Nevertheless, a few things are needed on you side to improve security, that's why we are providing the following notes in order to help you configure your software in a secure fashion. == Areas of Security == === Mails from DC's Administrators === You should not trust mails pretenting to come from us. The only way to be sure a mail is from someone, is to agree on exchanging cryptographically-protected messages. On [[Admins|this page]] you'll find the list of DC's administrators from which you may receive mails (on the users's mailing-list for example). You could trust their GPG keys directly, but that would not be secure at all. The best way is to meet, live, in a [[wikipedia:Key_signing_party|key signing party]]. If a friend has already signed our key, and is not too far from you, you may also propagate your trust to our keys. Once done, you'll be sure what seems to come from us is really from us. === Talking to the Right Machine/Service === All remote services use an address on the internet, like ''superservice.duckcorp.org'', but if you are connected through an untrusted network (like if you're using a third-party's WIFI), you cannot be sure you'll be connecting to the right machine, and you may disclose important information like your credentials. ==== Remote TLS/SSL-based Services ==== To ensure you're talking to the right server, and noone pretend to be a DC's server to tricks you, you need to install the following certificate in your browser : [[File:Duckcorp.crt]] (clicking on the link should ask for installation, and you'll just need to confirm you trust it). ==== Service Locator Security ==== One possible attack is to alter replies from the machine locator service (DNS) in order to redirect your communication to a nasty machine. Since November 2010, ''duckcorp.org'' and ''milkypond.org'' domains are cryptographically signed using the DNSSEC system, so you are now able to verify the address returned for the service is the right one. This system is not new, but has recently switched into production, so your operating system may not yet be properly configured to use this protection. Until it is pre-configured in most of them, you may configure it yourself using [[Services/DNS#How_to_test_my_zone_is_secured.3F|this procedure]]. {{warning}} Beware this protection solves certains security problems but is not sufficient to ensure you're talking to the right machine/service. Nevertheless it ensures: * the address of the machine/service is the right one * information related to the domain, list of mail servers, security information on hosts (SSHFP)… are not tampered Using this security plus certificate verification (see previous section) would ensure full security. === Secure SSH Connections === In order not to be tricked connecting to a fake server, or to a rooted server (just in case), it is possible to check the SSH key of the server. As this verification is quite boring both for administrators and users, almost nobody on earth does it. Fortunately, it is possible to publish this information in the DNS and have OpenSSH check it for you automatically. To add this security, you can edit your system configuration (''/etc/ssh/ssh_config'') or your personal one (''~/.ssh/config''), and add the folowing: Host * VerifyHostKeyDNS ask Of course, the DNS replies may be altered, so if you want full security, read the [[Services/Security#Service_Locator_Security|section about Service Locator Security]]. 5e78f32b8b46545a6239dd48d3347264e704b5a6 174 173 2010-12-04T19:19:02Z Duck 2 /* Service Locator Security */ wikitext text/x-wiki == Introduction == '''All''' services containing sensitive information are protected using cryptography. Whenever possible, we add the necessary configuration to ensure unsecure usages are not possible, to protect your data. Nevertheless, a few things are needed on you side to improve security, that's why we are providing the following notes in order to help you configure your software in a secure fashion. == Areas of Security == === Mails from DC's Administrators === You should not trust mails pretenting to come from us. The only way to be sure a mail is from someone, is to agree on exchanging cryptographically-protected messages. On [[Admins|this page]] you'll find the list of DC's administrators from which you may receive mails (on the users's mailing-list for example). You could trust their GPG keys directly, but that would not be secure at all. The best way is to meet, live, in a [[wikipedia:Key_signing_party|key signing party]]. If a friend has already signed our key, and is not too far from you, you may also propagate your trust to our keys. Once done, you'll be sure what seems to come from us is really from us. === Talking to the Right Machine/Service === All remote services use an address on the internet, like ''superservice.duckcorp.org'', but if you are connected through an untrusted network (like if you're using a third-party's WIFI), you cannot be sure you'll be connecting to the right machine, and you may disclose important information like your credentials. ==== Remote TLS/SSL-based Services ==== To ensure you're talking to the right server, and noone pretend to be a DC's server to tricks you, you need to install the following certificate in your browser : [[File:Duckcorp.crt]] (clicking on the link should ask for installation, and you'll just need to confirm you trust it). ==== Service Locator Security ==== One possible attack is to alter replies from the machine locator service (DNS) in order to redirect your communication to a nasty machine. Since November 2010, ''duckcorp.org'' and ''milkypond.org'' domains are cryptographically signed using the DNSSEC system, so you are now able to verify the address returned for the service is the right one. This system is not new, but has recently switched into production, so your operating system may not yet be properly configured to use this protection. Until it is pre-configured in most of them, you may configure it yourself using [[Services/DNS#How_to_test_my_zone_is_secured.3F|this procedure]]. {{warning}} Beware this protection solves certains security problems but is not sufficient to ensure you're talking to the right machine/service. Nevertheless it ensures: * the address of the machine/service is the right one * information related to the domain, list of mail servers, security information on hosts (SSHFP)… are not tampered Using this security plus certificate verification (see [[Services/Security#Remote_TLS.2FSSL-based_Services|section about TLS/SSL-based Security]]) would ensure full security. === Secure SSH Connections === In order not to be tricked connecting to a fake server, or to a rooted server (just in case), it is possible to check the SSH key of the server. As this verification is quite boring both for administrators and users, almost nobody on earth does it. Fortunately, it is possible to publish this information in the DNS and have OpenSSH check it for you automatically. To add this security, you can edit your system configuration (''/etc/ssh/ssh_config'') or your personal one (''~/.ssh/config''), and add the folowing: Host * VerifyHostKeyDNS ask Of course, the DNS replies may be altered, so if you want full security, read the [[Services/Security#Service_Locator_Security|section about Service Locator Security]]. 177dc6c105331e237e996b7be5fe760f41abad2e 175 174 2010-12-04T19:20:05Z Duck 2 /* Remote TLS/SSL-based Services */ wikitext text/x-wiki == Introduction == '''All''' services containing sensitive information are protected using cryptography. Whenever possible, we add the necessary configuration to ensure unsecure usages are not possible, to protect your data. Nevertheless, a few things are needed on you side to improve security, that's why we are providing the following notes in order to help you configure your software in a secure fashion. == Areas of Security == === Mails from DC's Administrators === You should not trust mails pretenting to come from us. The only way to be sure a mail is from someone, is to agree on exchanging cryptographically-protected messages. On [[Admins|this page]] you'll find the list of DC's administrators from which you may receive mails (on the users's mailing-list for example). You could trust their GPG keys directly, but that would not be secure at all. The best way is to meet, live, in a [[wikipedia:Key_signing_party|key signing party]]. If a friend has already signed our key, and is not too far from you, you may also propagate your trust to our keys. Once done, you'll be sure what seems to come from us is really from us. === Talking to the Right Machine/Service === All remote services use an address on the internet, like ''superservice.duckcorp.org'', but if you are connected through an untrusted network (like if you're using a third-party's WIFI), you cannot be sure you'll be connecting to the right machine, and you may disclose important information like your credentials. ==== TLS/SSL-based Services ==== To ensure you're talking to the right server, and noone pretend to be a DC's server to tricks you, you need to install the following certificate in your browser : [[File:Duckcorp.crt]] (clicking on the link should ask for installation, and you'll just need to confirm you trust it). ==== Service Locator Security ==== One possible attack is to alter replies from the machine locator service (DNS) in order to redirect your communication to a nasty machine. Since November 2010, ''duckcorp.org'' and ''milkypond.org'' domains are cryptographically signed using the DNSSEC system, so you are now able to verify the address returned for the service is the right one. This system is not new, but has recently switched into production, so your operating system may not yet be properly configured to use this protection. Until it is pre-configured in most of them, you may configure it yourself using [[Services/DNS#How_to_test_my_zone_is_secured.3F|this procedure]]. {{warning}} Beware this protection solves certains security problems but is not sufficient to ensure you're talking to the right machine/service. Nevertheless it ensures: * the address of the machine/service is the right one * information related to the domain, list of mail servers, security information on hosts (SSHFP)… are not tampered Using this security plus certificate verification (see [[Services/Security#Remote_TLS.2FSSL-based_Services|section about TLS/SSL-based Security]]) would ensure full security. === Secure SSH Connections === In order not to be tricked connecting to a fake server, or to a rooted server (just in case), it is possible to check the SSH key of the server. As this verification is quite boring both for administrators and users, almost nobody on earth does it. Fortunately, it is possible to publish this information in the DNS and have OpenSSH check it for you automatically. To add this security, you can edit your system configuration (''/etc/ssh/ssh_config'') or your personal one (''~/.ssh/config''), and add the folowing: Host * VerifyHostKeyDNS ask Of course, the DNS replies may be altered, so if you want full security, read the [[Services/Security#Service_Locator_Security|section about Service Locator Security]]. bd73be3a8bc4de48f851957ff648906d9ed8ec6f 176 175 2010-12-04T19:20:17Z Duck 2 /* Service Locator Security */ wikitext text/x-wiki == Introduction == '''All''' services containing sensitive information are protected using cryptography. Whenever possible, we add the necessary configuration to ensure unsecure usages are not possible, to protect your data. Nevertheless, a few things are needed on you side to improve security, that's why we are providing the following notes in order to help you configure your software in a secure fashion. == Areas of Security == === Mails from DC's Administrators === You should not trust mails pretenting to come from us. The only way to be sure a mail is from someone, is to agree on exchanging cryptographically-protected messages. On [[Admins|this page]] you'll find the list of DC's administrators from which you may receive mails (on the users's mailing-list for example). You could trust their GPG keys directly, but that would not be secure at all. The best way is to meet, live, in a [[wikipedia:Key_signing_party|key signing party]]. If a friend has already signed our key, and is not too far from you, you may also propagate your trust to our keys. Once done, you'll be sure what seems to come from us is really from us. === Talking to the Right Machine/Service === All remote services use an address on the internet, like ''superservice.duckcorp.org'', but if you are connected through an untrusted network (like if you're using a third-party's WIFI), you cannot be sure you'll be connecting to the right machine, and you may disclose important information like your credentials. ==== TLS/SSL-based Services ==== To ensure you're talking to the right server, and noone pretend to be a DC's server to tricks you, you need to install the following certificate in your browser : [[File:Duckcorp.crt]] (clicking on the link should ask for installation, and you'll just need to confirm you trust it). ==== Service Locator Security ==== One possible attack is to alter replies from the machine locator service (DNS) in order to redirect your communication to a nasty machine. Since November 2010, ''duckcorp.org'' and ''milkypond.org'' domains are cryptographically signed using the DNSSEC system, so you are now able to verify the address returned for the service is the right one. This system is not new, but has recently switched into production, so your operating system may not yet be properly configured to use this protection. Until it is pre-configured in most of them, you may configure it yourself using [[Services/DNS#How_to_test_my_zone_is_secured.3F|this procedure]]. {{warning}} Beware this protection solves certains security problems but is not sufficient to ensure you're talking to the right machine/service. Nevertheless it ensures: * the address of the machine/service is the right one * information related to the domain, list of mail servers, security information on hosts (SSHFP)… are not tampered Using this security plus certificate verification (see [[Services/Security#TLS.2FSSL-based_Services|section about TLS/SSL-based Security]]) would ensure full security. === Secure SSH Connections === In order not to be tricked connecting to a fake server, or to a rooted server (just in case), it is possible to check the SSH key of the server. As this verification is quite boring both for administrators and users, almost nobody on earth does it. Fortunately, it is possible to publish this information in the DNS and have OpenSSH check it for you automatically. To add this security, you can edit your system configuration (''/etc/ssh/ssh_config'') or your personal one (''~/.ssh/config''), and add the folowing: Host * VerifyHostKeyDNS ask Of course, the DNS replies may be altered, so if you want full security, read the [[Services/Security#Service_Locator_Security|section about Service Locator Security]]. 034ff53f26870d215f8297ef471416bd60e06235 177 176 2010-12-04T19:22:27Z Duck 2 /* TLS/SSL-based Services */ wikitext text/x-wiki == Introduction == '''All''' services containing sensitive information are protected using cryptography. Whenever possible, we add the necessary configuration to ensure unsecure usages are not possible, to protect your data. Nevertheless, a few things are needed on you side to improve security, that's why we are providing the following notes in order to help you configure your software in a secure fashion. == Areas of Security == === Mails from DC's Administrators === You should not trust mails pretenting to come from us. The only way to be sure a mail is from someone, is to agree on exchanging cryptographically-protected messages. On [[Admins|this page]] you'll find the list of DC's administrators from which you may receive mails (on the users's mailing-list for example). You could trust their GPG keys directly, but that would not be secure at all. The best way is to meet, live, in a [[wikipedia:Key_signing_party|key signing party]]. If a friend has already signed our key, and is not too far from you, you may also propagate your trust to our keys. Once done, you'll be sure what seems to come from us is really from us. === Talking to the Right Machine/Service === All remote services use an address on the internet, like ''superservice.duckcorp.org'', but if you are connected through an untrusted network (like if you're using a third-party's WIFI), you cannot be sure you'll be connecting to the right machine, and you may disclose important information like your credentials. ==== TLS/SSL-based Services ==== To ensure you're talking to the right server, and noone pretend to be a DC's server to tricks you, you need to install the [[File:Duckcorp.crt|following certificate]] in your browser (clicking on the link should ask for installation, and you'll just need to confirm you trust it). ==== Service Locator Security ==== One possible attack is to alter replies from the machine locator service (DNS) in order to redirect your communication to a nasty machine. Since November 2010, ''duckcorp.org'' and ''milkypond.org'' domains are cryptographically signed using the DNSSEC system, so you are now able to verify the address returned for the service is the right one. This system is not new, but has recently switched into production, so your operating system may not yet be properly configured to use this protection. Until it is pre-configured in most of them, you may configure it yourself using [[Services/DNS#How_to_test_my_zone_is_secured.3F|this procedure]]. {{warning}} Beware this protection solves certains security problems but is not sufficient to ensure you're talking to the right machine/service. Nevertheless it ensures: * the address of the machine/service is the right one * information related to the domain, list of mail servers, security information on hosts (SSHFP)… are not tampered Using this security plus certificate verification (see [[Services/Security#TLS.2FSSL-based_Services|section about TLS/SSL-based Security]]) would ensure full security. === Secure SSH Connections === In order not to be tricked connecting to a fake server, or to a rooted server (just in case), it is possible to check the SSH key of the server. As this verification is quite boring both for administrators and users, almost nobody on earth does it. Fortunately, it is possible to publish this information in the DNS and have OpenSSH check it for you automatically. To add this security, you can edit your system configuration (''/etc/ssh/ssh_config'') or your personal one (''~/.ssh/config''), and add the folowing: Host * VerifyHostKeyDNS ask Of course, the DNS replies may be altered, so if you want full security, read the [[Services/Security#Service_Locator_Security|section about Service Locator Security]]. 0e6da36f2e030c457986aefb397b7f6b23419935 178 177 2010-12-04T19:25:34Z Duck 2 /* TLS/SSL-based Services */ wikitext text/x-wiki == Introduction == '''All''' services containing sensitive information are protected using cryptography. Whenever possible, we add the necessary configuration to ensure unsecure usages are not possible, to protect your data. Nevertheless, a few things are needed on you side to improve security, that's why we are providing the following notes in order to help you configure your software in a secure fashion. == Areas of Security == === Mails from DC's Administrators === You should not trust mails pretenting to come from us. The only way to be sure a mail is from someone, is to agree on exchanging cryptographically-protected messages. On [[Admins|this page]] you'll find the list of DC's administrators from which you may receive mails (on the users's mailing-list for example). You could trust their GPG keys directly, but that would not be secure at all. The best way is to meet, live, in a [[wikipedia:Key_signing_party|key signing party]]. If a friend has already signed our key, and is not too far from you, you may also propagate your trust to our keys. Once done, you'll be sure what seems to come from us is really from us. === Talking to the Right Machine/Service === All remote services use an address on the internet, like ''superservice.duckcorp.org'', but if you are connected through an untrusted network (like if you're using a third-party's WIFI), you cannot be sure you'll be connecting to the right machine, and you may disclose important information like your credentials. ==== TLS/SSL-based Services ==== To ensure you're talking to the right server, and noone pretend to be a DC's server to tricks you, you need to install the following certificate ([[File:Duckcorp.crt]]) in your browser (clicking on the link should ask for installation, and you'll just need to confirm you trust it). ==== Service Locator Security ==== One possible attack is to alter replies from the machine locator service (DNS) in order to redirect your communication to a nasty machine. Since November 2010, ''duckcorp.org'' and ''milkypond.org'' domains are cryptographically signed using the DNSSEC system, so you are now able to verify the address returned for the service is the right one. This system is not new, but has recently switched into production, so your operating system may not yet be properly configured to use this protection. Until it is pre-configured in most of them, you may configure it yourself using [[Services/DNS#How_to_test_my_zone_is_secured.3F|this procedure]]. {{warning}} Beware this protection solves certains security problems but is not sufficient to ensure you're talking to the right machine/service. Nevertheless it ensures: * the address of the machine/service is the right one * information related to the domain, list of mail servers, security information on hosts (SSHFP)… are not tampered Using this security plus certificate verification (see [[Services/Security#TLS.2FSSL-based_Services|section about TLS/SSL-based Security]]) would ensure full security. === Secure SSH Connections === In order not to be tricked connecting to a fake server, or to a rooted server (just in case), it is possible to check the SSH key of the server. As this verification is quite boring both for administrators and users, almost nobody on earth does it. Fortunately, it is possible to publish this information in the DNS and have OpenSSH check it for you automatically. To add this security, you can edit your system configuration (''/etc/ssh/ssh_config'') or your personal one (''~/.ssh/config''), and add the folowing: Host * VerifyHostKeyDNS ask Of course, the DNS replies may be altered, so if you want full security, read the [[Services/Security#Service_Locator_Security|section about Service Locator Security]]. e51c3c5d5022472937f8f46de9855e4a3df6e77d 179 178 2010-12-04T21:32:34Z Duck 2 /* TLS/SSL-based Services */ wikitext text/x-wiki == Introduction == '''All''' services containing sensitive information are protected using cryptography. Whenever possible, we add the necessary configuration to ensure unsecure usages are not possible, to protect your data. Nevertheless, a few things are needed on you side to improve security, that's why we are providing the following notes in order to help you configure your software in a secure fashion. == Areas of Security == === Mails from DC's Administrators === You should not trust mails pretenting to come from us. The only way to be sure a mail is from someone, is to agree on exchanging cryptographically-protected messages. On [[Admins|this page]] you'll find the list of DC's administrators from which you may receive mails (on the users's mailing-list for example). You could trust their GPG keys directly, but that would not be secure at all. The best way is to meet, live, in a [[wikipedia:Key_signing_party|key signing party]]. If a friend has already signed our key, and is not too far from you, you may also propagate your trust to our keys. Once done, you'll be sure what seems to come from us is really from us. === Talking to the Right Machine/Service === All remote services use an address on the internet, like ''superservice.duckcorp.org'', but if you are connected through an untrusted network (like if you're using a third-party's WIFI), you cannot be sure you'll be connecting to the right machine, and you may disclose important information like your credentials. ==== TLS/SSL-based Services ==== To ensure you're talking to the right server, and noone pretend to be a DC's server to tricks you, you need to install the following certificate ([[File:Duckcorp.crt]]): * either in your software configuration (for example, to validate HTTP site in your browser, clicking on the link should ask for installation, and you'll just need to confirm you trust it) * or globally on your host by installing the certificate, as root, in ''/etc/ssl/certs'' and running ''c_rehash'' ==== Service Locator Security ==== One possible attack is to alter replies from the machine locator service (DNS) in order to redirect your communication to a nasty machine. Since November 2010, ''duckcorp.org'' and ''milkypond.org'' domains are cryptographically signed using the DNSSEC system, so you are now able to verify the address returned for the service is the right one. This system is not new, but has recently switched into production, so your operating system may not yet be properly configured to use this protection. Until it is pre-configured in most of them, you may configure it yourself using [[Services/DNS#How_to_test_my_zone_is_secured.3F|this procedure]]. {{warning}} Beware this protection solves certains security problems but is not sufficient to ensure you're talking to the right machine/service. Nevertheless it ensures: * the address of the machine/service is the right one * information related to the domain, list of mail servers, security information on hosts (SSHFP)… are not tampered Using this security plus certificate verification (see [[Services/Security#TLS.2FSSL-based_Services|section about TLS/SSL-based Security]]) would ensure full security. === Secure SSH Connections === In order not to be tricked connecting to a fake server, or to a rooted server (just in case), it is possible to check the SSH key of the server. As this verification is quite boring both for administrators and users, almost nobody on earth does it. Fortunately, it is possible to publish this information in the DNS and have OpenSSH check it for you automatically. To add this security, you can edit your system configuration (''/etc/ssh/ssh_config'') or your personal one (''~/.ssh/config''), and add the folowing: Host * VerifyHostKeyDNS ask Of course, the DNS replies may be altered, so if you want full security, read the [[Services/Security#Service_Locator_Security|section about Service Locator Security]]. 4b9d09cd63270fd6374d680132095e18a14b938f 180 179 2010-12-04T21:40:11Z Duck 2 /* TLS/SSL-based Services */ wikitext text/x-wiki == Introduction == '''All''' services containing sensitive information are protected using cryptography. Whenever possible, we add the necessary configuration to ensure unsecure usages are not possible, to protect your data. Nevertheless, a few things are needed on you side to improve security, that's why we are providing the following notes in order to help you configure your software in a secure fashion. == Areas of Security == === Mails from DC's Administrators === You should not trust mails pretenting to come from us. The only way to be sure a mail is from someone, is to agree on exchanging cryptographically-protected messages. On [[Admins|this page]] you'll find the list of DC's administrators from which you may receive mails (on the users's mailing-list for example). You could trust their GPG keys directly, but that would not be secure at all. The best way is to meet, live, in a [[wikipedia:Key_signing_party|key signing party]]. If a friend has already signed our key, and is not too far from you, you may also propagate your trust to our keys. Once done, you'll be sure what seems to come from us is really from us. === Talking to the Right Machine/Service === All remote services use an address on the internet, like ''superservice.duckcorp.org'', but if you are connected through an untrusted network (like if you're using a third-party's WIFI), you cannot be sure you'll be connecting to the right machine, and you may disclose important information like your credentials. ==== TLS/SSL-based Services ==== To ensure you're talking to the right server, and noone pretend to be a DC's server to tricks you, you need to install the following certificate ([[File:Duckcorp.crt]]): * either in your software configuration (for example, to validate HTTP site in your browser, clicking on the link should ask for installation, and you'll just need to confirm you trust it) * or globally on your host by installing the certificate, as root: ** (method 1, prefered) in ''/usr/local/share/ca-certificates'', and running ''update-ca-certificates'' ** (method 2, not suitable for GNUTLS-based apps) in ''/etc/ssl/certs'', and running ''c_rehash'' ==== Service Locator Security ==== One possible attack is to alter replies from the machine locator service (DNS) in order to redirect your communication to a nasty machine. Since November 2010, ''duckcorp.org'' and ''milkypond.org'' domains are cryptographically signed using the DNSSEC system, so you are now able to verify the address returned for the service is the right one. This system is not new, but has recently switched into production, so your operating system may not yet be properly configured to use this protection. Until it is pre-configured in most of them, you may configure it yourself using [[Services/DNS#How_to_test_my_zone_is_secured.3F|this procedure]]. {{warning}} Beware this protection solves certains security problems but is not sufficient to ensure you're talking to the right machine/service. Nevertheless it ensures: * the address of the machine/service is the right one * information related to the domain, list of mail servers, security information on hosts (SSHFP)… are not tampered Using this security plus certificate verification (see [[Services/Security#TLS.2FSSL-based_Services|section about TLS/SSL-based Security]]) would ensure full security. === Secure SSH Connections === In order not to be tricked connecting to a fake server, or to a rooted server (just in case), it is possible to check the SSH key of the server. As this verification is quite boring both for administrators and users, almost nobody on earth does it. Fortunately, it is possible to publish this information in the DNS and have OpenSSH check it for you automatically. To add this security, you can edit your system configuration (''/etc/ssh/ssh_config'') or your personal one (''~/.ssh/config''), and add the folowing: Host * VerifyHostKeyDNS ask Of course, the DNS replies may be altered, so if you want full security, read the [[Services/Security#Service_Locator_Security|section about Service Locator Security]]. d0d8c09678f9abb841ec4695d817c11faffcd03b 181 180 2010-12-04T21:42:16Z Duck 2 /* TLS/SSL-based Services */ wikitext text/x-wiki == Introduction == '''All''' services containing sensitive information are protected using cryptography. Whenever possible, we add the necessary configuration to ensure unsecure usages are not possible, to protect your data. Nevertheless, a few things are needed on you side to improve security, that's why we are providing the following notes in order to help you configure your software in a secure fashion. == Areas of Security == === Mails from DC's Administrators === You should not trust mails pretenting to come from us. The only way to be sure a mail is from someone, is to agree on exchanging cryptographically-protected messages. On [[Admins|this page]] you'll find the list of DC's administrators from which you may receive mails (on the users's mailing-list for example). You could trust their GPG keys directly, but that would not be secure at all. The best way is to meet, live, in a [[wikipedia:Key_signing_party|key signing party]]. If a friend has already signed our key, and is not too far from you, you may also propagate your trust to our keys. Once done, you'll be sure what seems to come from us is really from us. === Talking to the Right Machine/Service === All remote services use an address on the internet, like ''superservice.duckcorp.org'', but if you are connected through an untrusted network (like if you're using a third-party's WIFI), you cannot be sure you'll be connecting to the right machine, and you may disclose important information like your credentials. ==== TLS/SSL-based Services ==== To ensure you're talking to the right server, and noone pretend to be a DC's server to tricks you, you need to install the following certificate ([[File:Duckcorp.crt]]): * either in your software configuration (for example, to validate HTTP site in your browser, clicking on the link should ask for installation, and you'll just need to confirm you trust it) * or globally on your host by installing the certificate, as root: ** (method 1, prefered) in ''/usr/local/share/ca-certificates'', and running ''update-ca-certificates'' (the ''ca-certificates'' package needs to be installed) ** (method 2, not suitable for GNUTLS-based apps) in ''/etc/ssl/certs'', and running ''c_rehash'' (the ''openssl'' package needs to be installed) ==== Service Locator Security ==== One possible attack is to alter replies from the machine locator service (DNS) in order to redirect your communication to a nasty machine. Since November 2010, ''duckcorp.org'' and ''milkypond.org'' domains are cryptographically signed using the DNSSEC system, so you are now able to verify the address returned for the service is the right one. This system is not new, but has recently switched into production, so your operating system may not yet be properly configured to use this protection. Until it is pre-configured in most of them, you may configure it yourself using [[Services/DNS#How_to_test_my_zone_is_secured.3F|this procedure]]. {{warning}} Beware this protection solves certains security problems but is not sufficient to ensure you're talking to the right machine/service. Nevertheless it ensures: * the address of the machine/service is the right one * information related to the domain, list of mail servers, security information on hosts (SSHFP)… are not tampered Using this security plus certificate verification (see [[Services/Security#TLS.2FSSL-based_Services|section about TLS/SSL-based Security]]) would ensure full security. === Secure SSH Connections === In order not to be tricked connecting to a fake server, or to a rooted server (just in case), it is possible to check the SSH key of the server. As this verification is quite boring both for administrators and users, almost nobody on earth does it. Fortunately, it is possible to publish this information in the DNS and have OpenSSH check it for you automatically. To add this security, you can edit your system configuration (''/etc/ssh/ssh_config'') or your personal one (''~/.ssh/config''), and add the folowing: Host * VerifyHostKeyDNS ask Of course, the DNS replies may be altered, so if you want full security, read the [[Services/Security#Service_Locator_Security|section about Service Locator Security]]. 90b59a973d6697dcfa58fb34b8a6d1a6de4358fd 0 47 163 2010-12-04T18:13:19Z Duck 2 Created page with "Here is the list of '''current''' DuckCorp's administrators. These are the only people which have full access to the system (even if we may delegate nonsensitive things to truste…" wikitext text/x-wiki Here is the list of '''current''' DuckCorp's administrators. These are the only people which have full access to the system (even if we may delegate nonsensitive things to trusted parties, but you'll always be warned of such changes). == Active administrators == * Duck: *: Full Name: Marc Dequènes *: GPG Key Fingerprint: 6ADD 5093 AC6D 1072 C912 9000 B1CC D972 9026 7086 == Fallback administrators == * Arnau: *: Full Name: Arnaud Fontaine *: GPG Key Fingerprint: D792 B8A5 A567 B001 C342 2613 BDF2 A220 5E36 19D3 e3a34bd81404053010a46b1b2cc6e005da091d6f 168 163 2010-12-04T18:28:28Z Duck 2 Protected "[[Admins]]" ([edit=sysop] (indefinite) [move=sysop] (indefinite)) wikitext text/x-wiki Here is the list of '''current''' DuckCorp's administrators. These are the only people which have full access to the system (even if we may delegate nonsensitive things to trusted parties, but you'll always be warned of such changes). == Active administrators == * Duck: *: Full Name: Marc Dequènes *: GPG Key Fingerprint: 6ADD 5093 AC6D 1072 C912 9000 B1CC D972 9026 7086 == Fallback administrators == * Arnau: *: Full Name: Arnaud Fontaine *: GPG Key Fingerprint: D792 B8A5 A567 B001 C342 2613 BDF2 A220 5E36 19D3 e3a34bd81404053010a46b1b2cc6e005da091d6f 0 36 169 84 2010-12-04T18:29:06Z Duck 2 wikitext text/x-wiki {{Robelbox|title=Association|theme={{{theme|3}}}}} {{Padbox}} Here are bits of information about us: * [[A bit of History]] * [[DcExpenses|Association expenses]] * [[DcDonation|How and why make a donation]] * [[Admins|List of DuckCorp's Administrators]] {{Padbox/close}} {{Robelbox/close}} 715cc7cfa570200492d82747c097a2a6f24cd7ae 0 33 182 127 2011-01-26T00:13:44Z Duck 2 /* List of Previous Contributions */ wikitext text/x-wiki DuckCorp is built and maintained by volunteers, mostly with their own money. The services are totaly free of charge for all users, but you may wish to contribute to help us keep it working well and improve. == How to Contribute ? == You can help us with: * sponsoring: if you can host a machine and/or provide connectivity * equipements: see the list of possible improvements below * money: you can send us money which will be used in the association: ** by check (see the duckcorp.org whois for Duck's postal address, or ask him by mail or IRC) ** by Paypal to duck@duckcorp.org == What can you Contribute ? == Here are ideas on which to contribute: * [[DcExpenses#Regular_Expenses|regular expenses]] * [???] buy a new machine, to provide: VMs, more services redondancy, ... (needed hardware not yet evaluated, more on this later) * [~120€] add a battery backup unit for Toushirou's 3ware card (for more data security, as datacenters tends to be less and less reliable) * [??? (quite expensive)] change Orfeo's backplane to have 4 disks slot instead of 2, and add 2 new disks (in a new RAID 1 array), planned at least 120GB capacity (2.5″ 10000 RPM SAS, like the other ones) (can be bought anywhere, but proprietary braquets needed) == List of Previous Contributions == Only pure financial contributions are listed here; equipments and sponsored purchases are listed on the [[DcExpenses|DuckCorp expenses page]]. {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Amount !! Donnor !! Comments |- | 2010-05-16 || 42€ || Chloé |- | 2011-01-10 || 500€ || AnonymousDonnor1 |} Note: early contributions in the CoinNetwork projects are not taken into account, as most information is lost. 2768365f819fe04abcf96d47f2968da66f705a8c 183 182 2011-01-26T00:14:01Z Duck 2 /* List of Previous Contributions */ wikitext text/x-wiki DuckCorp is built and maintained by volunteers, mostly with their own money. The services are totaly free of charge for all users, but you may wish to contribute to help us keep it working well and improve. == How to Contribute ? == You can help us with: * sponsoring: if you can host a machine and/or provide connectivity * equipements: see the list of possible improvements below * money: you can send us money which will be used in the association: ** by check (see the duckcorp.org whois for Duck's postal address, or ask him by mail or IRC) ** by Paypal to duck@duckcorp.org == What can you Contribute ? == Here are ideas on which to contribute: * [[DcExpenses#Regular_Expenses|regular expenses]] * [???] buy a new machine, to provide: VMs, more services redondancy, ... (needed hardware not yet evaluated, more on this later) * [~120€] add a battery backup unit for Toushirou's 3ware card (for more data security, as datacenters tends to be less and less reliable) * [??? (quite expensive)] change Orfeo's backplane to have 4 disks slot instead of 2, and add 2 new disks (in a new RAID 1 array), planned at least 120GB capacity (2.5″ 10000 RPM SAS, like the other ones) (can be bought anywhere, but proprietary braquets needed) == List of Previous Contributions == Only pure financial contributions are listed here; equipments and sponsored purchases are listed on the [[DcExpenses|DuckCorp expenses page]]. {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Amount !! Donnor !! Comments |- | 2010-05-16 || 42€ || Chloé || |- | 2011-01-10 || 500€ || AnonymousDonnor1 || |} Note: early contributions in the CoinNetwork projects are not taken into account, as most information is lost. 87d310438b5ca3550e593e104c3848ebf332c9bd 184 183 2011-01-26T00:14:49Z Duck 2 /* List of Previous Contributions */ wikitext text/x-wiki DuckCorp is built and maintained by volunteers, mostly with their own money. The services are totaly free of charge for all users, but you may wish to contribute to help us keep it working well and improve. == How to Contribute ? == You can help us with: * sponsoring: if you can host a machine and/or provide connectivity * equipements: see the list of possible improvements below * money: you can send us money which will be used in the association: ** by check (see the duckcorp.org whois for Duck's postal address, or ask him by mail or IRC) ** by Paypal to duck@duckcorp.org == What can you Contribute ? == Here are ideas on which to contribute: * [[DcExpenses#Regular_Expenses|regular expenses]] * [???] buy a new machine, to provide: VMs, more services redondancy, ... (needed hardware not yet evaluated, more on this later) * [~120€] add a battery backup unit for Toushirou's 3ware card (for more data security, as datacenters tends to be less and less reliable) * [??? (quite expensive)] change Orfeo's backplane to have 4 disks slot instead of 2, and add 2 new disks (in a new RAID 1 array), planned at least 120GB capacity (2.5″ 10000 RPM SAS, like the other ones) (can be bought anywhere, but proprietary braquets needed) == List of Previous Contributions == Only pure financial contributions are listed here; equipments and sponsored purchases are listed on the [[DcExpenses|DuckCorp expenses page]]. {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Amount !! Donnor !! Comments |- | 2010-05-16 || 42€ || Chloé || |- | 2011-01-10 || 500€ || AnonymousDonnor1 || |} Note: early contributions in the CoinNetwork project are not taken into account, as most information is lost. 8e1faf9d0259737d69861cbf821d3307e5a00162 0 38 185 128 2011-02-15T23:18:05Z Duck 2 /* Usage */ wikitext text/x-wiki We are working to give users more control on their own resources, but it is a difficult task. We are working on a tool, but it is still heavily work in progress. It works correctly, but its skill is currently limited to a few tasks. == Requirements == This tool is accessible through a mail interface (later, we might add other types of frontends), and does care about security and privacy. You need to get a GPG/PGP key, and get it registered in a safe manner in our database (contact an administrator for this). If you hate english, you might also ask an administration to change your language preferences. The mail should be RFC3156-compliant, and should not use the combined method described in chapter 6.2 of this RFC (not supported yet). == Usage == Once it is done, you just need to send a signed mail to "MilkyPond Administration Officer" <banya@milkypond.org> with a list of commands in the body. Empty lines and comments (lines starting with "#") are ignored. The subject is purely informational, for you to identify the reply to the corresponding demand. As you may send '''secret''' information in the mail, you would like to hide it. Use the key EF410567 (fingerprint: D0CC BBA5 5460 719D 515C 11E6 E770 C685 EF41 0567), signed by the DuckCorp Administrators, for encryption. This is an optional, but recommended, feature. == Available Languages == * en * fr The setting follow the RFC 2616 Accept-Language field syntax. == Available Commands == === DNS management === Beware to properly update the serial! Available commands: * DNS INFO : to get the list of DNS zones you can manage (and probably more in the future) * DNS GET ZONE &lt;zone&gt; : to get the DNS &lt;zone&gt; content (attached in the reply) * DNS SET ZONE &lt;zone&gt; @&lt;i&gt; : to replace the current DNS &lt;zone&gt; content with the &lt;i&gt;st/nd/rd/th attachment (text/plain accepted only) : the zone syntax is checked before replacement Notes for signed zones: * the support for signed zone is basic, no specific information or possibility to setup any parameter yet * the fetched zone (with the GET command) does not reflect the real serial, as the signer process update the serial automatically when resigning the zone, so you need to ask for the current serial with the following command: host -t soa <zone> == Project Info == Please see https://projects.duckcorp.org/projects/cyborghood. 1eee03bf9e0d017d5e303a5c768fe4d9c30de13b 186 185 2011-02-15T23:19:11Z Duck 2 /* Requirements */ wikitext text/x-wiki We are working to give users more control on their own resources, but it is a difficult task. We are working on a tool, but it is still heavily work in progress. It works correctly, but its skill is currently limited to a few tasks. == Requirements == This tool is accessible through a mail interface (later, we might add other types of frontends), and does care about security and privacy. You need to get a GPG/PGP key, and get it registered in a safe manner in our database (contact an administrator for this). If you hate english, you might also ask an administration to change your language preferences. The mail should be RFC3156-compliant, and should not use the combined method (inline signing, like with mailcrypt) described in chapter 6.2 of this RFC (not supported yet). == Usage == Once it is done, you just need to send a signed mail to "MilkyPond Administration Officer" <banya@milkypond.org> with a list of commands in the body. Empty lines and comments (lines starting with "#") are ignored. The subject is purely informational, for you to identify the reply to the corresponding demand. As you may send '''secret''' information in the mail, you would like to hide it. Use the key EF410567 (fingerprint: D0CC BBA5 5460 719D 515C 11E6 E770 C685 EF41 0567), signed by the DuckCorp Administrators, for encryption. This is an optional, but recommended, feature. == Available Languages == * en * fr The setting follow the RFC 2616 Accept-Language field syntax. == Available Commands == === DNS management === Beware to properly update the serial! Available commands: * DNS INFO : to get the list of DNS zones you can manage (and probably more in the future) * DNS GET ZONE &lt;zone&gt; : to get the DNS &lt;zone&gt; content (attached in the reply) * DNS SET ZONE &lt;zone&gt; @&lt;i&gt; : to replace the current DNS &lt;zone&gt; content with the &lt;i&gt;st/nd/rd/th attachment (text/plain accepted only) : the zone syntax is checked before replacement Notes for signed zones: * the support for signed zone is basic, no specific information or possibility to setup any parameter yet * the fetched zone (with the GET command) does not reflect the real serial, as the signer process update the serial automatically when resigning the zone, so you need to ask for the current serial with the following command: host -t soa <zone> == Project Info == Please see https://projects.duckcorp.org/projects/cyborghood. d28eb85cbf00dee6cfd6cf111f90c1c120328707 0 30 187 140 2011-03-26T00:30:55Z Duck 2 /* The DuckCorp Story */ wikitext text/x-wiki == The DuckCorp Story == DuckCorp was born in 2000, from Duck's will to construct something more personal out of the CoinNetwork student house's LAN. At that time, it was merely a simple website, advertising a few personal projects. Later, several machines, gathered with various parts from people willing to dispose of them, used the 'duckcorp.org' domain name and provided services for CoinNetwork; this was the begining of the DC's sponsoring mission. Duck then met Rtp, and they began sharing about system administration topics. As they were willing to administrate CoinNetwork better, they began working on the infrastructure and tools together. Rtp created RtpNet, and received the magical SSH key to be a full DC administrator (so did Duck for Rtpnet indeed). They developed a software prototype aimed at managing the most important services of a distributed web of servers (LMS, LDAP Management System), which helped reducing the daily burden of CoinNetwork's administration a lot. After a while working hand in hand, they both found a job and moved to a new home, still helping each other when possible. Currently, RtpNet and DuckCorp have different goals, and follow their own path. On the way, DC found friendly sponsors (in order of appearance): * Nerim (first Orfeo's housing, IPv6 block, indirect sponsor via Hivane) * Hivane (global connectivity, secondary NS and MX) * Sivit (special accomodations for Toushirou's housing and connectivity) (now Nerim again, as it was acquired recently) * Alionis (Orfeo's housing) Thanks a lot pals :-). == The MilkyPond Project == MP is an historical share of an IRC network between DC and RN when they both stopped working on the CoinNetwork project. They were willing to cooperate but with the important changes that occurred in their lives, only IRC was kept as a communication link. With time going, DC began recreating services, with the main server Orfeo being kindly sponsored by Nerim, which was used by RN and later by other associations or individuals. Nothing much is done in the name of MP until 2007, besides adding a Jabber server. In early 2007, RN hired a server, Lechat (Dédibox), and was willing to participate more in the share. At the end of the year, T1R joined to help improving the IRC Network. In September 2007, RN was not able to provide services anymore, as it was too much of a burden. Nevertheless, it is still sponsoring the ''milkypond.org'' domain since then. == Key Dates == * 2000-05-22: DuckCorp is created * 2003-04-25: IANA PEN 16829 * 2003-07-09: RtpNet is created * ~2003-10-20: RSA key exchanged between DC and RN (date is from the exif info, but Photoshop is in the way) * 2004-06-12: MilkyPond is created (after DC and RN stopped working on the CoinNetwork project) * 2005-04/05: Orfeo RAM upgraded (512Mo->1.5Go) (blocked to ~800Mo [[Media:Orfeo.duckcorp.org-memory-day.png|until highmem in kernel]]) * 2005-05: IPv6 Ready (using a tunnel) * 2005-11-17: the users' mailing-list started * 2005-11: major mail system improvements (SMTP auth, improved antispam, webdesk) * 2005-12-08: Orfeo moved from the Nerim's Ivry datacenter to the Nerim suite in the LDCOM Courbevoie datacenter * 2006-01 to 2006-06: Orfeo problems due to an [http://xfs.org/index.php/XFS_FAQ#Q:_What_is_the_issue_with_directory_corruption_in_Linux_2.6.17.3F XFS bug] * 2007-04: IPv6 Ready (native IPv6) * 2007-07: Tōshirō bought and being prepared * 2007-08-08: Nerim's boss shutdown Orfeo violently; quickly repaired and setup behind a mere ADSL (helped by Nerim friends), but BLACKOUT for most services * 2007-08-13: Tōshirō installed in the Sivit suite of the Redbus datacenter, services progressively back online * 2007-09: LDAP infrastructure (again) * 2007-12: Orfeo-NG bough and installed in Alionis suite in EQX (Equinix) datacenter * 2007-12: T1R enters MilkyPond (for the IRC network) * 2008-07: VCS rework, Portal (Restricted Access Helper), Projects Manager (Redmine) * 2009-03: Banya bot (mail gateway for DNS modification, part of the CyborgHood project) * 2009-09: Orfeo moved to [http://www.alionis.net/infra/VBO.html Alionis VBO datacenter] * 2010-03: Thorfinn acquired (Nerim VDS) * 2010-04-24: stratum 2 NTP server [http://support.ntp.org/bin/view/Servers/NtpDuckCorpOrg publicly advertised] and in the [http://www.pool.ntp.org/user/DuckCorp pool] * 2010-05-22: 10th Anniversary !!! * 2010-05-29: 10th Anniversary party with users/sponsors/friends * 2010-10: DNS TSIG and DNSSEC == Admins == * Arnau [~2004-12 to now] (fallback admin since 2010-04-27) * Duck [begining to now] (leader) * Finger [2006-07-05 to 2008-02-04] (assistant) * Mmenal [~2004-12 to ~2006-07] * Rtp [2003-10 to 2007-07-15] == Evolution == No real traces were kept, so old numbers are mere rough guess. * 2000 -> 2004 ** more than 60 users served in the [[Media:Coinnetwork resal 2001-2002.png|CoinNetwork LAN]], nearly no external services besides a basic website and IRC ** services targeted for the CoinNetwork LAN * 2004 -> 2007 ** a few users (probably around 20) and 2 entities (RtpNet and [http://www.hurdfr.org/ HurdFr]) hosted ** more Internet-oriented services (complete mail software suite, MLs, Web hosting, DBs, RCS, ...) * 2007 -> 2010 ** more users (nearly 70 users in 2010, a few not very active) and 2 more entity hosted ([http://thebrain.lautre.net/ TheBrain] and [http://www.andesi.org/ Andesi]) ** more services (Jabber, user-friendly antispam, LDAP, IPv6, ...) == Photos == Look at the [http://photos.duckcorp.org/v/duckcorp/ gallery]. 14633d7393c95adc7eb8f5d0c88348930ccaf08c 0 48 189 2011-05-08T19:05:29Z Duck 2 Created page with "Besides critical system and services data, most of users data are backuped up too. Data you can expect being saved: * mails, along with antispam learning data and SIEVE filters …" wikitext text/x-wiki Besides critical system and services data, most of users data are backuped up too. Data you can expect being saved: * mails, along with antispam learning data and SIEVE filters * shared services configurations and personnal data (webmail, webdesk, projects, jabber, web stats, VCS…) * web data (hosted websites) * FTP data * /home on all machines where users can have shell access * /private on Toushirou A few files or directory names are globally excluded from backup: * cache * .Trash In your personnal data, you can choose to exclude directories (and their children), either because you don't want us to copy your data elsewhere, or because it is not needed (allowing us to save data on the backup system). To do that, you simply need to create a ''.nobackup'' file inside the directories to ignore, nothing more. The backup system would detect it and skip the whole directory over. 57d5bc6e9a049c5938782827bfc325313906d9b5 0 49 191 2011-05-14T19:16:07Z Duck 2 Created page with "== Mail Hosting == What we can offer: * full hosting (MX1) on our servers: ** multiple email addresses which can be real mailboxes or mere redirections at another third party ad…" wikitext text/x-wiki == Mail Hosting == What we can offer: * full hosting (MX1) on our servers: ** multiple email addresses which can be real mailboxes or mere redirections at another third party addresses ** based on ''milkypond.org'' (or maybe ''duckcorp.org'') domain(s) or you own domain(s) * fallback retention (MX2) on our servers or, at your choice, partner servers (currently via Hivane) == Full Hosting == === Access Methods === You can retrieve your mails, in case of a real mailbox, using: * IMAP+TLS/IMAPS * POP3S -> send === Mail Filtering === === Shared/Public Folders === == Retention fallback == The current retention period on our servers is 2 weeks, but can be temporary or permanently increased if needed. ad286c76bdb7b18c551b745ce88d274fc2f0a7a0 192 191 2011-05-14T20:22:09Z Duck 2 /* Full Hosting */ wikitext text/x-wiki == Mail Hosting == What we can offer: * full hosting (MX1) on our servers: ** multiple email addresses which can be real mailboxes or mere redirections at another third party addresses ** based on ''milkypond.org'' (or maybe ''duckcorp.org'') domain(s) or you own domain(s) * fallback retention (MX2) on our servers or, at your choice, partner servers (currently via Hivane) == Full Hosting == === Access Methods === You can retrieve your mails, in case of a real mailbox, using: * IMAP+TLS (TCP 143) / IMAPS (TCP 993) on imap.duckcorp.org * or POP3+TLS (TCP 110) / POP3S (TCP 995) on pop.duckcorp.org The IMAP protocol is recommanded, as it provides many interresting features. If you want to download all your mails absolutely at home, loosing the ability to read your mail from anywhere on the planet, you can do that with IMAP too (look at your mail client settings). You can use our servers to send mails out too via smtp.duckcorp.org using: * SMTP+TLS (TCP 25) / SMTPS (TCP 465) * and SASL authentication === Mail Filtering === === Shared/Public Folders === == Retention fallback == The current retention period on our servers is 2 weeks, but can be temporary or permanently increased if needed. 748a1bf03186000a7ce36679f51707816abfe17a 193 192 2011-05-14T20:34:05Z Duck 2 /* Full Hosting */ wikitext text/x-wiki == Mail Hosting == What we can offer: * full hosting (MX1) on our servers: ** multiple email addresses which can be real mailboxes or mere redirections at another third party addresses ** based on ''milkypond.org'' (or maybe ''duckcorp.org'') domain(s) or you own domain(s) * fallback retention (MX2) on our servers or, at your choice, partner servers (currently via Hivane) == Full Hosting == === Access Methods === You can retrieve your mails, in case of a real mailbox, using: * IMAP+TLS (TCP 143) / IMAPS (TCP 993) on imap.duckcorp.org * or POP3+TLS (TCP 110) / POP3S (TCP 995) on pop.duckcorp.org The IMAP protocol is recommanded, as it provides many interresting features. If you want to download all your mails absolutely at home, loosing the ability to read your mail from anywhere on the planet, you can do that with IMAP too (look at your mail client settings). You can use our servers to send mails out too via smtp.duckcorp.org using: * SMTP+TLS (TCP 25) / SMTPS (TCP 465) * and SASL authentication === Mail Filtering === With your favourite mail client, you can probably filter your mails in proper folders already. Nevertheless, this can be a annoying operation: * blocking you mail client for a long time if you have to process plenty of mails * downloading each mail information, and sometimes content (depending on your filters), is lenghty too, and cost much bandwidth * syncing filters accross your machines (home desktop, laptop, office machine…) is a pain in the ass * processing only when you're online prevents triggering actions in a timely manner (automatic redirect, vacation messages…), and running a machine 24/7 with a mail client polling new mails every 30s is not a solution We provide a much better way to do this using the SIEVE filters. === Shared/Public Folders === == Retention fallback == The current retention period on our servers is 2 weeks, but can be temporary or permanently increased if needed. cf9c526588413fc30ed8326f1a840c0f7d243bc5 194 193 2011-05-14T20:55:11Z Duck 2 /* Mail Filtering */ wikitext text/x-wiki == Mail Hosting == What we can offer: * full hosting (MX1) on our servers: ** multiple email addresses which can be real mailboxes or mere redirections at another third party addresses ** based on ''milkypond.org'' (or maybe ''duckcorp.org'') domain(s) or you own domain(s) * fallback retention (MX2) on our servers or, at your choice, partner servers (currently via Hivane) == Full Hosting == === Access Methods === You can retrieve your mails, in case of a real mailbox, using: * IMAP+TLS (TCP 143) / IMAPS (TCP 993) on imap.duckcorp.org * or POP3+TLS (TCP 110) / POP3S (TCP 995) on pop.duckcorp.org The IMAP protocol is recommanded, as it provides many interresting features. If you want to download all your mails absolutely at home, loosing the ability to read your mail from anywhere on the planet, you can do that with IMAP too (look at your mail client settings). You can use our servers to send mails out too via smtp.duckcorp.org using: * SMTP+TLS (TCP 25) / SMTPS (TCP 465) * and SASL authentication === Mail Filtering === With your favourite mail client, you can probably filter your mails in proper folders already. Nevertheless, this can be a annoying operation: * blocking you mail client for a long time if you have to process plenty of mails * downloading each mail information, and sometimes content (depending on your filters), is lenghty too, and cost much bandwidth * syncing filters accross your machines (home desktop, laptop, office machine…) is a pain in the ass * processing only when you're online prevents triggering actions in a timely manner (automatic redirect, vacation messages…), and running a machine 24/7 with a mail client polling new mails every 30s is not a solution We provide a much better way to do this using the [[wikipedia:Sieve_(mail_filtering_language)|SIEVE]] filters. Shortly, SIEVE is a language dedicated to expressing mail filters. Our server is able to process your mails according to these filters as soon as they arrive. You then don't have to care about them anymore, and may use light mail clients or webmails when you're not on your machine with your favourite software. To push your filters on the server, a dedicated protocol exists: MANAGESIEVE (TCP 4190) on sieve.duckcorp.org Several softwares support managing SIEVE rules: * Icedove/Thunderbird using the SIEVE extension (in xul-ext-sieve Debian package) provides a rules editor * Horde (Ingo) provides an easy to use web interface * Squirrelmail with the Avelsieve extension provides an easy to use web interface * Roundcube with an extension provides an easy to use web interface * sieve-connect provides a CLI to upload/download/activate your rules files (tell us if you know more software supporting this feature) You can read more info about SIEVE here: * http://www.fastmail.fm/docs/sieve/ * http://sieve.info/ === Shared/Public Folders === == Retention fallback == The current retention period on our servers is 2 weeks, but can be temporary or permanently increased if needed. 7036bfdc94e913ffcea535add0398374138a2bf5 195 194 2011-05-14T20:56:55Z Duck 2 /* Access Methods */ wikitext text/x-wiki == Mail Hosting == What we can offer: * full hosting (MX1) on our servers: ** multiple email addresses which can be real mailboxes or mere redirections at another third party addresses ** based on ''milkypond.org'' (or maybe ''duckcorp.org'') domain(s) or you own domain(s) * fallback retention (MX2) on our servers or, at your choice, partner servers (currently via Hivane) == Full Hosting == === Access Methods === You can retrieve your mails, in case of a real mailbox, using: * IMAP+TLS (TCP 143) / IMAPS (TCP 993) on imap.duckcorp.org * or POP3+TLS (TCP 110) / POP3S (TCP 995) on pop.duckcorp.org * or one of the [https://webmail.duckcorp.org/ provided webmails] The IMAP protocol is recommended over POP3, as it provides many interresting features. If you want to download all your mails absolutely at home, loosing the ability to read your mail from anywhere on the planet, you can do that with IMAP too (look at your mail client settings). You can use our servers to send mails out too via smtp.duckcorp.org using: * SMTP+TLS (TCP 25) / SMTPS (TCP 465) * and SASL authentication === Mail Filtering === With your favourite mail client, you can probably filter your mails in proper folders already. Nevertheless, this can be a annoying operation: * blocking you mail client for a long time if you have to process plenty of mails * downloading each mail information, and sometimes content (depending on your filters), is lenghty too, and cost much bandwidth * syncing filters accross your machines (home desktop, laptop, office machine…) is a pain in the ass * processing only when you're online prevents triggering actions in a timely manner (automatic redirect, vacation messages…), and running a machine 24/7 with a mail client polling new mails every 30s is not a solution We provide a much better way to do this using the [[wikipedia:Sieve_(mail_filtering_language)|SIEVE]] filters. Shortly, SIEVE is a language dedicated to expressing mail filters. Our server is able to process your mails according to these filters as soon as they arrive. You then don't have to care about them anymore, and may use light mail clients or webmails when you're not on your machine with your favourite software. To push your filters on the server, a dedicated protocol exists: MANAGESIEVE (TCP 4190) on sieve.duckcorp.org Several softwares support managing SIEVE rules: * Icedove/Thunderbird using the SIEVE extension (in xul-ext-sieve Debian package) provides a rules editor * Horde (Ingo) provides an easy to use web interface * Squirrelmail with the Avelsieve extension provides an easy to use web interface * Roundcube with an extension provides an easy to use web interface * sieve-connect provides a CLI to upload/download/activate your rules files (tell us if you know more software supporting this feature) You can read more info about SIEVE here: * http://www.fastmail.fm/docs/sieve/ * http://sieve.info/ === Shared/Public Folders === == Retention fallback == The current retention period on our servers is 2 weeks, but can be temporary or permanently increased if needed. 10ce067ad094b9f7eb3cf8a3aea3b550af82c1fd 196 195 2011-05-14T21:41:59Z Duck 2 /* Shared/Public Folders */ wikitext text/x-wiki == Mail Hosting == What we can offer: * full hosting (MX1) on our servers: ** multiple email addresses which can be real mailboxes or mere redirections at another third party addresses ** based on ''milkypond.org'' (or maybe ''duckcorp.org'') domain(s) or you own domain(s) * fallback retention (MX2) on our servers or, at your choice, partner servers (currently via Hivane) == Full Hosting == === Access Methods === You can retrieve your mails, in case of a real mailbox, using: * IMAP+TLS (TCP 143) / IMAPS (TCP 993) on imap.duckcorp.org * or POP3+TLS (TCP 110) / POP3S (TCP 995) on pop.duckcorp.org * or one of the [https://webmail.duckcorp.org/ provided webmails] The IMAP protocol is recommended over POP3, as it provides many interresting features. If you want to download all your mails absolutely at home, loosing the ability to read your mail from anywhere on the planet, you can do that with IMAP too (look at your mail client settings). You can use our servers to send mails out too via smtp.duckcorp.org using: * SMTP+TLS (TCP 25) / SMTPS (TCP 465) * and SASL authentication === Mail Filtering === With your favourite mail client, you can probably filter your mails in proper folders already. Nevertheless, this can be a annoying operation: * blocking you mail client for a long time if you have to process plenty of mails * downloading each mail information, and sometimes content (depending on your filters), is lenghty too, and cost much bandwidth * syncing filters accross your machines (home desktop, laptop, office machine…) is a pain in the ass * processing only when you're online prevents triggering actions in a timely manner (automatic redirect, vacation messages…), and running a machine 24/7 with a mail client polling new mails every 30s is not a solution We provide a much better way to do this using the [[wikipedia:Sieve_(mail_filtering_language)|SIEVE]] filters. Shortly, SIEVE is a language dedicated to expressing mail filters. Our server is able to process your mails according to these filters as soon as they arrive. You then don't have to care about them anymore, and may use light mail clients or webmails when you're not on your machine with your favourite software. To push your filters on the server, a dedicated protocol exists: MANAGESIEVE (TCP 4190) on sieve.duckcorp.org Several softwares support managing SIEVE rules: * Icedove/Thunderbird using the SIEVE extension (in xul-ext-sieve Debian package) provides a rules editor * Horde (Ingo) provides an easy to use web interface * Squirrelmail with the Avelsieve extension provides an easy to use web interface * Roundcube with an extension provides an easy to use web interface * sieve-connect provides a CLI to upload/download/activate your rules files (tell us if you know more software supporting this feature) You can read more info about SIEVE here: * http://www.fastmail.fm/docs/sieve/ * http://sieve.info/ === Shared/Public Folders === You may need to share mails or messages with friends or people your do stuff with. Depending on your needs, two solutions are possible: * share some of your own folders, thus called ''shared folders'' * manage a special folder hierarchy, called ''public folders'' (even if they may not be accessible to everyone) Through IMAP, or our webmails internally using IMAP, it is possible to partition the folder hierarchy into ''namespaces''. Traditionally you are using the root namespace for your private folders. Additionnal namespaces can be created and will appear among your own folders or separate, depending on your mail client's choice of representation. == Retention fallback == The current retention period on our servers is 2 weeks, but can be temporary or permanently increased if needed. 29700128f6868dba0576f0d54957ef6c100f8e42 197 196 2011-05-14T21:54:27Z Duck 2 /* Shared/Public Folders */ wikitext text/x-wiki == Mail Hosting == What we can offer: * full hosting (MX1) on our servers: ** multiple email addresses which can be real mailboxes or mere redirections at another third party addresses ** based on ''milkypond.org'' (or maybe ''duckcorp.org'') domain(s) or you own domain(s) * fallback retention (MX2) on our servers or, at your choice, partner servers (currently via Hivane) == Full Hosting == === Access Methods === You can retrieve your mails, in case of a real mailbox, using: * IMAP+TLS (TCP 143) / IMAPS (TCP 993) on imap.duckcorp.org * or POP3+TLS (TCP 110) / POP3S (TCP 995) on pop.duckcorp.org * or one of the [https://webmail.duckcorp.org/ provided webmails] The IMAP protocol is recommended over POP3, as it provides many interresting features. If you want to download all your mails absolutely at home, loosing the ability to read your mail from anywhere on the planet, you can do that with IMAP too (look at your mail client settings). You can use our servers to send mails out too via smtp.duckcorp.org using: * SMTP+TLS (TCP 25) / SMTPS (TCP 465) * and SASL authentication === Mail Filtering === With your favourite mail client, you can probably filter your mails in proper folders already. Nevertheless, this can be a annoying operation: * blocking you mail client for a long time if you have to process plenty of mails * downloading each mail information, and sometimes content (depending on your filters), is lenghty too, and cost much bandwidth * syncing filters accross your machines (home desktop, laptop, office machine…) is a pain in the ass * processing only when you're online prevents triggering actions in a timely manner (automatic redirect, vacation messages…), and running a machine 24/7 with a mail client polling new mails every 30s is not a solution We provide a much better way to do this using the [[wikipedia:Sieve_(mail_filtering_language)|SIEVE]] filters. Shortly, SIEVE is a language dedicated to expressing mail filters. Our server is able to process your mails according to these filters as soon as they arrive. You then don't have to care about them anymore, and may use light mail clients or webmails when you're not on your machine with your favourite software. To push your filters on the server, a dedicated protocol exists: MANAGESIEVE (TCP 4190) on sieve.duckcorp.org Several softwares support managing SIEVE rules: * Icedove/Thunderbird using the SIEVE extension (in xul-ext-sieve Debian package) provides a rules editor * Horde (Ingo) provides an easy to use web interface * Squirrelmail with the Avelsieve extension provides an easy to use web interface * Roundcube with an extension provides an easy to use web interface * sieve-connect provides a CLI to upload/download/activate your rules files (tell us if you know more software supporting this feature) You can read more info about SIEVE here: * http://www.fastmail.fm/docs/sieve/ * http://sieve.info/ === Shared/Public Folders === You may need to share mails or messages with friends or people your do stuff with. Depending on your needs, two solutions are possible: * share some of your own folders, thus called ''shared folders'' * manage a special folder hierarchy, called ''public folders'' (even if they may not be accessible to everyone) Through IMAP, or our webmails internally using IMAP, it is possible to partition the folder hierarchy into ''namespaces''. Traditionally you are using the root namespace for your private folders. Additionnal namespaces can be created and will appear among your own folders or separate, depending on your mail client's choice of representation. To avoid name clashes, we decided to prefix all additionnal namespace names with a '''#'''. Since 2011-05-14, the following extra namespaces are created and reserved: * #Shared, containing all folders other users decided to share with you * #MilkyPond, containing public MP/DC information mailboxes you may subscribe at will Using IMAP, it is possible to setup rights (read only, write allowed…) to your own folders in order to share them with other users, or group of users. Public folder are owned by noone, and must be created by DC administrators ; if you need one, send us a request and we may be able to create it and delegate administration to your care (namespace name is subject to approval). == Retention fallback == The current retention period on our servers is 2 weeks, but can be temporary or permanently increased if needed. 3f86dda65b6a749ea47b489a7fa9e024d5e212f3 198 197 2011-05-14T21:57:30Z Duck 2 /* Shared/Public Folders */ wikitext text/x-wiki == Mail Hosting == What we can offer: * full hosting (MX1) on our servers: ** multiple email addresses which can be real mailboxes or mere redirections at another third party addresses ** based on ''milkypond.org'' (or maybe ''duckcorp.org'') domain(s) or you own domain(s) * fallback retention (MX2) on our servers or, at your choice, partner servers (currently via Hivane) == Full Hosting == === Access Methods === You can retrieve your mails, in case of a real mailbox, using: * IMAP+TLS (TCP 143) / IMAPS (TCP 993) on imap.duckcorp.org * or POP3+TLS (TCP 110) / POP3S (TCP 995) on pop.duckcorp.org * or one of the [https://webmail.duckcorp.org/ provided webmails] The IMAP protocol is recommended over POP3, as it provides many interresting features. If you want to download all your mails absolutely at home, loosing the ability to read your mail from anywhere on the planet, you can do that with IMAP too (look at your mail client settings). You can use our servers to send mails out too via smtp.duckcorp.org using: * SMTP+TLS (TCP 25) / SMTPS (TCP 465) * and SASL authentication === Mail Filtering === With your favourite mail client, you can probably filter your mails in proper folders already. Nevertheless, this can be a annoying operation: * blocking you mail client for a long time if you have to process plenty of mails * downloading each mail information, and sometimes content (depending on your filters), is lenghty too, and cost much bandwidth * syncing filters accross your machines (home desktop, laptop, office machine…) is a pain in the ass * processing only when you're online prevents triggering actions in a timely manner (automatic redirect, vacation messages…), and running a machine 24/7 with a mail client polling new mails every 30s is not a solution We provide a much better way to do this using the [[wikipedia:Sieve_(mail_filtering_language)|SIEVE]] filters. Shortly, SIEVE is a language dedicated to expressing mail filters. Our server is able to process your mails according to these filters as soon as they arrive. You then don't have to care about them anymore, and may use light mail clients or webmails when you're not on your machine with your favourite software. To push your filters on the server, a dedicated protocol exists: MANAGESIEVE (TCP 4190) on sieve.duckcorp.org Several softwares support managing SIEVE rules: * Icedove/Thunderbird using the SIEVE extension (in xul-ext-sieve Debian package) provides a rules editor * Horde (Ingo) provides an easy to use web interface * Squirrelmail with the Avelsieve extension provides an easy to use web interface * Roundcube with an extension provides an easy to use web interface * sieve-connect provides a CLI to upload/download/activate your rules files (tell us if you know more software supporting this feature) You can read more info about SIEVE here: * http://www.fastmail.fm/docs/sieve/ * http://sieve.info/ === Shared/Public Folders === You may need to share mails or messages with friends or people your do stuff with. Depending on your needs, two solutions are possible: * share some of your own folders, thus called ''shared folders'' * manage a special folder hierarchy, called ''public folders'' (even if they may not be accessible to everyone) Through IMAP, or our webmails internally using IMAP, it is possible to partition the folder hierarchy into ''namespaces''. Traditionally you are using the root namespace for your private folders. Additionnal namespaces can be created and will appear among your own folders or separate, depending on your mail client's choice of representation. To avoid name clashes, we decided to prefix all additionnal namespace names with a '''#'''. Since 2011-05-14, the following extra namespaces are created and reserved: * #Shared, containing all folders other users decided to share with you * #MilkyPond, containing public MP/DC information mailboxes you may subscribe at will Using IMAP, it is possible to setup rights (read only, write allowed…) to your own folders in order to share them with other users, or group of users. Public folder are owned by noone, and must be created by DC administrators ; if you need one, send us a request and we may be able to create it and delegate administration to your care (namespace name is subject to approval). Once created, public folder can be administered like shared folders. == Retention fallback == The current retention period on our servers is 2 weeks, but can be temporary or permanently increased if needed. a477b860503ba4b4b8e12c1d1c32f55eaf2eb902 199 198 2011-05-17T17:06:32Z Duck 2 /* Mail Filtering */ wikitext text/x-wiki == Mail Hosting == What we can offer: * full hosting (MX1) on our servers: ** multiple email addresses which can be real mailboxes or mere redirections at another third party addresses ** based on ''milkypond.org'' (or maybe ''duckcorp.org'') domain(s) or you own domain(s) * fallback retention (MX2) on our servers or, at your choice, partner servers (currently via Hivane) == Full Hosting == === Access Methods === You can retrieve your mails, in case of a real mailbox, using: * IMAP+TLS (TCP 143) / IMAPS (TCP 993) on imap.duckcorp.org * or POP3+TLS (TCP 110) / POP3S (TCP 995) on pop.duckcorp.org * or one of the [https://webmail.duckcorp.org/ provided webmails] The IMAP protocol is recommended over POP3, as it provides many interresting features. If you want to download all your mails absolutely at home, loosing the ability to read your mail from anywhere on the planet, you can do that with IMAP too (look at your mail client settings). You can use our servers to send mails out too via smtp.duckcorp.org using: * SMTP+TLS (TCP 25) / SMTPS (TCP 465) * and SASL authentication === Mail Filtering === With your favourite mail client, you can probably filter your mails in proper folders already. Nevertheless, this can be a annoying operation: * blocking you mail client for a long time if you have to process plenty of mails * downloading each mail information, and sometimes content (depending on your filters), is lenghty too, and cost much bandwidth * syncing filters accross your machines (home desktop, laptop, office machine…) is a pain in the ass * processing only when you're online prevents triggering actions in a timely manner (automatic redirect, vacation messages…), and running a machine 24/7 with a mail client polling new mails every 30s is not a solution We provide a much better way to do this using the [[wikipedia:Sieve_(mail_filtering_language)|SIEVE]] filters. Shortly, SIEVE is a language dedicated to expressing mail filters. Our server is able to process your mails according to these filters as soon as they arrive. You then don't have to care about them anymore, and may use light mail clients or webmails when you're not on your machine with your favourite software. To push your filters on the server, a dedicated protocol exists: MANAGESIEVE (TCP 4190) on sieve.duckcorp.org Several softwares support managing SIEVE rules: * Icedove/Thunderbird using the SIEVE extension (in xul-ext-sieve Debian package) provides a rules editor * Horde (Ingo) provides an easy to use web interface * Squirrelmail with the Avelsieve extension provides an easy to use web interface * Roundcube with an extension provides an easy to use web interface * sieve-connect provides a CLI to upload/download/activate your rules files (tell us if you know more software supporting this feature) You can read more info about SIEVE here: * supported SIEVE features on our server: http://pigeonhole.dovecot.org/ * http://www.fastmail.fm/docs/sieve/ * http://sieve.info/ === Shared/Public Folders === You may need to share mails or messages with friends or people your do stuff with. Depending on your needs, two solutions are possible: * share some of your own folders, thus called ''shared folders'' * manage a special folder hierarchy, called ''public folders'' (even if they may not be accessible to everyone) Through IMAP, or our webmails internally using IMAP, it is possible to partition the folder hierarchy into ''namespaces''. Traditionally you are using the root namespace for your private folders. Additionnal namespaces can be created and will appear among your own folders or separate, depending on your mail client's choice of representation. To avoid name clashes, we decided to prefix all additionnal namespace names with a '''#'''. Since 2011-05-14, the following extra namespaces are created and reserved: * #Shared, containing all folders other users decided to share with you * #MilkyPond, containing public MP/DC information mailboxes you may subscribe at will Using IMAP, it is possible to setup rights (read only, write allowed…) to your own folders in order to share them with other users, or group of users. Public folder are owned by noone, and must be created by DC administrators ; if you need one, send us a request and we may be able to create it and delegate administration to your care (namespace name is subject to approval). Once created, public folder can be administered like shared folders. == Retention fallback == The current retention period on our servers is 2 weeks, but can be temporary or permanently increased if needed. 9452503965358552e02d5783e2d7043ea90d828d 200 199 2011-05-17T17:26:00Z Duck 2 /* Shared/Public Folders */ wikitext text/x-wiki == Mail Hosting == What we can offer: * full hosting (MX1) on our servers: ** multiple email addresses which can be real mailboxes or mere redirections at another third party addresses ** based on ''milkypond.org'' (or maybe ''duckcorp.org'') domain(s) or you own domain(s) * fallback retention (MX2) on our servers or, at your choice, partner servers (currently via Hivane) == Full Hosting == === Access Methods === You can retrieve your mails, in case of a real mailbox, using: * IMAP+TLS (TCP 143) / IMAPS (TCP 993) on imap.duckcorp.org * or POP3+TLS (TCP 110) / POP3S (TCP 995) on pop.duckcorp.org * or one of the [https://webmail.duckcorp.org/ provided webmails] The IMAP protocol is recommended over POP3, as it provides many interresting features. If you want to download all your mails absolutely at home, loosing the ability to read your mail from anywhere on the planet, you can do that with IMAP too (look at your mail client settings). You can use our servers to send mails out too via smtp.duckcorp.org using: * SMTP+TLS (TCP 25) / SMTPS (TCP 465) * and SASL authentication === Mail Filtering === With your favourite mail client, you can probably filter your mails in proper folders already. Nevertheless, this can be a annoying operation: * blocking you mail client for a long time if you have to process plenty of mails * downloading each mail information, and sometimes content (depending on your filters), is lenghty too, and cost much bandwidth * syncing filters accross your machines (home desktop, laptop, office machine…) is a pain in the ass * processing only when you're online prevents triggering actions in a timely manner (automatic redirect, vacation messages…), and running a machine 24/7 with a mail client polling new mails every 30s is not a solution We provide a much better way to do this using the [[wikipedia:Sieve_(mail_filtering_language)|SIEVE]] filters. Shortly, SIEVE is a language dedicated to expressing mail filters. Our server is able to process your mails according to these filters as soon as they arrive. You then don't have to care about them anymore, and may use light mail clients or webmails when you're not on your machine with your favourite software. To push your filters on the server, a dedicated protocol exists: MANAGESIEVE (TCP 4190) on sieve.duckcorp.org Several softwares support managing SIEVE rules: * Icedove/Thunderbird using the SIEVE extension (in xul-ext-sieve Debian package) provides a rules editor * Horde (Ingo) provides an easy to use web interface * Squirrelmail with the Avelsieve extension provides an easy to use web interface * Roundcube with an extension provides an easy to use web interface * sieve-connect provides a CLI to upload/download/activate your rules files (tell us if you know more software supporting this feature) You can read more info about SIEVE here: * supported SIEVE features on our server: http://pigeonhole.dovecot.org/ * http://www.fastmail.fm/docs/sieve/ * http://sieve.info/ === Shared/Public Folders === You may need to share mails or messages with friends or people your do stuff with. Depending on your needs, two solutions are possible: * share some of your own folders, thus called ''shared folders'' * manage a special folder hierarchy, called ''public folders'' (even if they may not be accessible to everyone) Through IMAP, or our webmails internally using IMAP, it is possible to partition the folder hierarchy into ''namespaces''. Traditionally you are using the root namespace for your private folders. Additionnal namespaces can be created and will appear among your own folders or separate, depending on your mail client's choice of representation. To avoid name clashes, we decided to prefix all additionnal namespace names with a '''#'''. Since 2011-05-14, the following extra namespaces are created and reserved: * #Shared, containing all folders other users decided to share with you * #MilkyPond, containing public MP/DC information mailboxes you may subscribe at will Using IMAP, it is possible to setup rights (read only, write allowed…) to your own folders in order to share them with other users, or group of users. Public folders are owned by noone, and must be created by DC administrators ; if you need one, send us a request and we may be able to create it and delegate administration to your care (namespace name is subject to approval). Once created, public folders can be administered like shared folders. Client mail softwares support: * Horde: support namespaces, shared folders configurable via 'Options'->'Share Folders' menu but no ACLs for public folders * Icedove/Thunderbird: support namespaces, shared and public folders configurable via folder selection and 'Tools' => 'Imap-ACL' menu action Most other softwares have namespace support only, so you should be able to use shared/public folders you have rights on but not configure them yourself == Retention fallback == The current retention period on our servers is 2 weeks, but can be temporary or permanently increased if needed. f8163367b7d3bb668635bc27b53682964e4c7ae2 201 200 2011-05-17T17:28:02Z Duck 2 /* Mail Filtering */ wikitext text/x-wiki == Mail Hosting == What we can offer: * full hosting (MX1) on our servers: ** multiple email addresses which can be real mailboxes or mere redirections at another third party addresses ** based on ''milkypond.org'' (or maybe ''duckcorp.org'') domain(s) or you own domain(s) * fallback retention (MX2) on our servers or, at your choice, partner servers (currently via Hivane) == Full Hosting == === Access Methods === You can retrieve your mails, in case of a real mailbox, using: * IMAP+TLS (TCP 143) / IMAPS (TCP 993) on imap.duckcorp.org * or POP3+TLS (TCP 110) / POP3S (TCP 995) on pop.duckcorp.org * or one of the [https://webmail.duckcorp.org/ provided webmails] The IMAP protocol is recommended over POP3, as it provides many interresting features. If you want to download all your mails absolutely at home, loosing the ability to read your mail from anywhere on the planet, you can do that with IMAP too (look at your mail client settings). You can use our servers to send mails out too via smtp.duckcorp.org using: * SMTP+TLS (TCP 25) / SMTPS (TCP 465) * and SASL authentication === Mail Filtering === With your favourite mail client, you can probably filter your mails in proper folders already. Nevertheless, this can be a annoying operation: * blocking you mail client for a long time if you have to process plenty of mails * downloading each mail information, and sometimes content (depending on your filters), is lenghty too, and cost much bandwidth * syncing filters accross your machines (home desktop, laptop, office machine…) is a pain in the ass * processing only when you're online prevents triggering actions in a timely manner (automatic redirect, vacation messages…), and running a machine 24/7 with a mail client polling new mails every 30s is not a solution We provide a much better way to do this using the [[wikipedia:Sieve_(mail_filtering_language)|SIEVE]] filters. Shortly, SIEVE is a language dedicated to expressing mail filters. Our server is able to process your mails according to these filters as soon as they arrive. You then don't have to care about them anymore, and may use light mail clients or webmails when you're not on your machine with your favourite software. To push your filters on the server, a dedicated protocol exists: : MANAGESIEVE (TCP 4190) on sieve.duckcorp.org Several softwares support managing SIEVE rules: * Icedove/Thunderbird using the SIEVE extension (in xul-ext-sieve Debian package) provides a rules editor * Horde (Ingo) provides an easy to use web interface * Squirrelmail with the Avelsieve extension provides an easy to use web interface * Roundcube with an extension provides an easy to use web interface * sieve-connect provides a CLI to upload/download/activate your rules files (tell us if you know more software supporting this feature) You can read more info about SIEVE here: * supported SIEVE features on our server: http://pigeonhole.dovecot.org/ * http://www.fastmail.fm/docs/sieve/ * http://sieve.info/ === Shared/Public Folders === You may need to share mails or messages with friends or people your do stuff with. Depending on your needs, two solutions are possible: * share some of your own folders, thus called ''shared folders'' * manage a special folder hierarchy, called ''public folders'' (even if they may not be accessible to everyone) Through IMAP, or our webmails internally using IMAP, it is possible to partition the folder hierarchy into ''namespaces''. Traditionally you are using the root namespace for your private folders. Additionnal namespaces can be created and will appear among your own folders or separate, depending on your mail client's choice of representation. To avoid name clashes, we decided to prefix all additionnal namespace names with a '''#'''. Since 2011-05-14, the following extra namespaces are created and reserved: * #Shared, containing all folders other users decided to share with you * #MilkyPond, containing public MP/DC information mailboxes you may subscribe at will Using IMAP, it is possible to setup rights (read only, write allowed…) to your own folders in order to share them with other users, or group of users. Public folders are owned by noone, and must be created by DC administrators ; if you need one, send us a request and we may be able to create it and delegate administration to your care (namespace name is subject to approval). Once created, public folders can be administered like shared folders. Client mail softwares support: * Horde: support namespaces, shared folders configurable via 'Options'->'Share Folders' menu but no ACLs for public folders * Icedove/Thunderbird: support namespaces, shared and public folders configurable via folder selection and 'Tools' => 'Imap-ACL' menu action Most other softwares have namespace support only, so you should be able to use shared/public folders you have rights on but not configure them yourself == Retention fallback == The current retention period on our servers is 2 weeks, but can be temporary or permanently increased if needed. 05f110621f961fbaa4bc3c42a51e64c305f03672 202 201 2011-05-17T17:28:12Z Duck 2 /* Shared/Public Folders */ wikitext text/x-wiki == Mail Hosting == What we can offer: * full hosting (MX1) on our servers: ** multiple email addresses which can be real mailboxes or mere redirections at another third party addresses ** based on ''milkypond.org'' (or maybe ''duckcorp.org'') domain(s) or you own domain(s) * fallback retention (MX2) on our servers or, at your choice, partner servers (currently via Hivane) == Full Hosting == === Access Methods === You can retrieve your mails, in case of a real mailbox, using: * IMAP+TLS (TCP 143) / IMAPS (TCP 993) on imap.duckcorp.org * or POP3+TLS (TCP 110) / POP3S (TCP 995) on pop.duckcorp.org * or one of the [https://webmail.duckcorp.org/ provided webmails] The IMAP protocol is recommended over POP3, as it provides many interresting features. If you want to download all your mails absolutely at home, loosing the ability to read your mail from anywhere on the planet, you can do that with IMAP too (look at your mail client settings). You can use our servers to send mails out too via smtp.duckcorp.org using: * SMTP+TLS (TCP 25) / SMTPS (TCP 465) * and SASL authentication === Mail Filtering === With your favourite mail client, you can probably filter your mails in proper folders already. Nevertheless, this can be a annoying operation: * blocking you mail client for a long time if you have to process plenty of mails * downloading each mail information, and sometimes content (depending on your filters), is lenghty too, and cost much bandwidth * syncing filters accross your machines (home desktop, laptop, office machine…) is a pain in the ass * processing only when you're online prevents triggering actions in a timely manner (automatic redirect, vacation messages…), and running a machine 24/7 with a mail client polling new mails every 30s is not a solution We provide a much better way to do this using the [[wikipedia:Sieve_(mail_filtering_language)|SIEVE]] filters. Shortly, SIEVE is a language dedicated to expressing mail filters. Our server is able to process your mails according to these filters as soon as they arrive. You then don't have to care about them anymore, and may use light mail clients or webmails when you're not on your machine with your favourite software. To push your filters on the server, a dedicated protocol exists: : MANAGESIEVE (TCP 4190) on sieve.duckcorp.org Several softwares support managing SIEVE rules: * Icedove/Thunderbird using the SIEVE extension (in xul-ext-sieve Debian package) provides a rules editor * Horde (Ingo) provides an easy to use web interface * Squirrelmail with the Avelsieve extension provides an easy to use web interface * Roundcube with an extension provides an easy to use web interface * sieve-connect provides a CLI to upload/download/activate your rules files (tell us if you know more software supporting this feature) You can read more info about SIEVE here: * supported SIEVE features on our server: http://pigeonhole.dovecot.org/ * http://www.fastmail.fm/docs/sieve/ * http://sieve.info/ === Shared/Public Folders === You may need to share mails or messages with friends or people your do stuff with. Depending on your needs, two solutions are possible: * share some of your own folders, thus called ''shared folders'' * manage a special folder hierarchy, called ''public folders'' (even if they may not be accessible to everyone) Through IMAP, or our webmails internally using IMAP, it is possible to partition the folder hierarchy into ''namespaces''. Traditionally you are using the root namespace for your private folders. Additionnal namespaces can be created and will appear among your own folders or separate, depending on your mail client's choice of representation. To avoid name clashes, we decided to prefix all additionnal namespace names with a '''#'''. Since 2011-05-14, the following extra namespaces are created and reserved: * #Shared, containing all folders other users decided to share with you * #MilkyPond, containing public MP/DC information mailboxes you may subscribe at will Using IMAP, it is possible to setup rights (read only, write allowed…) to your own folders in order to share them with other users, or group of users. Public folders are owned by noone, and must be created by DC administrators ; if you need one, send us a request and we may be able to create it and delegate administration to your care (namespace name is subject to approval). Once created, public folders can be administered like shared folders. Client mail softwares support: * Horde: support namespaces, shared folders configurable via 'Options'->'Share Folders' menu but no ACLs for public folders * Icedove/Thunderbird: support namespaces, shared and public folders configurable via folder selection and 'Tools' => 'Imap-ACL' menu action Most other softwares have namespace support only, so you should be able to use shared/public folders you have rights on but not configure them yourself (tell us if you know more software supporting this feature) == Retention fallback == The current retention period on our servers is 2 weeks, but can be temporary or permanently increased if needed. ea49ac807a41fb7a647aafbc1af5433b423d0f0b 0 49 203 202 2011-05-17T17:29:48Z Duck 2 /* Shared/Public Folders */ wikitext text/x-wiki == Mail Hosting == What we can offer: * full hosting (MX1) on our servers: ** multiple email addresses which can be real mailboxes or mere redirections at another third party addresses ** based on ''milkypond.org'' (or maybe ''duckcorp.org'') domain(s) or you own domain(s) * fallback retention (MX2) on our servers or, at your choice, partner servers (currently via Hivane) == Full Hosting == === Access Methods === You can retrieve your mails, in case of a real mailbox, using: * IMAP+TLS (TCP 143) / IMAPS (TCP 993) on imap.duckcorp.org * or POP3+TLS (TCP 110) / POP3S (TCP 995) on pop.duckcorp.org * or one of the [https://webmail.duckcorp.org/ provided webmails] The IMAP protocol is recommended over POP3, as it provides many interresting features. If you want to download all your mails absolutely at home, loosing the ability to read your mail from anywhere on the planet, you can do that with IMAP too (look at your mail client settings). You can use our servers to send mails out too via smtp.duckcorp.org using: * SMTP+TLS (TCP 25) / SMTPS (TCP 465) * and SASL authentication === Mail Filtering === With your favourite mail client, you can probably filter your mails in proper folders already. Nevertheless, this can be a annoying operation: * blocking you mail client for a long time if you have to process plenty of mails * downloading each mail information, and sometimes content (depending on your filters), is lenghty too, and cost much bandwidth * syncing filters accross your machines (home desktop, laptop, office machine…) is a pain in the ass * processing only when you're online prevents triggering actions in a timely manner (automatic redirect, vacation messages…), and running a machine 24/7 with a mail client polling new mails every 30s is not a solution We provide a much better way to do this using the [[wikipedia:Sieve_(mail_filtering_language)|SIEVE]] filters. Shortly, SIEVE is a language dedicated to expressing mail filters. Our server is able to process your mails according to these filters as soon as they arrive. You then don't have to care about them anymore, and may use light mail clients or webmails when you're not on your machine with your favourite software. To push your filters on the server, a dedicated protocol exists: : MANAGESIEVE (TCP 4190) on sieve.duckcorp.org Several softwares support managing SIEVE rules: * Icedove/Thunderbird using the SIEVE extension (in xul-ext-sieve Debian package) provides a rules editor * Horde (Ingo) provides an easy to use web interface * Squirrelmail with the Avelsieve extension provides an easy to use web interface * Roundcube with an extension provides an easy to use web interface * sieve-connect provides a CLI to upload/download/activate your rules files (tell us if you know more software supporting this feature) You can read more info about SIEVE here: * supported SIEVE features on our server: http://pigeonhole.dovecot.org/ * http://www.fastmail.fm/docs/sieve/ * http://sieve.info/ === Shared/Public Folders === You may need to share mails or messages with friends or people you do stuff with (in a project or association). Depending on your needs, two solutions are possible: * share some of your own folders, thus called ''shared folders'' * manage a special folder hierarchy, called ''public folders'' (even if they may not be accessible to everyone) Through IMAP, or our webmails internally using IMAP, it is possible to partition the folder hierarchy into ''namespaces''. Traditionally you are using the root namespace for your private folders. Additionnal namespaces can be created and will appear among your own folders or separate, depending on your mail client's choice of representation. To avoid name clashes, we decided to prefix all additionnal namespace names with a '''#'''. Since 2011-05-14, the following extra namespaces are created and reserved: * #Shared, containing all folders other users decided to share with you * #MilkyPond, containing public MP/DC information mailboxes you may subscribe at will Using IMAP, it is possible to setup rights (read only, write allowed…) to your own folders in order to share them with other users, or group of users. Public folders are owned by noone, and must be created by DC administrators ; if you need one, send us a request and we may be able to create it and delegate administration to your care (namespace name is subject to approval). Once created, public folders can be administered like shared folders. Client mail softwares support: * Horde: support namespaces, shared folders configurable via 'Options'->'Share Folders' menu but no ACLs for public folders * Icedove/Thunderbird: support namespaces, shared and public folders configurable via folder selection and 'Tools' => 'Imap-ACL' menu action Most other softwares have namespace support only, so you should be able to use shared/public folders you have rights on but not configure them yourself (tell us if you know more software supporting this feature) == Retention fallback == The current retention period on our servers is 2 weeks, but can be temporary or permanently increased if needed. 3f09a095c160a794f432d8dc4bc140088bd38394 204 203 2011-05-17T17:30:09Z Duck 2 /* Shared/Public Folders */ wikitext text/x-wiki == Mail Hosting == What we can offer: * full hosting (MX1) on our servers: ** multiple email addresses which can be real mailboxes or mere redirections at another third party addresses ** based on ''milkypond.org'' (or maybe ''duckcorp.org'') domain(s) or you own domain(s) * fallback retention (MX2) on our servers or, at your choice, partner servers (currently via Hivane) == Full Hosting == === Access Methods === You can retrieve your mails, in case of a real mailbox, using: * IMAP+TLS (TCP 143) / IMAPS (TCP 993) on imap.duckcorp.org * or POP3+TLS (TCP 110) / POP3S (TCP 995) on pop.duckcorp.org * or one of the [https://webmail.duckcorp.org/ provided webmails] The IMAP protocol is recommended over POP3, as it provides many interresting features. If you want to download all your mails absolutely at home, loosing the ability to read your mail from anywhere on the planet, you can do that with IMAP too (look at your mail client settings). You can use our servers to send mails out too via smtp.duckcorp.org using: * SMTP+TLS (TCP 25) / SMTPS (TCP 465) * and SASL authentication === Mail Filtering === With your favourite mail client, you can probably filter your mails in proper folders already. Nevertheless, this can be a annoying operation: * blocking you mail client for a long time if you have to process plenty of mails * downloading each mail information, and sometimes content (depending on your filters), is lenghty too, and cost much bandwidth * syncing filters accross your machines (home desktop, laptop, office machine…) is a pain in the ass * processing only when you're online prevents triggering actions in a timely manner (automatic redirect, vacation messages…), and running a machine 24/7 with a mail client polling new mails every 30s is not a solution We provide a much better way to do this using the [[wikipedia:Sieve_(mail_filtering_language)|SIEVE]] filters. Shortly, SIEVE is a language dedicated to expressing mail filters. Our server is able to process your mails according to these filters as soon as they arrive. You then don't have to care about them anymore, and may use light mail clients or webmails when you're not on your machine with your favourite software. To push your filters on the server, a dedicated protocol exists: : MANAGESIEVE (TCP 4190) on sieve.duckcorp.org Several softwares support managing SIEVE rules: * Icedove/Thunderbird using the SIEVE extension (in xul-ext-sieve Debian package) provides a rules editor * Horde (Ingo) provides an easy to use web interface * Squirrelmail with the Avelsieve extension provides an easy to use web interface * Roundcube with an extension provides an easy to use web interface * sieve-connect provides a CLI to upload/download/activate your rules files (tell us if you know more software supporting this feature) You can read more info about SIEVE here: * supported SIEVE features on our server: http://pigeonhole.dovecot.org/ * http://www.fastmail.fm/docs/sieve/ * http://sieve.info/ === Shared/Public Folders === You may need to share mails or messages with friends or people you do stuff with (in a project or association). Depending on your needs, two solutions are possible: * share some of your own private folders, thus called ''shared folders'' * manage a special folder hierarchy, called ''public folders'' (even if they may not be accessible to everyone) Through IMAP, or our webmails internally using IMAP, it is possible to partition the folder hierarchy into ''namespaces''. Traditionally you are using the root namespace for your private folders. Additionnal namespaces can be created and will appear among your own folders or separate, depending on your mail client's choice of representation. To avoid name clashes, we decided to prefix all additionnal namespace names with a '''#'''. Since 2011-05-14, the following extra namespaces are created and reserved: * #Shared, containing all folders other users decided to share with you * #MilkyPond, containing public MP/DC information mailboxes you may subscribe at will Using IMAP, it is possible to setup rights (read only, write allowed…) to your own folders in order to share them with other users, or group of users. Public folders are owned by noone, and must be created by DC administrators ; if you need one, send us a request and we may be able to create it and delegate administration to your care (namespace name is subject to approval). Once created, public folders can be administered like shared folders. Client mail softwares support: * Horde: support namespaces, shared folders configurable via 'Options'->'Share Folders' menu but no ACLs for public folders * Icedove/Thunderbird: support namespaces, shared and public folders configurable via folder selection and 'Tools' => 'Imap-ACL' menu action Most other softwares have namespace support only, so you should be able to use shared/public folders you have rights on but not configure them yourself (tell us if you know more software supporting this feature) == Retention fallback == The current retention period on our servers is 2 weeks, but can be temporary or permanently increased if needed. 1fe321655a5ed92becfe13a57d8ca9a26b1222b8 205 204 2011-05-17T17:31:56Z Duck 2 /* Shared/Public Folders */ wikitext text/x-wiki == Mail Hosting == What we can offer: * full hosting (MX1) on our servers: ** multiple email addresses which can be real mailboxes or mere redirections at another third party addresses ** based on ''milkypond.org'' (or maybe ''duckcorp.org'') domain(s) or you own domain(s) * fallback retention (MX2) on our servers or, at your choice, partner servers (currently via Hivane) == Full Hosting == === Access Methods === You can retrieve your mails, in case of a real mailbox, using: * IMAP+TLS (TCP 143) / IMAPS (TCP 993) on imap.duckcorp.org * or POP3+TLS (TCP 110) / POP3S (TCP 995) on pop.duckcorp.org * or one of the [https://webmail.duckcorp.org/ provided webmails] The IMAP protocol is recommended over POP3, as it provides many interresting features. If you want to download all your mails absolutely at home, loosing the ability to read your mail from anywhere on the planet, you can do that with IMAP too (look at your mail client settings). You can use our servers to send mails out too via smtp.duckcorp.org using: * SMTP+TLS (TCP 25) / SMTPS (TCP 465) * and SASL authentication === Mail Filtering === With your favourite mail client, you can probably filter your mails in proper folders already. Nevertheless, this can be a annoying operation: * blocking you mail client for a long time if you have to process plenty of mails * downloading each mail information, and sometimes content (depending on your filters), is lenghty too, and cost much bandwidth * syncing filters accross your machines (home desktop, laptop, office machine…) is a pain in the ass * processing only when you're online prevents triggering actions in a timely manner (automatic redirect, vacation messages…), and running a machine 24/7 with a mail client polling new mails every 30s is not a solution We provide a much better way to do this using the [[wikipedia:Sieve_(mail_filtering_language)|SIEVE]] filters. Shortly, SIEVE is a language dedicated to expressing mail filters. Our server is able to process your mails according to these filters as soon as they arrive. You then don't have to care about them anymore, and may use light mail clients or webmails when you're not on your machine with your favourite software. To push your filters on the server, a dedicated protocol exists: : MANAGESIEVE (TCP 4190) on sieve.duckcorp.org Several softwares support managing SIEVE rules: * Icedove/Thunderbird using the SIEVE extension (in xul-ext-sieve Debian package) provides a rules editor * Horde (Ingo) provides an easy to use web interface * Squirrelmail with the Avelsieve extension provides an easy to use web interface * Roundcube with an extension provides an easy to use web interface * sieve-connect provides a CLI to upload/download/activate your rules files (tell us if you know more software supporting this feature) You can read more info about SIEVE here: * supported SIEVE features on our server: http://pigeonhole.dovecot.org/ * http://www.fastmail.fm/docs/sieve/ * http://sieve.info/ === Shared/Public Folders === You may need to share mails or messages with friends or people you do stuff with (in a project or association). Depending on your needs, two solutions are possible: * share some of your own private folders, thus called ''shared folders'' * manage a special folder hierarchy, called ''public folders'' (even if they may not be accessible to everyone) Through IMAP, or our webmails internally using IMAP, it is possible to partition the folder hierarchy into ''namespaces''. Traditionally you are using the root namespace for your private folders. Additionnal namespaces can be created and will appear among your own folders or separate, depending on your mail client's choice of representation. To avoid name clashes, we decided to prefix all additionnal namespace names with a '''#'''. Since 2011-05-14, the following extra namespaces are created and reserved: * #Shared, containing all folders other users decided to share with you * #MilkyPond, containing public MP/DC information mailboxes you may subscribe at will Using IMAP, it is possible to setup rights (read only, write allowed…) to your own folders in order to share them with other users, or group of users. Public folders are owned by noone, and must be created by DC administrators ; if you need one, send us a request and we may be able to create it and delegate administration to your care (namespace name is subject to approval). Once created, public folders can be administered like shared folders. Client mail softwares support: * Horde: support namespaces, shared folders configurable via ''Options->Share Folders'' menu but no ACLs for public folders * Icedove/Thunderbird: support namespaces, shared and public folders configurable via folder selection and ''Tools->Imap-ACL'' menu action Most other softwares have namespace support only, so you should be able to use shared/public folders you have rights on but not configure them yourself (tell us if you know more software supporting this feature) == Retention fallback == The current retention period on our servers is 2 weeks, but can be temporary or permanently increased if needed. de934a3023505acc74ddfb82191f2a10d07afc79 206 205 2011-05-17T17:35:07Z Duck 2 /* Retention fallback */ wikitext text/x-wiki == Mail Hosting == What we can offer: * full hosting (MX1) on our servers: ** multiple email addresses which can be real mailboxes or mere redirections at another third party addresses ** based on ''milkypond.org'' (or maybe ''duckcorp.org'') domain(s) or you own domain(s) * fallback retention (MX2) on our servers or, at your choice, partner servers (currently via Hivane) == Full Hosting == === Access Methods === You can retrieve your mails, in case of a real mailbox, using: * IMAP+TLS (TCP 143) / IMAPS (TCP 993) on imap.duckcorp.org * or POP3+TLS (TCP 110) / POP3S (TCP 995) on pop.duckcorp.org * or one of the [https://webmail.duckcorp.org/ provided webmails] The IMAP protocol is recommended over POP3, as it provides many interresting features. If you want to download all your mails absolutely at home, loosing the ability to read your mail from anywhere on the planet, you can do that with IMAP too (look at your mail client settings). You can use our servers to send mails out too via smtp.duckcorp.org using: * SMTP+TLS (TCP 25) / SMTPS (TCP 465) * and SASL authentication === Mail Filtering === With your favourite mail client, you can probably filter your mails in proper folders already. Nevertheless, this can be a annoying operation: * blocking you mail client for a long time if you have to process plenty of mails * downloading each mail information, and sometimes content (depending on your filters), is lenghty too, and cost much bandwidth * syncing filters accross your machines (home desktop, laptop, office machine…) is a pain in the ass * processing only when you're online prevents triggering actions in a timely manner (automatic redirect, vacation messages…), and running a machine 24/7 with a mail client polling new mails every 30s is not a solution We provide a much better way to do this using the [[wikipedia:Sieve_(mail_filtering_language)|SIEVE]] filters. Shortly, SIEVE is a language dedicated to expressing mail filters. Our server is able to process your mails according to these filters as soon as they arrive. You then don't have to care about them anymore, and may use light mail clients or webmails when you're not on your machine with your favourite software. To push your filters on the server, a dedicated protocol exists: : MANAGESIEVE (TCP 4190) on sieve.duckcorp.org Several softwares support managing SIEVE rules: * Icedove/Thunderbird using the SIEVE extension (in xul-ext-sieve Debian package) provides a rules editor * Horde (Ingo) provides an easy to use web interface * Squirrelmail with the Avelsieve extension provides an easy to use web interface * Roundcube with an extension provides an easy to use web interface * sieve-connect provides a CLI to upload/download/activate your rules files (tell us if you know more software supporting this feature) You can read more info about SIEVE here: * supported SIEVE features on our server: http://pigeonhole.dovecot.org/ * http://www.fastmail.fm/docs/sieve/ * http://sieve.info/ === Shared/Public Folders === You may need to share mails or messages with friends or people you do stuff with (in a project or association). Depending on your needs, two solutions are possible: * share some of your own private folders, thus called ''shared folders'' * manage a special folder hierarchy, called ''public folders'' (even if they may not be accessible to everyone) Through IMAP, or our webmails internally using IMAP, it is possible to partition the folder hierarchy into ''namespaces''. Traditionally you are using the root namespace for your private folders. Additionnal namespaces can be created and will appear among your own folders or separate, depending on your mail client's choice of representation. To avoid name clashes, we decided to prefix all additionnal namespace names with a '''#'''. Since 2011-05-14, the following extra namespaces are created and reserved: * #Shared, containing all folders other users decided to share with you * #MilkyPond, containing public MP/DC information mailboxes you may subscribe at will Using IMAP, it is possible to setup rights (read only, write allowed…) to your own folders in order to share them with other users, or group of users. Public folders are owned by noone, and must be created by DC administrators ; if you need one, send us a request and we may be able to create it and delegate administration to your care (namespace name is subject to approval). Once created, public folders can be administered like shared folders. Client mail softwares support: * Horde: support namespaces, shared folders configurable via ''Options->Share Folders'' menu but no ACLs for public folders * Icedove/Thunderbird: support namespaces, shared and public folders configurable via folder selection and ''Tools->Imap-ACL'' menu action Most other softwares have namespace support only, so you should be able to use shared/public folders you have rights on but not configure them yourself (tell us if you know more software supporting this feature) == Retention fallback == The current retention period on our servers is 2 weeks, but can be temporary or permanently increased if needed. Mails flowing back to your primary server can be protected using TLS with certificate verification if you wish. d39273e8358d25aa717c814bbdc4d60250c1bc63 207 206 2011-05-17T17:50:23Z Duck 2 /* Retention fallback */ wikitext text/x-wiki == Mail Hosting == What we can offer: * full hosting (MX1) on our servers: ** multiple email addresses which can be real mailboxes or mere redirections at another third party addresses ** based on ''milkypond.org'' (or maybe ''duckcorp.org'') domain(s) or you own domain(s) * fallback retention (MX2) on our servers or, at your choice, partner servers (currently via Hivane) == Full Hosting == === Access Methods === You can retrieve your mails, in case of a real mailbox, using: * IMAP+TLS (TCP 143) / IMAPS (TCP 993) on imap.duckcorp.org * or POP3+TLS (TCP 110) / POP3S (TCP 995) on pop.duckcorp.org * or one of the [https://webmail.duckcorp.org/ provided webmails] The IMAP protocol is recommended over POP3, as it provides many interresting features. If you want to download all your mails absolutely at home, loosing the ability to read your mail from anywhere on the planet, you can do that with IMAP too (look at your mail client settings). You can use our servers to send mails out too via smtp.duckcorp.org using: * SMTP+TLS (TCP 25) / SMTPS (TCP 465) * and SASL authentication === Mail Filtering === With your favourite mail client, you can probably filter your mails in proper folders already. Nevertheless, this can be a annoying operation: * blocking you mail client for a long time if you have to process plenty of mails * downloading each mail information, and sometimes content (depending on your filters), is lenghty too, and cost much bandwidth * syncing filters accross your machines (home desktop, laptop, office machine…) is a pain in the ass * processing only when you're online prevents triggering actions in a timely manner (automatic redirect, vacation messages…), and running a machine 24/7 with a mail client polling new mails every 30s is not a solution We provide a much better way to do this using the [[wikipedia:Sieve_(mail_filtering_language)|SIEVE]] filters. Shortly, SIEVE is a language dedicated to expressing mail filters. Our server is able to process your mails according to these filters as soon as they arrive. You then don't have to care about them anymore, and may use light mail clients or webmails when you're not on your machine with your favourite software. To push your filters on the server, a dedicated protocol exists: : MANAGESIEVE (TCP 4190) on sieve.duckcorp.org Several softwares support managing SIEVE rules: * Icedove/Thunderbird using the SIEVE extension (in xul-ext-sieve Debian package) provides a rules editor * Horde (Ingo) provides an easy to use web interface * Squirrelmail with the Avelsieve extension provides an easy to use web interface * Roundcube with an extension provides an easy to use web interface * sieve-connect provides a CLI to upload/download/activate your rules files (tell us if you know more software supporting this feature) You can read more info about SIEVE here: * supported SIEVE features on our server: http://pigeonhole.dovecot.org/ * http://www.fastmail.fm/docs/sieve/ * http://sieve.info/ === Shared/Public Folders === You may need to share mails or messages with friends or people you do stuff with (in a project or association). Depending on your needs, two solutions are possible: * share some of your own private folders, thus called ''shared folders'' * manage a special folder hierarchy, called ''public folders'' (even if they may not be accessible to everyone) Through IMAP, or our webmails internally using IMAP, it is possible to partition the folder hierarchy into ''namespaces''. Traditionally you are using the root namespace for your private folders. Additionnal namespaces can be created and will appear among your own folders or separate, depending on your mail client's choice of representation. To avoid name clashes, we decided to prefix all additionnal namespace names with a '''#'''. Since 2011-05-14, the following extra namespaces are created and reserved: * #Shared, containing all folders other users decided to share with you * #MilkyPond, containing public MP/DC information mailboxes you may subscribe at will Using IMAP, it is possible to setup rights (read only, write allowed…) to your own folders in order to share them with other users, or group of users. Public folders are owned by noone, and must be created by DC administrators ; if you need one, send us a request and we may be able to create it and delegate administration to your care (namespace name is subject to approval). Once created, public folders can be administered like shared folders. Client mail softwares support: * Horde: support namespaces, shared folders configurable via ''Options->Share Folders'' menu but no ACLs for public folders * Icedove/Thunderbird: support namespaces, shared and public folders configurable via folder selection and ''Tools->Imap-ACL'' menu action Most other softwares have namespace support only, so you should be able to use shared/public folders you have rights on but not configure them yourself (tell us if you know more software supporting this feature) == Fallback retention == The current retention period on our servers is 2 weeks, but can be temporary or permanently increased if needed. Mails flowing back to your primary server can be protected using TLS with certificate verification if you wish. bb05a8f058d4ab5e1730dfeeb93c5b6789540ac2 208 207 2011-05-17T17:56:54Z Duck 2 /* Fallback retention */ wikitext text/x-wiki == Mail Hosting == What we can offer: * full hosting (MX1) on our servers: ** multiple email addresses which can be real mailboxes or mere redirections at another third party addresses ** based on ''milkypond.org'' (or maybe ''duckcorp.org'') domain(s) or you own domain(s) * fallback retention (MX2) on our servers or, at your choice, partner servers (currently via Hivane) == Full Hosting == === Access Methods === You can retrieve your mails, in case of a real mailbox, using: * IMAP+TLS (TCP 143) / IMAPS (TCP 993) on imap.duckcorp.org * or POP3+TLS (TCP 110) / POP3S (TCP 995) on pop.duckcorp.org * or one of the [https://webmail.duckcorp.org/ provided webmails] The IMAP protocol is recommended over POP3, as it provides many interresting features. If you want to download all your mails absolutely at home, loosing the ability to read your mail from anywhere on the planet, you can do that with IMAP too (look at your mail client settings). You can use our servers to send mails out too via smtp.duckcorp.org using: * SMTP+TLS (TCP 25) / SMTPS (TCP 465) * and SASL authentication === Mail Filtering === With your favourite mail client, you can probably filter your mails in proper folders already. Nevertheless, this can be a annoying operation: * blocking you mail client for a long time if you have to process plenty of mails * downloading each mail information, and sometimes content (depending on your filters), is lenghty too, and cost much bandwidth * syncing filters accross your machines (home desktop, laptop, office machine…) is a pain in the ass * processing only when you're online prevents triggering actions in a timely manner (automatic redirect, vacation messages…), and running a machine 24/7 with a mail client polling new mails every 30s is not a solution We provide a much better way to do this using the [[wikipedia:Sieve_(mail_filtering_language)|SIEVE]] filters. Shortly, SIEVE is a language dedicated to expressing mail filters. Our server is able to process your mails according to these filters as soon as they arrive. You then don't have to care about them anymore, and may use light mail clients or webmails when you're not on your machine with your favourite software. To push your filters on the server, a dedicated protocol exists: : MANAGESIEVE (TCP 4190) on sieve.duckcorp.org Several softwares support managing SIEVE rules: * Icedove/Thunderbird using the SIEVE extension (in xul-ext-sieve Debian package) provides a rules editor * Horde (Ingo) provides an easy to use web interface * Squirrelmail with the Avelsieve extension provides an easy to use web interface * Roundcube with an extension provides an easy to use web interface * sieve-connect provides a CLI to upload/download/activate your rules files (tell us if you know more software supporting this feature) You can read more info about SIEVE here: * supported SIEVE features on our server: http://pigeonhole.dovecot.org/ * http://www.fastmail.fm/docs/sieve/ * http://sieve.info/ === Shared/Public Folders === You may need to share mails or messages with friends or people you do stuff with (in a project or association). Depending on your needs, two solutions are possible: * share some of your own private folders, thus called ''shared folders'' * manage a special folder hierarchy, called ''public folders'' (even if they may not be accessible to everyone) Through IMAP, or our webmails internally using IMAP, it is possible to partition the folder hierarchy into ''namespaces''. Traditionally you are using the root namespace for your private folders. Additionnal namespaces can be created and will appear among your own folders or separate, depending on your mail client's choice of representation. To avoid name clashes, we decided to prefix all additionnal namespace names with a '''#'''. Since 2011-05-14, the following extra namespaces are created and reserved: * #Shared, containing all folders other users decided to share with you * #MilkyPond, containing public MP/DC information mailboxes you may subscribe at will Using IMAP, it is possible to setup rights (read only, write allowed…) to your own folders in order to share them with other users, or group of users. Public folders are owned by noone, and must be created by DC administrators ; if you need one, send us a request and we may be able to create it and delegate administration to your care (namespace name is subject to approval). Once created, public folders can be administered like shared folders. Client mail softwares support: * Horde: support namespaces, shared folders configurable via ''Options->Share Folders'' menu but no ACLs for public folders * Icedove/Thunderbird: support namespaces, shared and public folders configurable via folder selection and ''Tools->Imap-ACL'' menu action Most other softwares have namespace support only, so you should be able to use shared/public folders you have rights on but not configure them yourself (tell us if you know more software supporting this feature) == Fallback retention == The current retention period on our servers is 2 weeks, but can be temporary or permanently increased if needed. Mails flowing back to your primary server can be protected using TLS with certificate verification if you wish. Antivirus and antispam filtering are not applied to relayed mails, so we do not mess with your prefered strategy on your primary server, nevertheless basic checks (EHLO, DNS…) and RBL scoring are done to avoid accepting tons of SPAMs. eaadd7adbd691f641f930e7b37e93971e37138d4 209 208 2011-05-17T17:57:53Z Duck 2 /* Full Hosting */ wikitext text/x-wiki == Mail Hosting == What we can offer: * full hosting (MX1) on our servers: ** multiple email addresses which can be real mailboxes or mere redirections at another third party addresses ** based on ''milkypond.org'' (or maybe ''duckcorp.org'') domain(s) or you own domain(s) * fallback retention (MX2) on our servers or, at your choice, partner servers (currently via Hivane) == Full Hosting == === Access Methods === You can retrieve your mails, in case of a real mailbox, using: * IMAP+TLS (TCP 143) / IMAPS (TCP 993) on imap.duckcorp.org * or POP3+TLS (TCP 110) / POP3S (TCP 995) on pop.duckcorp.org * or one of the [https://webmail.duckcorp.org/ provided webmails] The IMAP protocol is recommended over POP3, as it provides many interresting features. If you want to download all your mails absolutely at home, loosing the ability to read your mail from anywhere on the planet, you can do that with IMAP too (look at your mail client settings). You can use our servers to send mails out too via smtp.duckcorp.org using: * SMTP+TLS (TCP 25) / SMTPS (TCP 465) * and SASL authentication === Antivirus and Antispam === === Mail Filtering === With your favourite mail client, you can probably filter your mails in proper folders already. Nevertheless, this can be a annoying operation: * blocking you mail client for a long time if you have to process plenty of mails * downloading each mail information, and sometimes content (depending on your filters), is lenghty too, and cost much bandwidth * syncing filters accross your machines (home desktop, laptop, office machine…) is a pain in the ass * processing only when you're online prevents triggering actions in a timely manner (automatic redirect, vacation messages…), and running a machine 24/7 with a mail client polling new mails every 30s is not a solution We provide a much better way to do this using the [[wikipedia:Sieve_(mail_filtering_language)|SIEVE]] filters. Shortly, SIEVE is a language dedicated to expressing mail filters. Our server is able to process your mails according to these filters as soon as they arrive. You then don't have to care about them anymore, and may use light mail clients or webmails when you're not on your machine with your favourite software. To push your filters on the server, a dedicated protocol exists: : MANAGESIEVE (TCP 4190) on sieve.duckcorp.org Several softwares support managing SIEVE rules: * Icedove/Thunderbird using the SIEVE extension (in xul-ext-sieve Debian package) provides a rules editor * Horde (Ingo) provides an easy to use web interface * Squirrelmail with the Avelsieve extension provides an easy to use web interface * Roundcube with an extension provides an easy to use web interface * sieve-connect provides a CLI to upload/download/activate your rules files (tell us if you know more software supporting this feature) You can read more info about SIEVE here: * supported SIEVE features on our server: http://pigeonhole.dovecot.org/ * http://www.fastmail.fm/docs/sieve/ * http://sieve.info/ === Shared/Public Folders === You may need to share mails or messages with friends or people you do stuff with (in a project or association). Depending on your needs, two solutions are possible: * share some of your own private folders, thus called ''shared folders'' * manage a special folder hierarchy, called ''public folders'' (even if they may not be accessible to everyone) Through IMAP, or our webmails internally using IMAP, it is possible to partition the folder hierarchy into ''namespaces''. Traditionally you are using the root namespace for your private folders. Additionnal namespaces can be created and will appear among your own folders or separate, depending on your mail client's choice of representation. To avoid name clashes, we decided to prefix all additionnal namespace names with a '''#'''. Since 2011-05-14, the following extra namespaces are created and reserved: * #Shared, containing all folders other users decided to share with you * #MilkyPond, containing public MP/DC information mailboxes you may subscribe at will Using IMAP, it is possible to setup rights (read only, write allowed…) to your own folders in order to share them with other users, or group of users. Public folders are owned by noone, and must be created by DC administrators ; if you need one, send us a request and we may be able to create it and delegate administration to your care (namespace name is subject to approval). Once created, public folders can be administered like shared folders. Client mail softwares support: * Horde: support namespaces, shared folders configurable via ''Options->Share Folders'' menu but no ACLs for public folders * Icedove/Thunderbird: support namespaces, shared and public folders configurable via folder selection and ''Tools->Imap-ACL'' menu action Most other softwares have namespace support only, so you should be able to use shared/public folders you have rights on but not configure them yourself (tell us if you know more software supporting this feature) == Fallback retention == The current retention period on our servers is 2 weeks, but can be temporary or permanently increased if needed. Mails flowing back to your primary server can be protected using TLS with certificate verification if you wish. Antivirus and antispam filtering are not applied to relayed mails, so we do not mess with your prefered strategy on your primary server, nevertheless basic checks (EHLO, DNS…) and RBL scoring are done to avoid accepting tons of SPAMs. 74875628ec307df35ad1a80db896499056ccc24f 210 209 2011-05-17T18:18:25Z Duck 2 /* Antivirus and Antispam */ wikitext text/x-wiki == Mail Hosting == What we can offer: * full hosting (MX1) on our servers: ** multiple email addresses which can be real mailboxes or mere redirections at another third party addresses ** based on ''milkypond.org'' (or maybe ''duckcorp.org'') domain(s) or you own domain(s) * fallback retention (MX2) on our servers or, at your choice, partner servers (currently via Hivane) == Full Hosting == === Access Methods === You can retrieve your mails, in case of a real mailbox, using: * IMAP+TLS (TCP 143) / IMAPS (TCP 993) on imap.duckcorp.org * or POP3+TLS (TCP 110) / POP3S (TCP 995) on pop.duckcorp.org * or one of the [https://webmail.duckcorp.org/ provided webmails] The IMAP protocol is recommended over POP3, as it provides many interresting features. If you want to download all your mails absolutely at home, loosing the ability to read your mail from anywhere on the planet, you can do that with IMAP too (look at your mail client settings). You can use our servers to send mails out too via smtp.duckcorp.org using: * SMTP+TLS (TCP 25) / SMTPS (TCP 465) * and SASL authentication === Antivirus and Antispam === Mails stored on our server are checked upon arrival for viruses and SPAMs. Mail redirected to a third party mailbox are not, not to mess with the strategy of the the final destination (which could arm learning greatly). Mails being viruses are suppressed automatically upon arrival. Once in a week, an extra antivirus check is done on all hosted mailboxes, to remove viruses not detected at the time it arrived (our antivirus database is updated daily), so you may see such mail disappear from your mailbox, don't fear. SPAMs are more difficult to detect, and it is an error-prone process, so we chose to use a learning software intead of using a global database. On the bright side of things, you should never loose mails and the software should be able to learn what is a SPAM from *your* point of view, but on the grey side you will have to teach him regulary to avoid errors. When your account is created, it acts like an empty headed body letting everything through, but after a few weeks of teaching it is able to recognise most of your habits and block a lot of annoying SPAM. === Mail Filtering === With your favourite mail client, you can probably filter your mails in proper folders already. Nevertheless, this can be a annoying operation: * blocking you mail client for a long time if you have to process plenty of mails * downloading each mail information, and sometimes content (depending on your filters), is lenghty too, and cost much bandwidth * syncing filters accross your machines (home desktop, laptop, office machine…) is a pain in the ass * processing only when you're online prevents triggering actions in a timely manner (automatic redirect, vacation messages…), and running a machine 24/7 with a mail client polling new mails every 30s is not a solution We provide a much better way to do this using the [[wikipedia:Sieve_(mail_filtering_language)|SIEVE]] filters. Shortly, SIEVE is a language dedicated to expressing mail filters. Our server is able to process your mails according to these filters as soon as they arrive. You then don't have to care about them anymore, and may use light mail clients or webmails when you're not on your machine with your favourite software. To push your filters on the server, a dedicated protocol exists: : MANAGESIEVE (TCP 4190) on sieve.duckcorp.org Several softwares support managing SIEVE rules: * Icedove/Thunderbird using the SIEVE extension (in xul-ext-sieve Debian package) provides a rules editor * Horde (Ingo) provides an easy to use web interface * Squirrelmail with the Avelsieve extension provides an easy to use web interface * Roundcube with an extension provides an easy to use web interface * sieve-connect provides a CLI to upload/download/activate your rules files (tell us if you know more software supporting this feature) You can read more info about SIEVE here: * supported SIEVE features on our server: http://pigeonhole.dovecot.org/ * http://www.fastmail.fm/docs/sieve/ * http://sieve.info/ === Shared/Public Folders === You may need to share mails or messages with friends or people you do stuff with (in a project or association). Depending on your needs, two solutions are possible: * share some of your own private folders, thus called ''shared folders'' * manage a special folder hierarchy, called ''public folders'' (even if they may not be accessible to everyone) Through IMAP, or our webmails internally using IMAP, it is possible to partition the folder hierarchy into ''namespaces''. Traditionally you are using the root namespace for your private folders. Additionnal namespaces can be created and will appear among your own folders or separate, depending on your mail client's choice of representation. To avoid name clashes, we decided to prefix all additionnal namespace names with a '''#'''. Since 2011-05-14, the following extra namespaces are created and reserved: * #Shared, containing all folders other users decided to share with you * #MilkyPond, containing public MP/DC information mailboxes you may subscribe at will Using IMAP, it is possible to setup rights (read only, write allowed…) to your own folders in order to share them with other users, or group of users. Public folders are owned by noone, and must be created by DC administrators ; if you need one, send us a request and we may be able to create it and delegate administration to your care (namespace name is subject to approval). Once created, public folders can be administered like shared folders. Client mail softwares support: * Horde: support namespaces, shared folders configurable via ''Options->Share Folders'' menu but no ACLs for public folders * Icedove/Thunderbird: support namespaces, shared and public folders configurable via folder selection and ''Tools->Imap-ACL'' menu action Most other softwares have namespace support only, so you should be able to use shared/public folders you have rights on but not configure them yourself (tell us if you know more software supporting this feature) == Fallback retention == The current retention period on our servers is 2 weeks, but can be temporary or permanently increased if needed. Mails flowing back to your primary server can be protected using TLS with certificate verification if you wish. Antivirus and antispam filtering are not applied to relayed mails, so we do not mess with your prefered strategy on your primary server, nevertheless basic checks (EHLO, DNS…) and RBL scoring are done to avoid accepting tons of SPAMs. c5c59a7cfcdea3b5a1fb295eb8c572b851e007a3 211 210 2011-05-17T18:25:53Z Duck 2 /* Antivirus and Antispam */ wikitext text/x-wiki == Mail Hosting == What we can offer: * full hosting (MX1) on our servers: ** multiple email addresses which can be real mailboxes or mere redirections at another third party addresses ** based on ''milkypond.org'' (or maybe ''duckcorp.org'') domain(s) or you own domain(s) * fallback retention (MX2) on our servers or, at your choice, partner servers (currently via Hivane) == Full Hosting == === Access Methods === You can retrieve your mails, in case of a real mailbox, using: * IMAP+TLS (TCP 143) / IMAPS (TCP 993) on imap.duckcorp.org * or POP3+TLS (TCP 110) / POP3S (TCP 995) on pop.duckcorp.org * or one of the [https://webmail.duckcorp.org/ provided webmails] The IMAP protocol is recommended over POP3, as it provides many interresting features. If you want to download all your mails absolutely at home, loosing the ability to read your mail from anywhere on the planet, you can do that with IMAP too (look at your mail client settings). You can use our servers to send mails out too via smtp.duckcorp.org using: * SMTP+TLS (TCP 25) / SMTPS (TCP 465) * and SASL authentication === Antivirus and Antispam === Mails stored on our server are checked upon arrival for viruses and SPAMs. Mail redirected to a third party mailbox are not, not to mess with the strategy of the the final destination (which could arm learning greatly). Mails being viruses are suppressed automatically upon arrival. Once in a week, an extra antivirus check is done on all hosted mailboxes, to remove viruses not detected at the time it arrived (our antivirus database is updated daily), so you may see such mail disappear from your mailbox, don't fear. SPAMs are more difficult to detect, and it is an error-prone process, so we chose to use a learning software intead of using a global database. On the bright side of things, you should never loose mails and the software should be able to learn what is a SPAM from '''your''' point of view, but on the grey side you will have to teach him regulary to avoid errors. When your account is created, it acts like an empty headed body letting everything through, but after a few weeks of teaching it is able to recognise most of your habits and block a lot of annoying SPAM. You can yourself setup a few parameters… To teach the system, you can: * use the [https://spamfilter.duckcorp.org/ web interface] to retrain from errors in the ''History'' page * resend SPAM to dc-spam@duckcorp.org and HAM (non-SPAM) to dc-ham@duckcorp.org *: {{warning}} PLEASE TAKE CARE to use the ''resend'' function of your mailer and never use ''forward'', which would result in '''yourself''' being considered as spam or ham === Mail Filtering === With your favourite mail client, you can probably filter your mails in proper folders already. Nevertheless, this can be a annoying operation: * blocking you mail client for a long time if you have to process plenty of mails * downloading each mail information, and sometimes content (depending on your filters), is lenghty too, and cost much bandwidth * syncing filters accross your machines (home desktop, laptop, office machine…) is a pain in the ass * processing only when you're online prevents triggering actions in a timely manner (automatic redirect, vacation messages…), and running a machine 24/7 with a mail client polling new mails every 30s is not a solution We provide a much better way to do this using the [[wikipedia:Sieve_(mail_filtering_language)|SIEVE]] filters. Shortly, SIEVE is a language dedicated to expressing mail filters. Our server is able to process your mails according to these filters as soon as they arrive. You then don't have to care about them anymore, and may use light mail clients or webmails when you're not on your machine with your favourite software. To push your filters on the server, a dedicated protocol exists: : MANAGESIEVE (TCP 4190) on sieve.duckcorp.org Several softwares support managing SIEVE rules: * Icedove/Thunderbird using the SIEVE extension (in xul-ext-sieve Debian package) provides a rules editor * Horde (Ingo) provides an easy to use web interface * Squirrelmail with the Avelsieve extension provides an easy to use web interface * Roundcube with an extension provides an easy to use web interface * sieve-connect provides a CLI to upload/download/activate your rules files (tell us if you know more software supporting this feature) You can read more info about SIEVE here: * supported SIEVE features on our server: http://pigeonhole.dovecot.org/ * http://www.fastmail.fm/docs/sieve/ * http://sieve.info/ === Shared/Public Folders === You may need to share mails or messages with friends or people you do stuff with (in a project or association). Depending on your needs, two solutions are possible: * share some of your own private folders, thus called ''shared folders'' * manage a special folder hierarchy, called ''public folders'' (even if they may not be accessible to everyone) Through IMAP, or our webmails internally using IMAP, it is possible to partition the folder hierarchy into ''namespaces''. Traditionally you are using the root namespace for your private folders. Additionnal namespaces can be created and will appear among your own folders or separate, depending on your mail client's choice of representation. To avoid name clashes, we decided to prefix all additionnal namespace names with a '''#'''. Since 2011-05-14, the following extra namespaces are created and reserved: * #Shared, containing all folders other users decided to share with you * #MilkyPond, containing public MP/DC information mailboxes you may subscribe at will Using IMAP, it is possible to setup rights (read only, write allowed…) to your own folders in order to share them with other users, or group of users. Public folders are owned by noone, and must be created by DC administrators ; if you need one, send us a request and we may be able to create it and delegate administration to your care (namespace name is subject to approval). Once created, public folders can be administered like shared folders. Client mail softwares support: * Horde: support namespaces, shared folders configurable via ''Options->Share Folders'' menu but no ACLs for public folders * Icedove/Thunderbird: support namespaces, shared and public folders configurable via folder selection and ''Tools->Imap-ACL'' menu action Most other softwares have namespace support only, so you should be able to use shared/public folders you have rights on but not configure them yourself (tell us if you know more software supporting this feature) == Fallback retention == The current retention period on our servers is 2 weeks, but can be temporary or permanently increased if needed. Mails flowing back to your primary server can be protected using TLS with certificate verification if you wish. Antivirus and antispam filtering are not applied to relayed mails, so we do not mess with your prefered strategy on your primary server, nevertheless basic checks (EHLO, DNS…) and RBL scoring are done to avoid accepting tons of SPAMs. ffe84c9fd2bfe8f88541f3af917457e0ab594859 212 211 2011-05-17T18:38:12Z Duck 2 /* Antivirus and Antispam */ wikitext text/x-wiki == Mail Hosting == What we can offer: * full hosting (MX1) on our servers: ** multiple email addresses which can be real mailboxes or mere redirections at another third party addresses ** based on ''milkypond.org'' (or maybe ''duckcorp.org'') domain(s) or you own domain(s) * fallback retention (MX2) on our servers or, at your choice, partner servers (currently via Hivane) == Full Hosting == === Access Methods === You can retrieve your mails, in case of a real mailbox, using: * IMAP+TLS (TCP 143) / IMAPS (TCP 993) on imap.duckcorp.org * or POP3+TLS (TCP 110) / POP3S (TCP 995) on pop.duckcorp.org * or one of the [https://webmail.duckcorp.org/ provided webmails] The IMAP protocol is recommended over POP3, as it provides many interresting features. If you want to download all your mails absolutely at home, loosing the ability to read your mail from anywhere on the planet, you can do that with IMAP too (look at your mail client settings). You can use our servers to send mails out too via smtp.duckcorp.org using: * SMTP+TLS (TCP 25) / SMTPS (TCP 465) * and SASL authentication === Antivirus and Antispam === Mails stored on our server are checked upon arrival for viruses and SPAMs. Mail redirected to a third party mailbox are not, not to mess with the strategy of the the final destination (which could arm learning greatly). Mails being viruses are suppressed automatically upon arrival. Once in a week, an extra antivirus check is done on all hosted mailboxes, to remove viruses not detected at the time it arrived (our antivirus database is updated daily), so you may see such mail disappear from your mailbox, don't fear. SPAMs are more difficult to detect, and it is an error-prone process, so we chose to use a learning software intead of using a global database. On the bright side of things, you should never loose mails and the software should be able to learn what is a SPAM from '''your''' point of view, but on the grey side you will have to teach him regulary to avoid errors. When your account is created, it acts like an empty headed body letting everything through, but after a few weeks of teaching it is able to recognise most of your habits and block a lot of annoying SPAM. You can yourself setup a few parameters in the ''Preferences'' page of the [https://spamfilter.duckcorp.org/ web interface], mostly: * how the system should train: ** TEFT (''On every new message scanned by the filter''): useful to learn very quickly especially on a new mailbox or when you've got tons of spam on your addresses, but you need to train it regulary or it will learn wrong (very quickly too !) ** TOE (''Only when the filter makes a mistake''): slow learning, but if you don't have time for training very often or go on long holidays without internet access this mode will give you a stable behavior ** TUM (''Only with new data or if the filter makes a mistake''): trade-off between the two previous modes, learn quite fast and not too demanding, adapts better to new SPAMs then TOE To teach the system, you can: * use the [https://spamfilter.duckcorp.org/ web interface] to retrain from errors in the ''History'' page * resend SPAM to dc-spam@duckcorp.org and HAM (non-SPAM) to dc-ham@duckcorp.org *: {{warning}} PLEASE TAKE CARE to use the ''resend'' function of your mailer and never use ''forward'', which would result in '''yourself''' being considered as spam or ham === Mail Filtering === With your favourite mail client, you can probably filter your mails in proper folders already. Nevertheless, this can be a annoying operation: * blocking you mail client for a long time if you have to process plenty of mails * downloading each mail information, and sometimes content (depending on your filters), is lenghty too, and cost much bandwidth * syncing filters accross your machines (home desktop, laptop, office machine…) is a pain in the ass * processing only when you're online prevents triggering actions in a timely manner (automatic redirect, vacation messages…), and running a machine 24/7 with a mail client polling new mails every 30s is not a solution We provide a much better way to do this using the [[wikipedia:Sieve_(mail_filtering_language)|SIEVE]] filters. Shortly, SIEVE is a language dedicated to expressing mail filters. Our server is able to process your mails according to these filters as soon as they arrive. You then don't have to care about them anymore, and may use light mail clients or webmails when you're not on your machine with your favourite software. To push your filters on the server, a dedicated protocol exists: : MANAGESIEVE (TCP 4190) on sieve.duckcorp.org Several softwares support managing SIEVE rules: * Icedove/Thunderbird using the SIEVE extension (in xul-ext-sieve Debian package) provides a rules editor * Horde (Ingo) provides an easy to use web interface * Squirrelmail with the Avelsieve extension provides an easy to use web interface * Roundcube with an extension provides an easy to use web interface * sieve-connect provides a CLI to upload/download/activate your rules files (tell us if you know more software supporting this feature) You can read more info about SIEVE here: * supported SIEVE features on our server: http://pigeonhole.dovecot.org/ * http://www.fastmail.fm/docs/sieve/ * http://sieve.info/ === Shared/Public Folders === You may need to share mails or messages with friends or people you do stuff with (in a project or association). Depending on your needs, two solutions are possible: * share some of your own private folders, thus called ''shared folders'' * manage a special folder hierarchy, called ''public folders'' (even if they may not be accessible to everyone) Through IMAP, or our webmails internally using IMAP, it is possible to partition the folder hierarchy into ''namespaces''. Traditionally you are using the root namespace for your private folders. Additionnal namespaces can be created and will appear among your own folders or separate, depending on your mail client's choice of representation. To avoid name clashes, we decided to prefix all additionnal namespace names with a '''#'''. Since 2011-05-14, the following extra namespaces are created and reserved: * #Shared, containing all folders other users decided to share with you * #MilkyPond, containing public MP/DC information mailboxes you may subscribe at will Using IMAP, it is possible to setup rights (read only, write allowed…) to your own folders in order to share them with other users, or group of users. Public folders are owned by noone, and must be created by DC administrators ; if you need one, send us a request and we may be able to create it and delegate administration to your care (namespace name is subject to approval). Once created, public folders can be administered like shared folders. Client mail softwares support: * Horde: support namespaces, shared folders configurable via ''Options->Share Folders'' menu but no ACLs for public folders * Icedove/Thunderbird: support namespaces, shared and public folders configurable via folder selection and ''Tools->Imap-ACL'' menu action Most other softwares have namespace support only, so you should be able to use shared/public folders you have rights on but not configure them yourself (tell us if you know more software supporting this feature) == Fallback retention == The current retention period on our servers is 2 weeks, but can be temporary or permanently increased if needed. Mails flowing back to your primary server can be protected using TLS with certificate verification if you wish. Antivirus and antispam filtering are not applied to relayed mails, so we do not mess with your prefered strategy on your primary server, nevertheless basic checks (EHLO, DNS…) and RBL scoring are done to avoid accepting tons of SPAMs. 33574f60dae031d7685586a31f511d11da6b01d3 213 212 2011-05-17T18:40:11Z Duck 2 /* Antivirus and Antispam */ wikitext text/x-wiki == Mail Hosting == What we can offer: * full hosting (MX1) on our servers: ** multiple email addresses which can be real mailboxes or mere redirections at another third party addresses ** based on ''milkypond.org'' (or maybe ''duckcorp.org'') domain(s) or you own domain(s) * fallback retention (MX2) on our servers or, at your choice, partner servers (currently via Hivane) == Full Hosting == === Access Methods === You can retrieve your mails, in case of a real mailbox, using: * IMAP+TLS (TCP 143) / IMAPS (TCP 993) on imap.duckcorp.org * or POP3+TLS (TCP 110) / POP3S (TCP 995) on pop.duckcorp.org * or one of the [https://webmail.duckcorp.org/ provided webmails] The IMAP protocol is recommended over POP3, as it provides many interresting features. If you want to download all your mails absolutely at home, loosing the ability to read your mail from anywhere on the planet, you can do that with IMAP too (look at your mail client settings). You can use our servers to send mails out too via smtp.duckcorp.org using: * SMTP+TLS (TCP 25) / SMTPS (TCP 465) * and SASL authentication === Antivirus and Antispam === Mails stored on our server are checked upon arrival for viruses and SPAMs. Mail redirected to a third party mailbox are not, not to mess with the strategy of the the final destination (which could arm learning greatly). Mails being viruses are suppressed automatically upon arrival. Once in a week, an extra antivirus check is done on all hosted mailboxes, to remove viruses not detected at the time it arrived (our antivirus database is updated daily), so you may see such mail disappear from your mailbox, don't fear. SPAMs are more difficult to detect, and it is an error-prone process, so we chose to use a learning software intead of using a global database. On the bright side of things, you should never loose mails and the software should be able to learn what is a SPAM from '''your''' point of view, but on the grey side you will have to teach him regulary to avoid errors. When your account is created, it acts like an empty headed body letting everything through, but after a few weeks of teaching it is able to recognise most of your habits and block a lot of annoying SPAM. You can yourself setup a few parameters in the ''Preferences'' page of the [https://spamfilter.duckcorp.org/ web interface], mostly: * how the system should train: ** TEFT (''On every new message scanned by the filter''): useful to learn very quickly especially on a new mailbox or when you've got tons of spam on your addresses, but you need to train it regulary or it will learn wrong (very quickly too !) ** TOE (''Only when the filter makes a mistake''): slow learning, but if you don't have time for training very often or go on long holidays without internet access this mode will give you a stable behavior ** TUM (''Only with new data or if the filter makes a mistake''): trade-off between the two previous modes, learn quite fast and not too demanding, adapts better to new SPAMs then TOE * filter sensitivity, so you can ask the system to be more or less aggressive To teach the system, you can: * use the [https://spamfilter.duckcorp.org/ web interface] to retrain from errors in the ''History'' page * resend SPAM to dc-spam@duckcorp.org and HAM (non-SPAM) to dc-ham@duckcorp.org *: {{warning}} PLEASE TAKE CARE to use the ''resend'' function of your mailer and never use ''forward'', which would result in '''yourself''' being considered as spam or ham === Mail Filtering === With your favourite mail client, you can probably filter your mails in proper folders already. Nevertheless, this can be a annoying operation: * blocking you mail client for a long time if you have to process plenty of mails * downloading each mail information, and sometimes content (depending on your filters), is lenghty too, and cost much bandwidth * syncing filters accross your machines (home desktop, laptop, office machine…) is a pain in the ass * processing only when you're online prevents triggering actions in a timely manner (automatic redirect, vacation messages…), and running a machine 24/7 with a mail client polling new mails every 30s is not a solution We provide a much better way to do this using the [[wikipedia:Sieve_(mail_filtering_language)|SIEVE]] filters. Shortly, SIEVE is a language dedicated to expressing mail filters. Our server is able to process your mails according to these filters as soon as they arrive. You then don't have to care about them anymore, and may use light mail clients or webmails when you're not on your machine with your favourite software. To push your filters on the server, a dedicated protocol exists: : MANAGESIEVE (TCP 4190) on sieve.duckcorp.org Several softwares support managing SIEVE rules: * Icedove/Thunderbird using the SIEVE extension (in xul-ext-sieve Debian package) provides a rules editor * Horde (Ingo) provides an easy to use web interface * Squirrelmail with the Avelsieve extension provides an easy to use web interface * Roundcube with an extension provides an easy to use web interface * sieve-connect provides a CLI to upload/download/activate your rules files (tell us if you know more software supporting this feature) You can read more info about SIEVE here: * supported SIEVE features on our server: http://pigeonhole.dovecot.org/ * http://www.fastmail.fm/docs/sieve/ * http://sieve.info/ === Shared/Public Folders === You may need to share mails or messages with friends or people you do stuff with (in a project or association). Depending on your needs, two solutions are possible: * share some of your own private folders, thus called ''shared folders'' * manage a special folder hierarchy, called ''public folders'' (even if they may not be accessible to everyone) Through IMAP, or our webmails internally using IMAP, it is possible to partition the folder hierarchy into ''namespaces''. Traditionally you are using the root namespace for your private folders. Additionnal namespaces can be created and will appear among your own folders or separate, depending on your mail client's choice of representation. To avoid name clashes, we decided to prefix all additionnal namespace names with a '''#'''. Since 2011-05-14, the following extra namespaces are created and reserved: * #Shared, containing all folders other users decided to share with you * #MilkyPond, containing public MP/DC information mailboxes you may subscribe at will Using IMAP, it is possible to setup rights (read only, write allowed…) to your own folders in order to share them with other users, or group of users. Public folders are owned by noone, and must be created by DC administrators ; if you need one, send us a request and we may be able to create it and delegate administration to your care (namespace name is subject to approval). Once created, public folders can be administered like shared folders. Client mail softwares support: * Horde: support namespaces, shared folders configurable via ''Options->Share Folders'' menu but no ACLs for public folders * Icedove/Thunderbird: support namespaces, shared and public folders configurable via folder selection and ''Tools->Imap-ACL'' menu action Most other softwares have namespace support only, so you should be able to use shared/public folders you have rights on but not configure them yourself (tell us if you know more software supporting this feature) == Fallback retention == The current retention period on our servers is 2 weeks, but can be temporary or permanently increased if needed. Mails flowing back to your primary server can be protected using TLS with certificate verification if you wish. Antivirus and antispam filtering are not applied to relayed mails, so we do not mess with your prefered strategy on your primary server, nevertheless basic checks (EHLO, DNS…) and RBL scoring are done to avoid accepting tons of SPAMs. ce7d7b73ed7232dc07c272dcd6eef5a2a638685e 214 213 2011-05-17T18:48:07Z Duck 2 /* Antivirus and Antispam */ wikitext text/x-wiki == Mail Hosting == What we can offer: * full hosting (MX1) on our servers: ** multiple email addresses which can be real mailboxes or mere redirections at another third party addresses ** based on ''milkypond.org'' (or maybe ''duckcorp.org'') domain(s) or you own domain(s) * fallback retention (MX2) on our servers or, at your choice, partner servers (currently via Hivane) == Full Hosting == === Access Methods === You can retrieve your mails, in case of a real mailbox, using: * IMAP+TLS (TCP 143) / IMAPS (TCP 993) on imap.duckcorp.org * or POP3+TLS (TCP 110) / POP3S (TCP 995) on pop.duckcorp.org * or one of the [https://webmail.duckcorp.org/ provided webmails] The IMAP protocol is recommended over POP3, as it provides many interresting features. If you want to download all your mails absolutely at home, loosing the ability to read your mail from anywhere on the planet, you can do that with IMAP too (look at your mail client settings). You can use our servers to send mails out too via smtp.duckcorp.org using: * SMTP+TLS (TCP 25) / SMTPS (TCP 465) * and SASL authentication === Antivirus and Antispam === Mails stored on our server are checked upon arrival for viruses and SPAMs. Mail redirected to a third party mailbox are not, not to mess with the strategy of the the final destination (which could arm learning greatly). Mails being viruses are suppressed automatically upon arrival. Once in a week, an extra antivirus check is done on all hosted mailboxes, to remove viruses not detected at the time it arrived (our antivirus database is updated daily), so you may see such mail disappear from your mailbox, don't fear. SPAMs are more difficult to detect, and it is an error-prone process, so we chose to use a learning software intead of using a global database. On the bright side of things, you should never loose mails and the software should be able to learn what is a SPAM from '''your''' point of view, but on the grey side you will have to teach him regulary to avoid errors. When your account is created, it acts like an empty headed body letting everything through, but after a few weeks of teaching it is able to recognise most of your habits and block a lot of annoying SPAM. You can yourself setup a few parameters in the ''Preferences'' page of the [https://spamfilter.duckcorp.org/ web interface], mostly: * how the system should train: ** TEFT (''On every new message scanned by the filter''): useful to learn very quickly especially on a new mailbox or when you've got tons of spam on your addresses, but you need to train it regulary or it will learn wrong (very quickly too !) ** TOE (''Only when the filter makes a mistake''): slow learning, but if you don't have time for training very often or go on long holidays without internet access this mode will give you a stable behavior ** TUM (''Only with new data or if the filter makes a mistake''): trade-off between the two previous modes, learn quite fast and not too demanding, adapts better to new SPAMs then TOE * filter sensitivity, so you can ask the system to be more or less aggressive * message Handling: * ''Quarantine the message'': mails are not delivered to your mailbox but retained by the system and you can only manage them through the [https://spamfilter.duckcorp.org/ web interface] ; if you retrain a quarantined mail as HAM, it will be freed from quarantine and delivered in your mailbox at once ; in this mode, you need to flush your quarantine once in a while * ''Tag the Subject header with'': mails are delivered with a modified title (which is a tad ugly) * ''Deliver the message normally with a X-DSPAM-Result header'': mails are delivered with a special field in your mail headers (not always visible depending on your mail client and its configuration) ; this is quite handy if you prefer SPAMs arranged in a specific folder To teach the system, you can: * use the [https://spamfilter.duckcorp.org/ web interface] to retrain from errors in the ''History'' page * resend SPAM to dc-spam@duckcorp.org and HAM (non-SPAM) to dc-ham@duckcorp.org *: {{warning}} PLEASE TAKE CARE to use the ''resend'' function of your mailer and never use ''forward'', which would result in '''yourself''' being considered as spam or ham === Mail Filtering === With your favourite mail client, you can probably filter your mails in proper folders already. Nevertheless, this can be a annoying operation: * blocking you mail client for a long time if you have to process plenty of mails * downloading each mail information, and sometimes content (depending on your filters), is lenghty too, and cost much bandwidth * syncing filters accross your machines (home desktop, laptop, office machine…) is a pain in the ass * processing only when you're online prevents triggering actions in a timely manner (automatic redirect, vacation messages…), and running a machine 24/7 with a mail client polling new mails every 30s is not a solution We provide a much better way to do this using the [[wikipedia:Sieve_(mail_filtering_language)|SIEVE]] filters. Shortly, SIEVE is a language dedicated to expressing mail filters. Our server is able to process your mails according to these filters as soon as they arrive. You then don't have to care about them anymore, and may use light mail clients or webmails when you're not on your machine with your favourite software. To push your filters on the server, a dedicated protocol exists: : MANAGESIEVE (TCP 4190) on sieve.duckcorp.org Several softwares support managing SIEVE rules: * Icedove/Thunderbird using the SIEVE extension (in xul-ext-sieve Debian package) provides a rules editor * Horde (Ingo) provides an easy to use web interface * Squirrelmail with the Avelsieve extension provides an easy to use web interface * Roundcube with an extension provides an easy to use web interface * sieve-connect provides a CLI to upload/download/activate your rules files (tell us if you know more software supporting this feature) You can read more info about SIEVE here: * supported SIEVE features on our server: http://pigeonhole.dovecot.org/ * http://www.fastmail.fm/docs/sieve/ * http://sieve.info/ === Shared/Public Folders === You may need to share mails or messages with friends or people you do stuff with (in a project or association). Depending on your needs, two solutions are possible: * share some of your own private folders, thus called ''shared folders'' * manage a special folder hierarchy, called ''public folders'' (even if they may not be accessible to everyone) Through IMAP, or our webmails internally using IMAP, it is possible to partition the folder hierarchy into ''namespaces''. Traditionally you are using the root namespace for your private folders. Additionnal namespaces can be created and will appear among your own folders or separate, depending on your mail client's choice of representation. To avoid name clashes, we decided to prefix all additionnal namespace names with a '''#'''. Since 2011-05-14, the following extra namespaces are created and reserved: * #Shared, containing all folders other users decided to share with you * #MilkyPond, containing public MP/DC information mailboxes you may subscribe at will Using IMAP, it is possible to setup rights (read only, write allowed…) to your own folders in order to share them with other users, or group of users. Public folders are owned by noone, and must be created by DC administrators ; if you need one, send us a request and we may be able to create it and delegate administration to your care (namespace name is subject to approval). Once created, public folders can be administered like shared folders. Client mail softwares support: * Horde: support namespaces, shared folders configurable via ''Options->Share Folders'' menu but no ACLs for public folders * Icedove/Thunderbird: support namespaces, shared and public folders configurable via folder selection and ''Tools->Imap-ACL'' menu action Most other softwares have namespace support only, so you should be able to use shared/public folders you have rights on but not configure them yourself (tell us if you know more software supporting this feature) == Fallback retention == The current retention period on our servers is 2 weeks, but can be temporary or permanently increased if needed. Mails flowing back to your primary server can be protected using TLS with certificate verification if you wish. Antivirus and antispam filtering are not applied to relayed mails, so we do not mess with your prefered strategy on your primary server, nevertheless basic checks (EHLO, DNS…) and RBL scoring are done to avoid accepting tons of SPAMs. ffbbe5e2f9538588a75780dab9dca76a0780bc76 215 214 2011-05-17T18:53:07Z Duck 2 /* Antivirus and Antispam */ wikitext text/x-wiki == Mail Hosting == What we can offer: * full hosting (MX1) on our servers: ** multiple email addresses which can be real mailboxes or mere redirections at another third party addresses ** based on ''milkypond.org'' (or maybe ''duckcorp.org'') domain(s) or you own domain(s) * fallback retention (MX2) on our servers or, at your choice, partner servers (currently via Hivane) == Full Hosting == === Access Methods === You can retrieve your mails, in case of a real mailbox, using: * IMAP+TLS (TCP 143) / IMAPS (TCP 993) on imap.duckcorp.org * or POP3+TLS (TCP 110) / POP3S (TCP 995) on pop.duckcorp.org * or one of the [https://webmail.duckcorp.org/ provided webmails] The IMAP protocol is recommended over POP3, as it provides many interresting features. If you want to download all your mails absolutely at home, loosing the ability to read your mail from anywhere on the planet, you can do that with IMAP too (look at your mail client settings). You can use our servers to send mails out too via smtp.duckcorp.org using: * SMTP+TLS (TCP 25) / SMTPS (TCP 465) * and SASL authentication === Antivirus and Antispam === Mails stored on our server are checked upon arrival for viruses and SPAMs. Mail redirected to a third party mailbox are not, not to mess with the strategy of the the final destination (which could arm learning greatly). Mails being viruses are suppressed automatically upon arrival. Once in a week, an extra antivirus check is done on all hosted mailboxes, to remove viruses not detected at the time it arrived (our antivirus database is updated daily), so you may see such mail disappear from your mailbox, don't fear. SPAMs are more difficult to detect, and it is an error-prone process, so we chose to use a learning software intead of using a global database. On the bright side of things, you should never loose mails and the software should be able to learn what is a SPAM from '''your''' point of view, but on the grey side you will have to teach him regulary to avoid errors. When your account is created, it acts like an empty headed body letting everything through, but after a few weeks of teaching it is able to recognise most of your habits and block a lot of annoying SPAM. To teach the system, you can: * use the [https://spamfilter.duckcorp.org/ web interface] to retrain from errors in the ''History'' page * resend SPAM to dc-spam@duckcorp.org and HAM (non-SPAM) to dc-ham@duckcorp.org *: {{warning}} PLEASE TAKE CARE to use the ''resend'' function of your mailer and never use ''forward'', which would result in '''yourself''' being considered as spam or ham You can yourself setup a few parameters in the ''Preferences'' page of the [https://spamfilter.duckcorp.org/ web interface], mostly: * how the system should train: ** TEFT (''On every new message scanned by the filter''): useful to learn very quickly especially on a new mailbox or when you've got tons of spam on your addresses, but you need to train it regulary (daily is better) or it will learn wrong (very quickly too !) ** TOE (''Only when the filter makes a mistake''): slow learning, but if you don't have time for training very often or go on long holidays without internet access this mode will give you a stable behavior ** TUM (''Only with new data or if the filter makes a mistake''): trade-off between the two previous modes, learn quite fast and not too demanding, adapts better to new SPAMs then TOE * filter sensitivity, so you can ask the system to be more or less aggressive * message Handling: * ''Quarantine the message'': mails are not delivered to your mailbox but retained by the system and you can only manage them through the [https://spamfilter.duckcorp.org/ web interface] ; if you retrain a quarantined mail as HAM, it will be freed from quarantine and delivered in your mailbox at once ; in this mode, you need to flush your quarantine once in a while * ''Tag the Subject header with'': mails are delivered with a modified title (which is a tad ugly) * ''Deliver the message normally with a X-DSPAM-Result header'': mails are delivered with a special field in your mail headers (not always visible depending on your mail client and its configuration) ; this is quite handy if you prefer SPAMs arranged in a specific folder * ''Disable DSPAM filtering'': you may switch off filtering at your own risk We strongly recommend using TEFT with daily training for a few weeks then switching to TUM. If you need to go away for a long time, switching to TOE is recommended. Using the quarantine feature is also a safe choice, as the web interface is quite easy to use. === Mail Filtering === With your favourite mail client, you can probably filter your mails in proper folders already. Nevertheless, this can be a annoying operation: * blocking you mail client for a long time if you have to process plenty of mails * downloading each mail information, and sometimes content (depending on your filters), is lenghty too, and cost much bandwidth * syncing filters accross your machines (home desktop, laptop, office machine…) is a pain in the ass * processing only when you're online prevents triggering actions in a timely manner (automatic redirect, vacation messages…), and running a machine 24/7 with a mail client polling new mails every 30s is not a solution We provide a much better way to do this using the [[wikipedia:Sieve_(mail_filtering_language)|SIEVE]] filters. Shortly, SIEVE is a language dedicated to expressing mail filters. Our server is able to process your mails according to these filters as soon as they arrive. You then don't have to care about them anymore, and may use light mail clients or webmails when you're not on your machine with your favourite software. To push your filters on the server, a dedicated protocol exists: : MANAGESIEVE (TCP 4190) on sieve.duckcorp.org Several softwares support managing SIEVE rules: * Icedove/Thunderbird using the SIEVE extension (in xul-ext-sieve Debian package) provides a rules editor * Horde (Ingo) provides an easy to use web interface * Squirrelmail with the Avelsieve extension provides an easy to use web interface * Roundcube with an extension provides an easy to use web interface * sieve-connect provides a CLI to upload/download/activate your rules files (tell us if you know more software supporting this feature) You can read more info about SIEVE here: * supported SIEVE features on our server: http://pigeonhole.dovecot.org/ * http://www.fastmail.fm/docs/sieve/ * http://sieve.info/ === Shared/Public Folders === You may need to share mails or messages with friends or people you do stuff with (in a project or association). Depending on your needs, two solutions are possible: * share some of your own private folders, thus called ''shared folders'' * manage a special folder hierarchy, called ''public folders'' (even if they may not be accessible to everyone) Through IMAP, or our webmails internally using IMAP, it is possible to partition the folder hierarchy into ''namespaces''. Traditionally you are using the root namespace for your private folders. Additionnal namespaces can be created and will appear among your own folders or separate, depending on your mail client's choice of representation. To avoid name clashes, we decided to prefix all additionnal namespace names with a '''#'''. Since 2011-05-14, the following extra namespaces are created and reserved: * #Shared, containing all folders other users decided to share with you * #MilkyPond, containing public MP/DC information mailboxes you may subscribe at will Using IMAP, it is possible to setup rights (read only, write allowed…) to your own folders in order to share them with other users, or group of users. Public folders are owned by noone, and must be created by DC administrators ; if you need one, send us a request and we may be able to create it and delegate administration to your care (namespace name is subject to approval). Once created, public folders can be administered like shared folders. Client mail softwares support: * Horde: support namespaces, shared folders configurable via ''Options->Share Folders'' menu but no ACLs for public folders * Icedove/Thunderbird: support namespaces, shared and public folders configurable via folder selection and ''Tools->Imap-ACL'' menu action Most other softwares have namespace support only, so you should be able to use shared/public folders you have rights on but not configure them yourself (tell us if you know more software supporting this feature) == Fallback retention == The current retention period on our servers is 2 weeks, but can be temporary or permanently increased if needed. Mails flowing back to your primary server can be protected using TLS with certificate verification if you wish. Antivirus and antispam filtering are not applied to relayed mails, so we do not mess with your prefered strategy on your primary server, nevertheless basic checks (EHLO, DNS…) and RBL scoring are done to avoid accepting tons of SPAMs. 5641f6091e7eaf98a4de1a9d699c8f21238aef80 216 215 2011-05-17T18:54:37Z Duck 2 /* Antivirus and Antispam */ wikitext text/x-wiki == Mail Hosting == What we can offer: * full hosting (MX1) on our servers: ** multiple email addresses which can be real mailboxes or mere redirections at another third party addresses ** based on ''milkypond.org'' (or maybe ''duckcorp.org'') domain(s) or you own domain(s) * fallback retention (MX2) on our servers or, at your choice, partner servers (currently via Hivane) == Full Hosting == === Access Methods === You can retrieve your mails, in case of a real mailbox, using: * IMAP+TLS (TCP 143) / IMAPS (TCP 993) on imap.duckcorp.org * or POP3+TLS (TCP 110) / POP3S (TCP 995) on pop.duckcorp.org * or one of the [https://webmail.duckcorp.org/ provided webmails] The IMAP protocol is recommended over POP3, as it provides many interresting features. If you want to download all your mails absolutely at home, loosing the ability to read your mail from anywhere on the planet, you can do that with IMAP too (look at your mail client settings). You can use our servers to send mails out too via smtp.duckcorp.org using: * SMTP+TLS (TCP 25) / SMTPS (TCP 465) * and SASL authentication === Antivirus and Antispam === Mails stored on our server are checked upon arrival for viruses and SPAMs. Mail redirected to a third party mailbox are not, not to mess with the strategy of the the final destination (which could arm learning greatly). Mails being viruses are suppressed automatically upon arrival. Once in a week, an extra antivirus check is done on all hosted mailboxes, to remove viruses not detected at the time it arrived (our antivirus database is updated daily), so you may see such mail disappear from your mailbox, don't fear. SPAMs are more difficult to detect, and it is an error-prone process, so we chose to use a learning software intead of using a global database. On the bright side of things, you should never loose mails and the software should be able to learn what is a SPAM from '''your''' point of view, but on the grey side you will have to teach him regulary to avoid errors. When your account is created, it acts like an empty headed body letting everything through, but after a few weeks of teaching it is able to recognise most of your habits and block a lot of annoying SPAM. To teach the system, you can: * use the [https://spamfilter.duckcorp.org/ web interface] to retrain from errors in the ''History'' page * resend SPAM to dc-spam@duckcorp.org and HAM (non-SPAM) to dc-ham@duckcorp.org *: {{warning}} PLEASE TAKE CARE to use the ''resend'' function of your mailer and never use ''forward'', which would result in '''yourself''' being considered as spam or ham You can yourself setup a few parameters in the ''Preferences'' page of the [https://spamfilter.duckcorp.org/ web interface], mostly: * how the system should train: ** TEFT (''On every new message scanned by the filter''): useful to learn very quickly especially on a new mailbox or when you've got tons of spam on your addresses, but you need to train it regulary (daily is better) or it will learn wrong (very quickly too !) ** TOE (''Only when the filter makes a mistake''): slow learning, but if you don't have time for training very often or go on long holidays without internet access this mode will give you a stable behavior ** TUM (''Only with new data or if the filter makes a mistake''): trade-off between the two previous modes, learn quite fast and not too demanding, adapts better to new SPAMs then TOE * filter sensitivity, so you can ask the system to be more or less aggressive * message handling: * ''Quarantine the message'': mails are not delivered to your mailbox but retained by the system and you can only manage them through the [https://spamfilter.duckcorp.org/ web interface] ; if you retrain a quarantined mail as HAM, it will be freed from quarantine and delivered in your mailbox at once ; in this mode, you need to flush your quarantine once in a while * ''Tag the Subject header with'': mails are delivered with a modified title (which is a tad ugly) * ''Deliver the message normally with a X-DSPAM-Result header'': mails are delivered with a special field in your mail headers (not always visible depending on your mail client and its configuration) ; this is quite handy if you prefer SPAMs arranged in a specific folder * ''Disable DSPAM filtering'': you may switch off filtering at your own risk We strongly recommend using TEFT with daily training for a few weeks then switching to TUM. If you need to go away for a long time, switching to TOE is recommended. Using the quarantine feature is also a safe choice, as the web interface is quite easy to use. === Mail Filtering === With your favourite mail client, you can probably filter your mails in proper folders already. Nevertheless, this can be a annoying operation: * blocking you mail client for a long time if you have to process plenty of mails * downloading each mail information, and sometimes content (depending on your filters), is lenghty too, and cost much bandwidth * syncing filters accross your machines (home desktop, laptop, office machine…) is a pain in the ass * processing only when you're online prevents triggering actions in a timely manner (automatic redirect, vacation messages…), and running a machine 24/7 with a mail client polling new mails every 30s is not a solution We provide a much better way to do this using the [[wikipedia:Sieve_(mail_filtering_language)|SIEVE]] filters. Shortly, SIEVE is a language dedicated to expressing mail filters. Our server is able to process your mails according to these filters as soon as they arrive. You then don't have to care about them anymore, and may use light mail clients or webmails when you're not on your machine with your favourite software. To push your filters on the server, a dedicated protocol exists: : MANAGESIEVE (TCP 4190) on sieve.duckcorp.org Several softwares support managing SIEVE rules: * Icedove/Thunderbird using the SIEVE extension (in xul-ext-sieve Debian package) provides a rules editor * Horde (Ingo) provides an easy to use web interface * Squirrelmail with the Avelsieve extension provides an easy to use web interface * Roundcube with an extension provides an easy to use web interface * sieve-connect provides a CLI to upload/download/activate your rules files (tell us if you know more software supporting this feature) You can read more info about SIEVE here: * supported SIEVE features on our server: http://pigeonhole.dovecot.org/ * http://www.fastmail.fm/docs/sieve/ * http://sieve.info/ === Shared/Public Folders === You may need to share mails or messages with friends or people you do stuff with (in a project or association). Depending on your needs, two solutions are possible: * share some of your own private folders, thus called ''shared folders'' * manage a special folder hierarchy, called ''public folders'' (even if they may not be accessible to everyone) Through IMAP, or our webmails internally using IMAP, it is possible to partition the folder hierarchy into ''namespaces''. Traditionally you are using the root namespace for your private folders. Additionnal namespaces can be created and will appear among your own folders or separate, depending on your mail client's choice of representation. To avoid name clashes, we decided to prefix all additionnal namespace names with a '''#'''. Since 2011-05-14, the following extra namespaces are created and reserved: * #Shared, containing all folders other users decided to share with you * #MilkyPond, containing public MP/DC information mailboxes you may subscribe at will Using IMAP, it is possible to setup rights (read only, write allowed…) to your own folders in order to share them with other users, or group of users. Public folders are owned by noone, and must be created by DC administrators ; if you need one, send us a request and we may be able to create it and delegate administration to your care (namespace name is subject to approval). Once created, public folders can be administered like shared folders. Client mail softwares support: * Horde: support namespaces, shared folders configurable via ''Options->Share Folders'' menu but no ACLs for public folders * Icedove/Thunderbird: support namespaces, shared and public folders configurable via folder selection and ''Tools->Imap-ACL'' menu action Most other softwares have namespace support only, so you should be able to use shared/public folders you have rights on but not configure them yourself (tell us if you know more software supporting this feature) == Fallback retention == The current retention period on our servers is 2 weeks, but can be temporary or permanently increased if needed. Mails flowing back to your primary server can be protected using TLS with certificate verification if you wish. Antivirus and antispam filtering are not applied to relayed mails, so we do not mess with your prefered strategy on your primary server, nevertheless basic checks (EHLO, DNS…) and RBL scoring are done to avoid accepting tons of SPAMs. b0b471ab5dc88171d0c2e660b0fa119b278bce10 217 216 2011-05-17T18:59:03Z Duck 2 /* Antivirus and Antispam */ wikitext text/x-wiki == Mail Hosting == What we can offer: * full hosting (MX1) on our servers: ** multiple email addresses which can be real mailboxes or mere redirections at another third party addresses ** based on ''milkypond.org'' (or maybe ''duckcorp.org'') domain(s) or you own domain(s) * fallback retention (MX2) on our servers or, at your choice, partner servers (currently via Hivane) == Full Hosting == === Access Methods === You can retrieve your mails, in case of a real mailbox, using: * IMAP+TLS (TCP 143) / IMAPS (TCP 993) on imap.duckcorp.org * or POP3+TLS (TCP 110) / POP3S (TCP 995) on pop.duckcorp.org * or one of the [https://webmail.duckcorp.org/ provided webmails] The IMAP protocol is recommended over POP3, as it provides many interresting features. If you want to download all your mails absolutely at home, loosing the ability to read your mail from anywhere on the planet, you can do that with IMAP too (look at your mail client settings). You can use our servers to send mails out too via smtp.duckcorp.org using: * SMTP+TLS (TCP 25) / SMTPS (TCP 465) * and SASL authentication === Antivirus and Antispam === Mails stored on our server are checked upon arrival for viruses and SPAMs. Mail redirected to a third party mailbox are not, not to mess with the strategy of the the final destination (which could arm learning greatly). Mails being viruses are suppressed automatically upon arrival. Once in a week, an extra antivirus check is done on all hosted mailboxes, to remove viruses not detected at the time it arrived (our antivirus database is updated daily), so you may see such mail disappear from your mailbox, don't fear. SPAMs are more difficult to detect, and it is an error-prone process, so we chose to use a learning software intead of using a global database. On the bright side of things, you would never loose mails and the software should be able to learn what is a SPAM from '''your''' point of view (which has proved to differ slightly between our users), but on the grey side you will have to teach him regulary to avoid errors. When your account is created, it acts like an empty headed body letting everything through, but after a few weeks of teaching it is able to recognise most of your habits and block a lot of annoying SPAM. To teach the system, you can: * use the [https://spamfilter.duckcorp.org/ web interface] to retrain from errors in the ''History'' page * resend SPAM to dc-spam@duckcorp.org and HAM (non-SPAM) to dc-ham@duckcorp.org *: {{warning}} PLEASE TAKE CARE to use the ''resend'' function of your mailer and never use ''forward'', which would result in '''yourself''' being considered as spam or ham You can yourself setup a few parameters in the ''Preferences'' page of the [https://spamfilter.duckcorp.org/ web interface], mostly: * how the system should train: ** TEFT (''On every new message scanned by the filter''): useful to learn very quickly especially on a new mailbox or when you've got tons of spam on your addresses, but you need to train it regulary (daily is better) or it will learn wrong (very quickly too !) ** TOE (''Only when the filter makes a mistake''): slow learning, but if you don't have time for training very often or go on long holidays without internet access this mode will give you a stable behavior ** TUM (''Only with new data or if the filter makes a mistake''): trade-off between the two previous modes, learn quite fast and not too demanding, adapts better to new SPAMs then TOE * filter sensitivity, so you can ask the system to be more or less aggressive * message handling: * ''Quarantine the message'': mails are not delivered to your mailbox but retained by the system and you can only manage them through the [https://spamfilter.duckcorp.org/ web interface] ; if you retrain a quarantined mail as HAM, it will be freed from quarantine and delivered in your mailbox at once ; in this mode, you need to flush your quarantine once in a while * ''Tag the Subject header with'': mails are delivered with a modified title (which is a tad ugly) * ''Deliver the message normally with a X-DSPAM-Result header'': mails are delivered with a special field in your mail headers (not always visible depending on your mail client and its configuration) ; this is quite handy if you prefer SPAMs arranged in a specific folder * ''Disable DSPAM filtering'': you may switch off filtering at your own risk We strongly recommend using TEFT with daily training for a few weeks then switching to TUM. If you need to go away for a long time, switching to TOE is recommended. Using the quarantine feature is also a safe choice, as the web interface is quite easy to use. === Mail Filtering === With your favourite mail client, you can probably filter your mails in proper folders already. Nevertheless, this can be a annoying operation: * blocking you mail client for a long time if you have to process plenty of mails * downloading each mail information, and sometimes content (depending on your filters), is lenghty too, and cost much bandwidth * syncing filters accross your machines (home desktop, laptop, office machine…) is a pain in the ass * processing only when you're online prevents triggering actions in a timely manner (automatic redirect, vacation messages…), and running a machine 24/7 with a mail client polling new mails every 30s is not a solution We provide a much better way to do this using the [[wikipedia:Sieve_(mail_filtering_language)|SIEVE]] filters. Shortly, SIEVE is a language dedicated to expressing mail filters. Our server is able to process your mails according to these filters as soon as they arrive. You then don't have to care about them anymore, and may use light mail clients or webmails when you're not on your machine with your favourite software. To push your filters on the server, a dedicated protocol exists: : MANAGESIEVE (TCP 4190) on sieve.duckcorp.org Several softwares support managing SIEVE rules: * Icedove/Thunderbird using the SIEVE extension (in xul-ext-sieve Debian package) provides a rules editor * Horde (Ingo) provides an easy to use web interface * Squirrelmail with the Avelsieve extension provides an easy to use web interface * Roundcube with an extension provides an easy to use web interface * sieve-connect provides a CLI to upload/download/activate your rules files (tell us if you know more software supporting this feature) You can read more info about SIEVE here: * supported SIEVE features on our server: http://pigeonhole.dovecot.org/ * http://www.fastmail.fm/docs/sieve/ * http://sieve.info/ === Shared/Public Folders === You may need to share mails or messages with friends or people you do stuff with (in a project or association). Depending on your needs, two solutions are possible: * share some of your own private folders, thus called ''shared folders'' * manage a special folder hierarchy, called ''public folders'' (even if they may not be accessible to everyone) Through IMAP, or our webmails internally using IMAP, it is possible to partition the folder hierarchy into ''namespaces''. Traditionally you are using the root namespace for your private folders. Additionnal namespaces can be created and will appear among your own folders or separate, depending on your mail client's choice of representation. To avoid name clashes, we decided to prefix all additionnal namespace names with a '''#'''. Since 2011-05-14, the following extra namespaces are created and reserved: * #Shared, containing all folders other users decided to share with you * #MilkyPond, containing public MP/DC information mailboxes you may subscribe at will Using IMAP, it is possible to setup rights (read only, write allowed…) to your own folders in order to share them with other users, or group of users. Public folders are owned by noone, and must be created by DC administrators ; if you need one, send us a request and we may be able to create it and delegate administration to your care (namespace name is subject to approval). Once created, public folders can be administered like shared folders. Client mail softwares support: * Horde: support namespaces, shared folders configurable via ''Options->Share Folders'' menu but no ACLs for public folders * Icedove/Thunderbird: support namespaces, shared and public folders configurable via folder selection and ''Tools->Imap-ACL'' menu action Most other softwares have namespace support only, so you should be able to use shared/public folders you have rights on but not configure them yourself (tell us if you know more software supporting this feature) == Fallback retention == The current retention period on our servers is 2 weeks, but can be temporary or permanently increased if needed. Mails flowing back to your primary server can be protected using TLS with certificate verification if you wish. Antivirus and antispam filtering are not applied to relayed mails, so we do not mess with your prefered strategy on your primary server, nevertheless basic checks (EHLO, DNS…) and RBL scoring are done to avoid accepting tons of SPAMs. ea5e9fe86801551bff74aa7fbc67690f84120e84 218 217 2011-05-17T18:59:26Z Duck 2 /* Antivirus and Antispam */ wikitext text/x-wiki == Mail Hosting == What we can offer: * full hosting (MX1) on our servers: ** multiple email addresses which can be real mailboxes or mere redirections at another third party addresses ** based on ''milkypond.org'' (or maybe ''duckcorp.org'') domain(s) or you own domain(s) * fallback retention (MX2) on our servers or, at your choice, partner servers (currently via Hivane) == Full Hosting == === Access Methods === You can retrieve your mails, in case of a real mailbox, using: * IMAP+TLS (TCP 143) / IMAPS (TCP 993) on imap.duckcorp.org * or POP3+TLS (TCP 110) / POP3S (TCP 995) on pop.duckcorp.org * or one of the [https://webmail.duckcorp.org/ provided webmails] The IMAP protocol is recommended over POP3, as it provides many interresting features. If you want to download all your mails absolutely at home, loosing the ability to read your mail from anywhere on the planet, you can do that with IMAP too (look at your mail client settings). You can use our servers to send mails out too via smtp.duckcorp.org using: * SMTP+TLS (TCP 25) / SMTPS (TCP 465) * and SASL authentication === Antivirus and Antispam === Mails stored on our server are checked upon arrival for viruses and SPAMs. Mail redirected to a third party mailbox are not, not to mess with the strategy of the the final destination (which could arm learning greatly). Mails being viruses are suppressed automatically upon arrival. Once in a week, an extra antivirus check is done on all hosted mailboxes, to remove viruses not detected at the time it arrived (our antivirus database is updated daily), so you may see such mail disappear from your mailbox, don't fear. SPAMs are more difficult to detect, and it is an error-prone process, so we chose to use a learning software intead of using a global database. On the bright side of things, you would never loose mails and the software should be able to learn what is a SPAM from '''your''' point of view (which has proved to differ slightly between our users), but on the grey side you will have to teach him regulary to avoid errors. When your account is created, it acts like an empty headed body letting everything through, but after a few weeks of teaching it is able to recognise most of your habits and block a lot of annoying SPAM. To teach the system, you can: * use the [https://spamfilter.duckcorp.org/ web interface] to retrain from errors in the ''History'' page * resend SPAM to dc-spam@duckcorp.org and HAM (non-SPAM) to dc-ham@duckcorp.org *: {{warning}} PLEASE TAKE CARE to use the ''resend'' function of your mailer and never use ''forward'', which would result in '''yourself''' being considered as spam or ham You can yourself setup a few parameters in the ''Preferences'' page of the [https://spamfilter.duckcorp.org/ web interface], mostly: * how the system should train: ** TEFT (''On every new message scanned by the filter''): useful to learn very quickly especially on a new mailbox or when you've got tons of spam on your addresses, but you need to train it regulary (daily is better) or it will learn wrong (very quickly too !) ** TOE (''Only when the filter makes a mistake''): slow learning, but if you don't have time for training very often or go on long holidays without internet access this mode will give you a stable behavior ** TUM (''Only with new data or if the filter makes a mistake''): trade-off between the two previous modes, learn quite fast and not too demanding, adapts better to new SPAMs then TOE * filter sensitivity, so you can ask the system to be more or less aggressive * message handling: ** ''Quarantine the message'': mails are not delivered to your mailbox but retained by the system and you can only manage them through the [https://spamfilter.duckcorp.org/ web interface] ; if you retrain a quarantined mail as HAM, it will be freed from quarantine and delivered in your mailbox at once ; in this mode, you need to flush your quarantine once in a while ** ''Tag the Subject header with'': mails are delivered with a modified title (which is a tad ugly) ** ''Deliver the message normally with a X-DSPAM-Result header'': mails are delivered with a special field in your mail headers (not always visible depending on your mail client and its configuration) ; this is quite handy if you prefer SPAMs arranged in a specific folder * ''Disable DSPAM filtering'': you may switch off filtering at your own risk We strongly recommend using TEFT with daily training for a few weeks then switching to TUM. If you need to go away for a long time, switching to TOE is recommended. Using the quarantine feature is also a safe choice, as the web interface is quite easy to use. === Mail Filtering === With your favourite mail client, you can probably filter your mails in proper folders already. Nevertheless, this can be a annoying operation: * blocking you mail client for a long time if you have to process plenty of mails * downloading each mail information, and sometimes content (depending on your filters), is lenghty too, and cost much bandwidth * syncing filters accross your machines (home desktop, laptop, office machine…) is a pain in the ass * processing only when you're online prevents triggering actions in a timely manner (automatic redirect, vacation messages…), and running a machine 24/7 with a mail client polling new mails every 30s is not a solution We provide a much better way to do this using the [[wikipedia:Sieve_(mail_filtering_language)|SIEVE]] filters. Shortly, SIEVE is a language dedicated to expressing mail filters. Our server is able to process your mails according to these filters as soon as they arrive. You then don't have to care about them anymore, and may use light mail clients or webmails when you're not on your machine with your favourite software. To push your filters on the server, a dedicated protocol exists: : MANAGESIEVE (TCP 4190) on sieve.duckcorp.org Several softwares support managing SIEVE rules: * Icedove/Thunderbird using the SIEVE extension (in xul-ext-sieve Debian package) provides a rules editor * Horde (Ingo) provides an easy to use web interface * Squirrelmail with the Avelsieve extension provides an easy to use web interface * Roundcube with an extension provides an easy to use web interface * sieve-connect provides a CLI to upload/download/activate your rules files (tell us if you know more software supporting this feature) You can read more info about SIEVE here: * supported SIEVE features on our server: http://pigeonhole.dovecot.org/ * http://www.fastmail.fm/docs/sieve/ * http://sieve.info/ === Shared/Public Folders === You may need to share mails or messages with friends or people you do stuff with (in a project or association). Depending on your needs, two solutions are possible: * share some of your own private folders, thus called ''shared folders'' * manage a special folder hierarchy, called ''public folders'' (even if they may not be accessible to everyone) Through IMAP, or our webmails internally using IMAP, it is possible to partition the folder hierarchy into ''namespaces''. Traditionally you are using the root namespace for your private folders. Additionnal namespaces can be created and will appear among your own folders or separate, depending on your mail client's choice of representation. To avoid name clashes, we decided to prefix all additionnal namespace names with a '''#'''. Since 2011-05-14, the following extra namespaces are created and reserved: * #Shared, containing all folders other users decided to share with you * #MilkyPond, containing public MP/DC information mailboxes you may subscribe at will Using IMAP, it is possible to setup rights (read only, write allowed…) to your own folders in order to share them with other users, or group of users. Public folders are owned by noone, and must be created by DC administrators ; if you need one, send us a request and we may be able to create it and delegate administration to your care (namespace name is subject to approval). Once created, public folders can be administered like shared folders. Client mail softwares support: * Horde: support namespaces, shared folders configurable via ''Options->Share Folders'' menu but no ACLs for public folders * Icedove/Thunderbird: support namespaces, shared and public folders configurable via folder selection and ''Tools->Imap-ACL'' menu action Most other softwares have namespace support only, so you should be able to use shared/public folders you have rights on but not configure them yourself (tell us if you know more software supporting this feature) == Fallback retention == The current retention period on our servers is 2 weeks, but can be temporary or permanently increased if needed. Mails flowing back to your primary server can be protected using TLS with certificate verification if you wish. Antivirus and antispam filtering are not applied to relayed mails, so we do not mess with your prefered strategy on your primary server, nevertheless basic checks (EHLO, DNS…) and RBL scoring are done to avoid accepting tons of SPAMs. 94e1602f49852eee2ebc90617a5354b41d95792d 219 218 2011-05-17T18:59:57Z Duck 2 /* Antivirus and Antispam */ wikitext text/x-wiki == Mail Hosting == What we can offer: * full hosting (MX1) on our servers: ** multiple email addresses which can be real mailboxes or mere redirections at another third party addresses ** based on ''milkypond.org'' (or maybe ''duckcorp.org'') domain(s) or you own domain(s) * fallback retention (MX2) on our servers or, at your choice, partner servers (currently via Hivane) == Full Hosting == === Access Methods === You can retrieve your mails, in case of a real mailbox, using: * IMAP+TLS (TCP 143) / IMAPS (TCP 993) on imap.duckcorp.org * or POP3+TLS (TCP 110) / POP3S (TCP 995) on pop.duckcorp.org * or one of the [https://webmail.duckcorp.org/ provided webmails] The IMAP protocol is recommended over POP3, as it provides many interresting features. If you want to download all your mails absolutely at home, loosing the ability to read your mail from anywhere on the planet, you can do that with IMAP too (look at your mail client settings). You can use our servers to send mails out too via smtp.duckcorp.org using: * SMTP+TLS (TCP 25) / SMTPS (TCP 465) * and SASL authentication === Antivirus and Antispam === Mails stored on our server are checked upon arrival for viruses and SPAMs. Mail redirected to a third party mailbox are not, not to mess with the strategy of the the final destination (which could arm learning greatly). Mails being viruses are suppressed automatically upon arrival. Once in a week, an extra antivirus check is done on all hosted mailboxes, to remove viruses not detected at the time it arrived (our antivirus database is updated daily), so you may see such mail disappear from your mailbox, don't fear. SPAMs are more difficult to detect, and it is an error-prone process, so we chose to use a learning software intead of using a global database. On the bright side of things, you would never loose mails and the software should be able to learn what is a SPAM from '''your''' point of view (which has proved to differ slightly between our users), but on the grey side you will have to teach him regulary to avoid errors. When your account is created, it acts like an empty headed body letting everything through, but after a few weeks of teaching it is able to recognise most of your habits and block a lot of annoying SPAM. To teach the system, you can: * use the [https://spamfilter.duckcorp.org/ web interface] to retrain from errors in the ''History'' page * resend SPAM to dc-spam@duckcorp.org and HAM (non-SPAM) to dc-ham@duckcorp.org *: {{warning}} PLEASE TAKE CARE to use the ''resend'' function of your mailer and never use ''forward'', which would result in '''yourself''' being considered as spam or ham You can yourself setup a few parameters in the ''Preferences'' page of the [https://spamfilter.duckcorp.org/ web interface], mostly: * how the system should train: ** TEFT (''On every new message scanned by the filter''): useful to learn very quickly especially on a new mailbox or when you've got tons of spam on your addresses, but you need to train it regulary (daily is better) or it will learn wrong (very quickly too !) ** TOE (''Only when the filter makes a mistake''): slow learning, but if you don't have time for training very often or go on long holidays without internet access this mode will give you a stable behavior ** TUM (''Only with new data or if the filter makes a mistake''): trade-off between the two previous modes, learn quite fast and not too demanding, adapts better to new SPAMs then TOE * filter sensitivity: you can ask the system to be more or less aggressive * message handling: ** ''Quarantine the message'': mails are not delivered to your mailbox but retained by the system and you can only manage them through the [https://spamfilter.duckcorp.org/ web interface] ; if you retrain a quarantined mail as HAM, it will be freed from quarantine and delivered in your mailbox at once ; in this mode, you need to flush your quarantine once in a while ** ''Tag the Subject header with'': mails are delivered with a modified title (which is a tad ugly) ** ''Deliver the message normally with a X-DSPAM-Result header'': mails are delivered with a special field in your mail headers (not always visible depending on your mail client and its configuration) ; this is quite handy if you prefer SPAMs arranged in a specific folder * ''Disable DSPAM filtering'': you may switch off filtering at your own risk We strongly recommend using TEFT with daily training for a few weeks then switching to TUM. If you need to go away for a long time, switching to TOE is recommended. Using the quarantine feature is also a safe choice, as the web interface is quite easy to use. === Mail Filtering === With your favourite mail client, you can probably filter your mails in proper folders already. Nevertheless, this can be a annoying operation: * blocking you mail client for a long time if you have to process plenty of mails * downloading each mail information, and sometimes content (depending on your filters), is lenghty too, and cost much bandwidth * syncing filters accross your machines (home desktop, laptop, office machine…) is a pain in the ass * processing only when you're online prevents triggering actions in a timely manner (automatic redirect, vacation messages…), and running a machine 24/7 with a mail client polling new mails every 30s is not a solution We provide a much better way to do this using the [[wikipedia:Sieve_(mail_filtering_language)|SIEVE]] filters. Shortly, SIEVE is a language dedicated to expressing mail filters. Our server is able to process your mails according to these filters as soon as they arrive. You then don't have to care about them anymore, and may use light mail clients or webmails when you're not on your machine with your favourite software. To push your filters on the server, a dedicated protocol exists: : MANAGESIEVE (TCP 4190) on sieve.duckcorp.org Several softwares support managing SIEVE rules: * Icedove/Thunderbird using the SIEVE extension (in xul-ext-sieve Debian package) provides a rules editor * Horde (Ingo) provides an easy to use web interface * Squirrelmail with the Avelsieve extension provides an easy to use web interface * Roundcube with an extension provides an easy to use web interface * sieve-connect provides a CLI to upload/download/activate your rules files (tell us if you know more software supporting this feature) You can read more info about SIEVE here: * supported SIEVE features on our server: http://pigeonhole.dovecot.org/ * http://www.fastmail.fm/docs/sieve/ * http://sieve.info/ === Shared/Public Folders === You may need to share mails or messages with friends or people you do stuff with (in a project or association). Depending on your needs, two solutions are possible: * share some of your own private folders, thus called ''shared folders'' * manage a special folder hierarchy, called ''public folders'' (even if they may not be accessible to everyone) Through IMAP, or our webmails internally using IMAP, it is possible to partition the folder hierarchy into ''namespaces''. Traditionally you are using the root namespace for your private folders. Additionnal namespaces can be created and will appear among your own folders or separate, depending on your mail client's choice of representation. To avoid name clashes, we decided to prefix all additionnal namespace names with a '''#'''. Since 2011-05-14, the following extra namespaces are created and reserved: * #Shared, containing all folders other users decided to share with you * #MilkyPond, containing public MP/DC information mailboxes you may subscribe at will Using IMAP, it is possible to setup rights (read only, write allowed…) to your own folders in order to share them with other users, or group of users. Public folders are owned by noone, and must be created by DC administrators ; if you need one, send us a request and we may be able to create it and delegate administration to your care (namespace name is subject to approval). Once created, public folders can be administered like shared folders. Client mail softwares support: * Horde: support namespaces, shared folders configurable via ''Options->Share Folders'' menu but no ACLs for public folders * Icedove/Thunderbird: support namespaces, shared and public folders configurable via folder selection and ''Tools->Imap-ACL'' menu action Most other softwares have namespace support only, so you should be able to use shared/public folders you have rights on but not configure them yourself (tell us if you know more software supporting this feature) == Fallback retention == The current retention period on our servers is 2 weeks, but can be temporary or permanently increased if needed. Mails flowing back to your primary server can be protected using TLS with certificate verification if you wish. Antivirus and antispam filtering are not applied to relayed mails, so we do not mess with your prefered strategy on your primary server, nevertheless basic checks (EHLO, DNS…) and RBL scoring are done to avoid accepting tons of SPAMs. ec93d309b6558d4b06f7506bccf5d562767ad980 220 219 2011-05-17T19:03:14Z Duck 2 /* Mail Hosting */ wikitext text/x-wiki == Mail Hosting == What we can offer: * full hosting (MX1) on our servers: ** multiple email addresses which can be real mailboxes or mere redirections towards third party addresses ** based on ''milkypond.org'' (or maybe ''duckcorp.org'') domain(s) or you own domain(s) * fallback retention (MX2) on our servers or, at your choice, partner servers (currently via Hivane) == Full Hosting == === Access Methods === You can retrieve your mails, in case of a real mailbox, using: * IMAP+TLS (TCP 143) / IMAPS (TCP 993) on imap.duckcorp.org * or POP3+TLS (TCP 110) / POP3S (TCP 995) on pop.duckcorp.org * or one of the [https://webmail.duckcorp.org/ provided webmails] The IMAP protocol is recommended over POP3, as it provides many interresting features. If you want to download all your mails absolutely at home, loosing the ability to read your mail from anywhere on the planet, you can do that with IMAP too (look at your mail client settings). You can use our servers to send mails out too via smtp.duckcorp.org using: * SMTP+TLS (TCP 25) / SMTPS (TCP 465) * and SASL authentication === Antivirus and Antispam === Mails stored on our server are checked upon arrival for viruses and SPAMs. Mail redirected to a third party mailbox are not, not to mess with the strategy of the the final destination (which could arm learning greatly). Mails being viruses are suppressed automatically upon arrival. Once in a week, an extra antivirus check is done on all hosted mailboxes, to remove viruses not detected at the time it arrived (our antivirus database is updated daily), so you may see such mail disappear from your mailbox, don't fear. SPAMs are more difficult to detect, and it is an error-prone process, so we chose to use a learning software intead of using a global database. On the bright side of things, you would never loose mails and the software should be able to learn what is a SPAM from '''your''' point of view (which has proved to differ slightly between our users), but on the grey side you will have to teach him regulary to avoid errors. When your account is created, it acts like an empty headed body letting everything through, but after a few weeks of teaching it is able to recognise most of your habits and block a lot of annoying SPAM. To teach the system, you can: * use the [https://spamfilter.duckcorp.org/ web interface] to retrain from errors in the ''History'' page * resend SPAM to dc-spam@duckcorp.org and HAM (non-SPAM) to dc-ham@duckcorp.org *: {{warning}} PLEASE TAKE CARE to use the ''resend'' function of your mailer and never use ''forward'', which would result in '''yourself''' being considered as spam or ham You can yourself setup a few parameters in the ''Preferences'' page of the [https://spamfilter.duckcorp.org/ web interface], mostly: * how the system should train: ** TEFT (''On every new message scanned by the filter''): useful to learn very quickly especially on a new mailbox or when you've got tons of spam on your addresses, but you need to train it regulary (daily is better) or it will learn wrong (very quickly too !) ** TOE (''Only when the filter makes a mistake''): slow learning, but if you don't have time for training very often or go on long holidays without internet access this mode will give you a stable behavior ** TUM (''Only with new data or if the filter makes a mistake''): trade-off between the two previous modes, learn quite fast and not too demanding, adapts better to new SPAMs then TOE * filter sensitivity: you can ask the system to be more or less aggressive * message handling: ** ''Quarantine the message'': mails are not delivered to your mailbox but retained by the system and you can only manage them through the [https://spamfilter.duckcorp.org/ web interface] ; if you retrain a quarantined mail as HAM, it will be freed from quarantine and delivered in your mailbox at once ; in this mode, you need to flush your quarantine once in a while ** ''Tag the Subject header with'': mails are delivered with a modified title (which is a tad ugly) ** ''Deliver the message normally with a X-DSPAM-Result header'': mails are delivered with a special field in your mail headers (not always visible depending on your mail client and its configuration) ; this is quite handy if you prefer SPAMs arranged in a specific folder * ''Disable DSPAM filtering'': you may switch off filtering at your own risk We strongly recommend using TEFT with daily training for a few weeks then switching to TUM. If you need to go away for a long time, switching to TOE is recommended. Using the quarantine feature is also a safe choice, as the web interface is quite easy to use. === Mail Filtering === With your favourite mail client, you can probably filter your mails in proper folders already. Nevertheless, this can be a annoying operation: * blocking you mail client for a long time if you have to process plenty of mails * downloading each mail information, and sometimes content (depending on your filters), is lenghty too, and cost much bandwidth * syncing filters accross your machines (home desktop, laptop, office machine…) is a pain in the ass * processing only when you're online prevents triggering actions in a timely manner (automatic redirect, vacation messages…), and running a machine 24/7 with a mail client polling new mails every 30s is not a solution We provide a much better way to do this using the [[wikipedia:Sieve_(mail_filtering_language)|SIEVE]] filters. Shortly, SIEVE is a language dedicated to expressing mail filters. Our server is able to process your mails according to these filters as soon as they arrive. You then don't have to care about them anymore, and may use light mail clients or webmails when you're not on your machine with your favourite software. To push your filters on the server, a dedicated protocol exists: : MANAGESIEVE (TCP 4190) on sieve.duckcorp.org Several softwares support managing SIEVE rules: * Icedove/Thunderbird using the SIEVE extension (in xul-ext-sieve Debian package) provides a rules editor * Horde (Ingo) provides an easy to use web interface * Squirrelmail with the Avelsieve extension provides an easy to use web interface * Roundcube with an extension provides an easy to use web interface * sieve-connect provides a CLI to upload/download/activate your rules files (tell us if you know more software supporting this feature) You can read more info about SIEVE here: * supported SIEVE features on our server: http://pigeonhole.dovecot.org/ * http://www.fastmail.fm/docs/sieve/ * http://sieve.info/ === Shared/Public Folders === You may need to share mails or messages with friends or people you do stuff with (in a project or association). Depending on your needs, two solutions are possible: * share some of your own private folders, thus called ''shared folders'' * manage a special folder hierarchy, called ''public folders'' (even if they may not be accessible to everyone) Through IMAP, or our webmails internally using IMAP, it is possible to partition the folder hierarchy into ''namespaces''. Traditionally you are using the root namespace for your private folders. Additionnal namespaces can be created and will appear among your own folders or separate, depending on your mail client's choice of representation. To avoid name clashes, we decided to prefix all additionnal namespace names with a '''#'''. Since 2011-05-14, the following extra namespaces are created and reserved: * #Shared, containing all folders other users decided to share with you * #MilkyPond, containing public MP/DC information mailboxes you may subscribe at will Using IMAP, it is possible to setup rights (read only, write allowed…) to your own folders in order to share them with other users, or group of users. Public folders are owned by noone, and must be created by DC administrators ; if you need one, send us a request and we may be able to create it and delegate administration to your care (namespace name is subject to approval). Once created, public folders can be administered like shared folders. Client mail softwares support: * Horde: support namespaces, shared folders configurable via ''Options->Share Folders'' menu but no ACLs for public folders * Icedove/Thunderbird: support namespaces, shared and public folders configurable via folder selection and ''Tools->Imap-ACL'' menu action Most other softwares have namespace support only, so you should be able to use shared/public folders you have rights on but not configure them yourself (tell us if you know more software supporting this feature) == Fallback retention == The current retention period on our servers is 2 weeks, but can be temporary or permanently increased if needed. Mails flowing back to your primary server can be protected using TLS with certificate verification if you wish. Antivirus and antispam filtering are not applied to relayed mails, so we do not mess with your prefered strategy on your primary server, nevertheless basic checks (EHLO, DNS…) and RBL scoring are done to avoid accepting tons of SPAMs. f4fbc7c9b0cd1ba21d2f1ed4cacc96edda3d67da 221 220 2011-05-17T21:12:54Z Duck 2 /* Full Hosting */ wikitext text/x-wiki == Mail Hosting == What we can offer: * full hosting (MX1) on our servers: ** multiple email addresses which can be real mailboxes or mere redirections towards third party addresses ** based on ''milkypond.org'' (or maybe ''duckcorp.org'') domain(s) or you own domain(s) * fallback retention (MX2) on our servers or, at your choice, partner servers (currently via Hivane) == Full Hosting == === Access Methods === You can retrieve your mails, in case of a real mailbox, using: * IMAP+TLS (TCP 143) / IMAPS (TCP 993) on imap.duckcorp.org * or POP3+TLS (TCP 110) / POP3S (TCP 995) on pop.duckcorp.org * or one of the [https://webmail.duckcorp.org/ provided webmails] The IMAP protocol is recommended over POP3, as it provides many interresting features. If you want to download all your mails absolutely at home, loosing the ability to read your mail from anywhere on the planet, you can do that with IMAP too (look at your mail client settings). You can use our servers to send mails out too via smtp.duckcorp.org using: * SMTP+TLS (TCP 25) / SMTPS (TCP 465) * and SASL authentication === Antivirus and Antispam === Mails stored on our server are checked upon arrival for viruses and SPAMs. Mail redirected to a third party mailbox are not, not to mess with the strategy of the the final destination (which could arm learning greatly). Mails being viruses are suppressed automatically upon arrival. Once in a week, an extra antivirus check is done on all hosted mailboxes, to remove viruses not detected at the time it arrived (our antivirus database is updated daily), so you may see such mail disappear from your mailbox, don't fear. SPAMs are more difficult to detect, and it is an error-prone process, so we chose to use a learning software intead of using a global database. On the bright side of things, you would never loose mails and the software should be able to learn what is a SPAM from '''your''' point of view (which has proved to differ slightly between our users), but on the grey side you will have to teach him regulary to avoid errors. When your account is created, it acts like an empty headed body letting everything through, but after a few weeks of teaching it is able to recognise most of your habits and block a lot of annoying SPAM. To teach the system, you can: * use the [https://spamfilter.duckcorp.org/ web interface] to retrain from errors in the ''History'' page * resend SPAM to dc-spam@duckcorp.org and HAM (non-SPAM) to dc-ham@duckcorp.org *: {{warning}} PLEASE TAKE CARE to use the ''resend'' function of your mailer and never use ''forward'', which would result in '''yourself''' being considered as spam or ham You can yourself setup a few parameters in the ''Preferences'' page of the [https://spamfilter.duckcorp.org/ web interface], mostly: * how the system should train: ** TEFT (''On every new message scanned by the filter''): useful to learn very quickly especially on a new mailbox or when you've got tons of spam on your addresses, but you need to train it regulary (daily is better) or it will learn wrong (very quickly too !) ** TOE (''Only when the filter makes a mistake''): slow learning, but if you don't have time for training very often or go on long holidays without internet access this mode will give you a stable behavior ** TUM (''Only with new data or if the filter makes a mistake''): trade-off between the two previous modes, learn quite fast and not too demanding, adapts better to new SPAMs then TOE * filter sensitivity: you can ask the system to be more or less aggressive * message handling: ** ''Quarantine the message'': mails are not delivered to your mailbox but retained by the system and you can only manage them through the [https://spamfilter.duckcorp.org/ web interface] ; if you retrain a quarantined mail as HAM, it will be freed from quarantine and delivered in your mailbox at once ; in this mode, you need to flush your quarantine once in a while ** ''Tag the Subject header with'': mails are delivered with a modified title (which is a tad ugly) ** ''Deliver the message normally with a X-DSPAM-Result header'': mails are delivered with a special field in your mail headers (not always visible depending on your mail client and its configuration) ; this is quite handy if you prefer SPAMs arranged in a specific folder * ''Disable DSPAM filtering'': you may switch off filtering at your own risk We strongly recommend using TEFT with daily training for a few weeks then switching to TUM. If you need to go away for a long time, switching to TOE is recommended. Using the quarantine feature is also a safe choice, as the web interface is quite easy to use. === Mail Filtering === With your favourite mail client, you can probably filter your mails in proper folders already. Nevertheless, this can be a annoying operation: * blocking you mail client for a long time if you have to process plenty of mails * downloading each mail information, and sometimes content (depending on your filters), is lenghty too, and cost much bandwidth * syncing filters accross your machines (home desktop, laptop, office machine…) is a pain in the ass * processing only when you're online prevents triggering actions in a timely manner (automatic redirect, vacation messages…), and running a machine 24/7 with a mail client polling new mails every 30s is not a solution We provide a much better way to do this using the [[wikipedia:Sieve_(mail_filtering_language)|SIEVE]] filters. Shortly, SIEVE is a language dedicated to expressing mail filters. Our server is able to process your mails according to these filters as soon as they arrive. You then don't have to care about them anymore, and may use light mail clients or webmails when you're not on your machine with your favourite software. To push your filters on the server, a dedicated protocol exists: : MANAGESIEVE (TCP 4190) on sieve.duckcorp.org Several softwares support managing SIEVE rules: * Icedove/Thunderbird using the SIEVE extension (in xul-ext-sieve Debian package) provides a rules editor * Horde (Ingo) provides an easy to use web interface * Squirrelmail with the Avelsieve extension provides an easy to use web interface * Roundcube with an extension provides an easy to use web interface * sieve-connect provides a CLI to upload/download/activate your rules files (tell us if you know more software supporting this feature) You can read more info about SIEVE here: * supported SIEVE features on our server: http://pigeonhole.dovecot.org/ * http://www.fastmail.fm/docs/sieve/ * http://sieve.info/ === Shared/Public Folders === You may need to share mails or messages with friends or people you do stuff with (in a project or association). Depending on your needs, two solutions are possible: * share some of your own private folders, thus called ''shared folders'' * manage a special folder hierarchy, called ''public folders'' (even if they may not be accessible to everyone) Through IMAP, or our webmails internally using IMAP, it is possible to partition the folder hierarchy into ''namespaces''. Traditionally you are using the root namespace for your private folders. Additionnal namespaces can be created and will appear among your own folders or separate, depending on your mail client's choice of representation. To avoid name clashes, we decided to prefix all additionnal namespace names with a '''#'''. Since 2011-05-14, the following extra namespaces are created and reserved: * #Shared, containing all folders other users decided to share with you * #MilkyPond, containing public MP/DC information mailboxes you may subscribe at will Using IMAP, it is possible to setup rights (read only, write allowed…) to your own folders in order to share them with other users, or group of users. Public folders are owned by noone, and must be created by DC administrators ; if you need one, send us a request and we may be able to create it and delegate administration to your care (namespace name is subject to approval). Once created, public folders can be administered like shared folders. Client mail softwares support: * Horde: support namespaces, shared folders configurable via ''Options->Share Folders'' menu but no ACLs for public folders * Icedove/Thunderbird: support namespaces, shared and public folders configurable via folder selection and ''Tools->Imap-ACL'' menu action Most other softwares have namespace support only, so you should be able to use shared/public folders you have rights on but not configure them yourself (tell us if you know more software supporting this feature) === Quotas === == Fallback retention == The current retention period on our servers is 2 weeks, but can be temporary or permanently increased if needed. Mails flowing back to your primary server can be protected using TLS with certificate verification if you wish. Antivirus and antispam filtering are not applied to relayed mails, so we do not mess with your prefered strategy on your primary server, nevertheless basic checks (EHLO, DNS…) and RBL scoring are done to avoid accepting tons of SPAMs. a4f8a26b50d9a57bfbd632e990c8ed9a4d9fe87f 222 221 2011-05-17T21:19:37Z Duck 2 /* Quotas */ wikitext text/x-wiki == Mail Hosting == What we can offer: * full hosting (MX1) on our servers: ** multiple email addresses which can be real mailboxes or mere redirections towards third party addresses ** based on ''milkypond.org'' (or maybe ''duckcorp.org'') domain(s) or you own domain(s) * fallback retention (MX2) on our servers or, at your choice, partner servers (currently via Hivane) == Full Hosting == === Access Methods === You can retrieve your mails, in case of a real mailbox, using: * IMAP+TLS (TCP 143) / IMAPS (TCP 993) on imap.duckcorp.org * or POP3+TLS (TCP 110) / POP3S (TCP 995) on pop.duckcorp.org * or one of the [https://webmail.duckcorp.org/ provided webmails] The IMAP protocol is recommended over POP3, as it provides many interresting features. If you want to download all your mails absolutely at home, loosing the ability to read your mail from anywhere on the planet, you can do that with IMAP too (look at your mail client settings). You can use our servers to send mails out too via smtp.duckcorp.org using: * SMTP+TLS (TCP 25) / SMTPS (TCP 465) * and SASL authentication === Antivirus and Antispam === Mails stored on our server are checked upon arrival for viruses and SPAMs. Mail redirected to a third party mailbox are not, not to mess with the strategy of the the final destination (which could arm learning greatly). Mails being viruses are suppressed automatically upon arrival. Once in a week, an extra antivirus check is done on all hosted mailboxes, to remove viruses not detected at the time it arrived (our antivirus database is updated daily), so you may see such mail disappear from your mailbox, don't fear. SPAMs are more difficult to detect, and it is an error-prone process, so we chose to use a learning software intead of using a global database. On the bright side of things, you would never loose mails and the software should be able to learn what is a SPAM from '''your''' point of view (which has proved to differ slightly between our users), but on the grey side you will have to teach him regulary to avoid errors. When your account is created, it acts like an empty headed body letting everything through, but after a few weeks of teaching it is able to recognise most of your habits and block a lot of annoying SPAM. To teach the system, you can: * use the [https://spamfilter.duckcorp.org/ web interface] to retrain from errors in the ''History'' page * resend SPAM to dc-spam@duckcorp.org and HAM (non-SPAM) to dc-ham@duckcorp.org *: {{warning}} PLEASE TAKE CARE to use the ''resend'' function of your mailer and never use ''forward'', which would result in '''yourself''' being considered as spam or ham You can yourself setup a few parameters in the ''Preferences'' page of the [https://spamfilter.duckcorp.org/ web interface], mostly: * how the system should train: ** TEFT (''On every new message scanned by the filter''): useful to learn very quickly especially on a new mailbox or when you've got tons of spam on your addresses, but you need to train it regulary (daily is better) or it will learn wrong (very quickly too !) ** TOE (''Only when the filter makes a mistake''): slow learning, but if you don't have time for training very often or go on long holidays without internet access this mode will give you a stable behavior ** TUM (''Only with new data or if the filter makes a mistake''): trade-off between the two previous modes, learn quite fast and not too demanding, adapts better to new SPAMs then TOE * filter sensitivity: you can ask the system to be more or less aggressive * message handling: ** ''Quarantine the message'': mails are not delivered to your mailbox but retained by the system and you can only manage them through the [https://spamfilter.duckcorp.org/ web interface] ; if you retrain a quarantined mail as HAM, it will be freed from quarantine and delivered in your mailbox at once ; in this mode, you need to flush your quarantine once in a while ** ''Tag the Subject header with'': mails are delivered with a modified title (which is a tad ugly) ** ''Deliver the message normally with a X-DSPAM-Result header'': mails are delivered with a special field in your mail headers (not always visible depending on your mail client and its configuration) ; this is quite handy if you prefer SPAMs arranged in a specific folder * ''Disable DSPAM filtering'': you may switch off filtering at your own risk We strongly recommend using TEFT with daily training for a few weeks then switching to TUM. If you need to go away for a long time, switching to TOE is recommended. Using the quarantine feature is also a safe choice, as the web interface is quite easy to use. === Mail Filtering === With your favourite mail client, you can probably filter your mails in proper folders already. Nevertheless, this can be a annoying operation: * blocking you mail client for a long time if you have to process plenty of mails * downloading each mail information, and sometimes content (depending on your filters), is lenghty too, and cost much bandwidth * syncing filters accross your machines (home desktop, laptop, office machine…) is a pain in the ass * processing only when you're online prevents triggering actions in a timely manner (automatic redirect, vacation messages…), and running a machine 24/7 with a mail client polling new mails every 30s is not a solution We provide a much better way to do this using the [[wikipedia:Sieve_(mail_filtering_language)|SIEVE]] filters. Shortly, SIEVE is a language dedicated to expressing mail filters. Our server is able to process your mails according to these filters as soon as they arrive. You then don't have to care about them anymore, and may use light mail clients or webmails when you're not on your machine with your favourite software. To push your filters on the server, a dedicated protocol exists: : MANAGESIEVE (TCP 4190) on sieve.duckcorp.org Several softwares support managing SIEVE rules: * Icedove/Thunderbird using the SIEVE extension (in xul-ext-sieve Debian package) provides a rules editor * Horde (Ingo) provides an easy to use web interface * Squirrelmail with the Avelsieve extension provides an easy to use web interface * Roundcube with an extension provides an easy to use web interface * sieve-connect provides a CLI to upload/download/activate your rules files (tell us if you know more software supporting this feature) You can read more info about SIEVE here: * supported SIEVE features on our server: http://pigeonhole.dovecot.org/ * http://www.fastmail.fm/docs/sieve/ * http://sieve.info/ === Shared/Public Folders === You may need to share mails or messages with friends or people you do stuff with (in a project or association). Depending on your needs, two solutions are possible: * share some of your own private folders, thus called ''shared folders'' * manage a special folder hierarchy, called ''public folders'' (even if they may not be accessible to everyone) Through IMAP, or our webmails internally using IMAP, it is possible to partition the folder hierarchy into ''namespaces''. Traditionally you are using the root namespace for your private folders. Additionnal namespaces can be created and will appear among your own folders or separate, depending on your mail client's choice of representation. To avoid name clashes, we decided to prefix all additionnal namespace names with a '''#'''. Since 2011-05-14, the following extra namespaces are created and reserved: * #Shared, containing all folders other users decided to share with you * #MilkyPond, containing public MP/DC information mailboxes you may subscribe at will Using IMAP, it is possible to setup rights (read only, write allowed…) to your own folders in order to share them with other users, or group of users. Public folders are owned by noone, and must be created by DC administrators ; if you need one, send us a request and we may be able to create it and delegate administration to your care (namespace name is subject to approval). Once created, public folders can be administered like shared folders. Client mail softwares support: * Horde: support namespaces, shared folders configurable via ''Options->Share Folders'' menu but no ACLs for public folders * Icedove/Thunderbird: support namespaces, shared and public folders configurable via folder selection and ''Tools->Imap-ACL'' menu action Most other softwares have namespace support only, so you should be able to use shared/public folders you have rights on but not configure them yourself (tell us if you know more software supporting this feature) === Quotas === Even if it would be nice to live without it, we had to establish quotas to force people sort their mails out once in a while and delete useless things instead of leaving an ever-growing mess behind. The default quota is 512MB which is not that big but should match needs of most users. This said, you may ask us for more and there's no reason we would refuse a reasonable demand. == Fallback retention == The current retention period on our servers is 2 weeks, but can be temporary or permanently increased if needed. Mails flowing back to your primary server can be protected using TLS with certificate verification if you wish. Antivirus and antispam filtering are not applied to relayed mails, so we do not mess with your prefered strategy on your primary server, nevertheless basic checks (EHLO, DNS…) and RBL scoring are done to avoid accepting tons of SPAMs. d6ba342cb3c9b64932136964f56ad64e3cd74deb 245 222 2012-01-23T01:34:47Z Duck 2 wikitext text/x-wiki What we can offer: * multiple email addresses (mailboxes or redirections) based on ''milkypond.org'' (or maybe ''duckcorp.org'') domain(s) or you own domain(s) * roaming accounts to be able to send emails wherever you are == Access Methods == You can retrieve your mails, in case of a real mailbox, using: * IMAP+TLS (TCP 143) / IMAPS (TCP 993) on imap.duckcorp.org * or POP3+TLS (TCP 110) / POP3S (TCP 995) on pop.duckcorp.org * or one of the [https://webmail.duckcorp.org/ provided webmails] The IMAP protocol is recommended over POP3, as it provides many interresting features. If you want to download all your mails absolutely at home, loosing the ability to read your mail from anywhere on the planet, you can do that with IMAP too (look at your mail client settings). You can use our servers to send mails out too via smtp.duckcorp.org using: * SMTP+TLS (TCP 25) / SMTPS (TCP 465) * and SASL authentication == Mailboxes Features == === Antivirus and Antispam === Mails stored on our server are checked upon arrival for viruses and SPAMs. Mail redirected to a third party mailbox are not, not to mess with the strategy of the the final destination (which could arm learning greatly). Mails being viruses are suppressed automatically upon arrival. Once in a week, an extra antivirus check is done on all hosted mailboxes, to remove viruses not detected at the time it arrived (our antivirus database is updated daily), so you may see such mail disappear from your mailbox, don't fear. SPAMs are more difficult to detect, and it is an error-prone process, so we chose to use a learning software intead of using a global database. On the bright side of things, you would never loose mails and the software should be able to learn what is a SPAM from '''your''' point of view (which has proved to differ slightly between our users), but on the grey side you will have to teach him regulary to avoid errors. When your account is created, it acts like an empty headed body letting everything through, but after a few weeks of teaching it is able to recognise most of your habits and block a lot of annoying SPAM. To teach the system, you can: * use the [https://spamfilter.duckcorp.org/ web interface] to retrain from errors in the ''History'' page * resend SPAM to dc-spam@duckcorp.org and HAM (non-SPAM) to dc-ham@duckcorp.org *: {{warning}} PLEASE TAKE CARE to use the ''resend'' function of your mailer and never use ''forward'', which would result in '''yourself''' being considered as spam or ham You can yourself setup a few parameters in the ''Preferences'' page of the [https://spamfilter.duckcorp.org/ web interface], mostly: * how the system should train: ** TEFT (''On every new message scanned by the filter''): useful to learn very quickly especially on a new mailbox or when you've got tons of spam on your addresses, but you need to train it regulary (daily is better) or it will learn wrong (very quickly too !) ** TOE (''Only when the filter makes a mistake''): slow learning, but if you don't have time for training very often or go on long holidays without internet access this mode will give you a stable behavior ** TUM (''Only with new data or if the filter makes a mistake''): trade-off between the two previous modes, learn quite fast and not too demanding, adapts better to new SPAMs then TOE * filter sensitivity: you can ask the system to be more or less aggressive * message handling: ** ''Quarantine the message'': mails are not delivered to your mailbox but retained by the system and you can only manage them through the [https://spamfilter.duckcorp.org/ web interface] ; if you retrain a quarantined mail as HAM, it will be freed from quarantine and delivered in your mailbox at once ; in this mode, you need to flush your quarantine once in a while ** ''Tag the Subject header with'': mails are delivered with a modified title (which is a tad ugly) ** ''Deliver the message normally with a X-DSPAM-Result header'': mails are delivered with a special field in your mail headers (not always visible depending on your mail client and its configuration) ; this is quite handy if you prefer SPAMs arranged in a specific folder * ''Disable DSPAM filtering'': you may switch off filtering at your own risk We strongly recommend using TEFT with daily training for a few weeks then switching to TUM. If you need to go away for a long time, switching to TOE is recommended. Using the quarantine feature is also a safe choice, as the web interface is quite easy to use. === Mail Filtering === With your favourite mail client, you can probably filter your mails in proper folders already. Nevertheless, this can be a annoying operation: * blocking you mail client for a long time if you have to process plenty of mails * downloading each mail information, and sometimes content (depending on your filters), is lenghty too, and cost much bandwidth * syncing filters accross your machines (home desktop, laptop, office machine…) is a pain in the ass * processing only when you're online prevents triggering actions in a timely manner (automatic redirect, vacation messages…), and running a machine 24/7 with a mail client polling new mails every 30s is not a solution We provide a much better way to do this using the [[wikipedia:Sieve_(mail_filtering_language)|SIEVE]] filters. Shortly, SIEVE is a language dedicated to expressing mail filters. Our server is able to process your mails according to these filters as soon as they arrive. You then don't have to care about them anymore, and may use light mail clients or webmails when you're not on your machine with your favourite software. To push your filters on the server, a dedicated protocol exists: : MANAGESIEVE (TCP 4190) on sieve.duckcorp.org Several softwares support managing SIEVE rules: * Icedove/Thunderbird using the SIEVE extension (in xul-ext-sieve Debian package) provides a rules editor * Horde (Ingo) provides an easy to use web interface * Squirrelmail with the Avelsieve extension provides an easy to use web interface * Roundcube with an extension provides an easy to use web interface * sieve-connect provides a CLI to upload/download/activate your rules files (tell us if you know more software supporting this feature) You can read more info about SIEVE here: * supported SIEVE features on our server: http://pigeonhole.dovecot.org/ * http://www.fastmail.fm/docs/sieve/ * http://sieve.info/ === Shared/Public Folders === You may need to share mails or messages with friends or people you do stuff with (in a project or association). Depending on your needs, two solutions are possible: * share some of your own private folders, thus called ''shared folders'' * manage a special folder hierarchy, called ''public folders'' (even if they may not be accessible to everyone) Through IMAP, or our webmails internally using IMAP, it is possible to partition the folder hierarchy into ''namespaces''. Traditionally you are using the root namespace for your private folders. Additionnal namespaces can be created and will appear among your own folders or separate, depending on your mail client's choice of representation. To avoid name clashes, we decided to prefix all additionnal namespace names with a '''#'''. Since 2011-05-14, the following extra namespaces are created and reserved: * #Shared, containing all folders other users decided to share with you * #MilkyPond, containing public MP/DC information mailboxes you may subscribe at will Using IMAP, it is possible to setup rights (read only, write allowed…) to your own folders in order to share them with other users, or group of users. Public folders are owned by noone, and must be created by DC administrators ; if you need one, send us a request and we may be able to create it and delegate administration to your care (namespace name is subject to approval). Once created, public folders can be administered like shared folders. Client mail softwares support: * Horde: support namespaces, shared folders configurable via ''Options->Share Folders'' menu but no ACLs for public folders * Icedove/Thunderbird: support namespaces, shared and public folders configurable via folder selection and ''Tools->Imap-ACL'' menu action Most other softwares have namespace support only, so you should be able to use shared/public folders you have rights on but not configure them yourself (tell us if you know more software supporting this feature) == Limitations == === Maximum Mail Size === Mail you send or receive are limited to 10MB. If you need to transmit much bigger data, then a mail transport is not appropriate, you'd better use a file sharing method instead. === Quotas === Even if it would be nice to live without it, we had to establish quotas to force people sort their mails out once in a while and delete useless things instead of leaving an ever-growing mess behind. The default quota is 512MB which is not that big but should match needs of most users. This said, you may ask us for more and there's no reason we would refuse a reasonable demand. cd7acc4018f3af35ad1f5d663e25150b9d7a9f95 0 46 223 181 2011-08-11T11:41:08Z Duck 2 wikitext text/x-wiki == Introduction == '''All''' services containing sensitive information are protected using cryptography. Whenever possible, we add the necessary configuration to ensure unsecure usages are not possible, to protect your data. Nevertheless, a few things are needed on your side to improve security, that's why we are providing the following notes in order to help you configure your software in a secure fashion. == Areas of Security == === Mails from DC's Administrators === You should not trust mails pretenting to come from us. The only way to be sure a mail is from someone, is to agree on exchanging cryptographically-protected messages. On [[Admins|this page]] you'll find the list of DC's administrators from which you may receive mails (on the users's mailing-list for example). You could trust their GPG keys directly, but that would not be secure at all. The best way is to meet, live, in a [[wikipedia:Key_signing_party|key signing party]]. If a friend has already signed our key, and is not too far from you, you may also propagate your trust to our keys. Once done, you'll be sure what seems to come from us is really from us. === Talking to the Right Machine/Service === All remote services use an address on the internet, like ''superservice.duckcorp.org'', but if you are connected through an untrusted network (like if you're using a third-party's WIFI), you cannot be sure you'll be connecting to the right machine, and you may disclose important information like your credentials. ==== TLS/SSL-based Services ==== To ensure you're talking to the right server, and noone pretend to be a DC's server to tricks you, you need to install the following certificate ([[File:Duckcorp.crt]]): * either in your software configuration (for example, to validate HTTP site in your browser, clicking on the link should ask for installation, and you'll just need to confirm you trust it) * or globally on your host by installing the certificate, as root: ** (method 1, prefered) in ''/usr/local/share/ca-certificates'', and running ''update-ca-certificates'' (the ''ca-certificates'' package needs to be installed) ** (method 2, not suitable for GNUTLS-based apps) in ''/etc/ssl/certs'', and running ''c_rehash'' (the ''openssl'' package needs to be installed) ==== Service Locator Security ==== One possible attack is to alter replies from the machine locator service (DNS) in order to redirect your communication to a nasty machine. Since November 2010, ''duckcorp.org'' and ''milkypond.org'' domains are cryptographically signed using the DNSSEC system, so you are now able to verify the address returned for the service is the right one. This system is not new, but has recently switched into production, so your operating system may not yet be properly configured to use this protection. Until it is pre-configured in most of them, you may configure it yourself using [[Services/DNS#How_to_test_my_zone_is_secured.3F|this procedure]]. {{warning}} Beware this protection solves certains security problems but is not sufficient to ensure you're talking to the right machine/service. Nevertheless it ensures: * the address of the machine/service is the right one * information related to the domain, list of mail servers, security information on hosts (SSHFP)… are not tampered Using this security plus certificate verification (see [[Services/Security#TLS.2FSSL-based_Services|section about TLS/SSL-based Security]]) would ensure full security. === Secure SSH Connections === In order not to be tricked connecting to a fake server, or to a rooted server (just in case), it is possible to check the SSH key of the server. As this verification is quite boring both for administrators and users, almost nobody on earth does it. Fortunately, it is possible to publish this information in the DNS and have OpenSSH check it for you automatically. To add this security, you can edit your system configuration (''/etc/ssh/ssh_config'') or your personal one (''~/.ssh/config''), and add the folowing: Host * VerifyHostKeyDNS ask Of course, the DNS replies may be altered, so if you want full security, read the [[Services/Security#Service_Locator_Security|section about Service Locator Security]]. 27baf826ab957dfb16e8d2b33173483a928fb1ba 0 39 224 190 2011-08-11T11:43:43Z Duck 2 wikitext text/x-wiki Here is a short overview of the services provided by DuckCorp. Our services are supervised and important data are saved regulary. {{warning}} [[Services/Security|Notes about security !]] == Public Services == * a stratum 2 NTP server, to setup time on your machines, and also part of the [http://www.pool.ntp.org/en/ NTP Pool Project] * a dictionnary server, using the DICT protocol, provided with a [http://dico.duckcorp.org/ web interface] == Shared Users Services == Even if the service is publicly accessible, and is used to share information with the world, parts of the it may be restricted by their respective owner. * [ftp://ftp.duckcorp.org/ public FTP server] (with ACLs) * [https://wiki.duckcorp.org/ public wiki] (with ACLs) * [https://projects.duckcorp.org/ public issue tracker] (with ACLs) * [https://rcs.duckcorp.org/ public VCS access] (with web viewers) * [http://debian.duckcorp.org/ public Debian repository] (needs rework) * [http://photos.duckcorp.org/ public photo gallery] (with ACLs) == Users Services == * Network facilities: ** [[Services/DNS|DNS hosting]] (NS1/NS2, DNSSEC) ** IPv6 tunnels ** [[Services/NSTX|NSTX]] (IP over DNS tunnels) * Communication facilities: ** [[Services/Mail|mail hosting]] (MX1/MX2, user controlled antispam, antivirus, flexible quotas, SIEVE filtering, webmails, ...) ** mailing-lists hosting ** IRC world: *** IRC Network (with web gateway) *** IRC bouncer *** IRC to IM gateway (to connect to ICQ/AIM/YM!/... through an IRC interface) ** XMPP (Jabber) Network (using the 'milkypond.org' domain, or a user domain) ** Triboune Libre ** SAFT * Application facilities: ** web hosting, with various possibilities for web programming (SSI, PHP, Perl, Python, Ruby, ...), and stats ** VCS hosting: git, SVN, BZR ** shell access (site admin, run custom scripts, screen for text-mode geeks, ...) (for trusted users only) * Databases facilities: ** PostgreSQL ** MySQL ** LDAP * [[Services/Backup|Backup]] 23c9c6d24b72610f4982d600b7bafddf72e84a6f 229 224 2012-01-22T17:59:05Z Duck 2 /* Users Services */ wikitext text/x-wiki Here is a short overview of the services provided by DuckCorp. Our services are supervised and important data are saved regulary. {{warning}} [[Services/Security|Notes about security !]] == Public Services == * a stratum 2 NTP server, to setup time on your machines, and also part of the [http://www.pool.ntp.org/en/ NTP Pool Project] * a dictionnary server, using the DICT protocol, provided with a [http://dico.duckcorp.org/ web interface] == Shared Users Services == Even if the service is publicly accessible, and is used to share information with the world, parts of the it may be restricted by their respective owner. * [ftp://ftp.duckcorp.org/ public FTP server] (with ACLs) * [https://wiki.duckcorp.org/ public wiki] (with ACLs) * [https://projects.duckcorp.org/ public issue tracker] (with ACLs) * [https://rcs.duckcorp.org/ public VCS access] (with web viewers) * [http://debian.duckcorp.org/ public Debian repository] (needs rework) * [http://photos.duckcorp.org/ public photo gallery] (with ACLs) == Users Services == * Network facilities: ** [[Services/DNS|DNS hosting]] (NS1/NS2, DNSSEC) ** IPv6 tunnels ** [[Services/NSTX|NSTX]] (IP over DNS tunnels) * Communication facilities: ** [[Services/Mail|mail hosting]] (MX1/MX2, user controlled antispam, antivirus, flexible quotas, SIEVE filtering, webmails, ...) ** mailing-lists hosting ** IRC world: *** IRC Network (with web gateway) *** IRC bouncer *** IRC to IM gateway (to connect to ICQ/AIM/YM!/... through an IRC interface) ** XMPP (Jabber) Network (using the 'milkypond.org' domain, or a user domain) ** Triboune Libre ** SAFT * Application facilities: ** web hosting, with various possibilities for web programming (SSI, PHP, Perl, Python, Ruby, ...), and stats ** VCS hosting: git, SVN, BZR ** [[Services/Shell|shell access]] (site admin, run custom scripts, screen for text-mode geeks, ...) (for trusted users only) * Databases facilities: ** PostgreSQL ** MySQL ** LDAP * [[Services/Backup|Backup]] 585bdbfa9fc94d421b2efc954fd5e464b3967f53 238 229 2012-01-22T23:56:08Z Duck 2 wikitext text/x-wiki Here is a short overview of the services provided by DuckCorp. Our services are supervised and important data are [[Services/Backup|saved regularly]]. {{warning}} [[Services/Security|Notes about security !]] == Public Services == * a stratum 2 NTP server, to setup time on your machines, and also part of the [http://www.pool.ntp.org/en/ NTP Pool Project] * a dictionnary server, using the DICT protocol, provided with a [http://dico.duckcorp.org/ web interface] == Shared Users Services == Even if the service is publicly accessible, and is used to share information with the world, parts of the it may be restricted by their respective owner. * [ftp://ftp.duckcorp.org/ public FTP server] (with ACLs) * [https://wiki.duckcorp.org/ public wiki] (with ACLs) * [https://projects.duckcorp.org/ public issue tracker] (with ACLs) * [https://rcs.duckcorp.org/ public VCS access] (with web viewers) * [http://debian.duckcorp.org/ public Debian repository] (needs rework) * [http://photos.duckcorp.org/ public photo gallery] (with ACLs) == Users Services == * Network facilities: ** [[Services/DNS|DNS hosting]] (NS1/NS2, DNSSEC) ** IPv6 tunnels ** [[Services/NSTX|NSTX]] (IP over DNS tunnels) * Communication facilities: ** [[Services/Mail|mail hosting]] (MX1/MX2, user controlled antispam, antivirus, flexible quotas, SIEVE filtering, webmails, ...) ** mailing-lists hosting ** IRC world: *** IRC Network (with web gateway) *** IRC bouncer *** IRC to IM gateway (to connect to ICQ/AIM/YM!/... through an IRC interface) ** XMPP (Jabber) Network (using the 'milkypond.org' domain, or a user domain) ** Triboune Libre ** SAFT * Application facilities: ** web hosting, with various possibilities for web programming (SSI, PHP, Perl, Python, Ruby, ...), and stats ** VCS hosting: git, SVN, BZR ** [[Services/Shell|shell access]] (site admin, run custom scripts, screen for text-mode geeks, ...) (for trusted users only) * Databases facilities: ** PostgreSQL ** MySQL ** LDAP a4ddc206f5788310db98e0d2bb8ecdc23efad7d9 239 238 2012-01-23T00:33:08Z Duck 2 wikitext text/x-wiki Here is a short overview of the services provided by DuckCorp. Our services are supervised and important data are [[Services/Backup|saved regularly]]. {{warning}} [[Services/Security|Notes about security !]] {| class="wikitable" style="text-align: center; width: 100%;" |+ Available Services |- ! Category !! colspan="2" | Service !! Access !! Description |- | rowspan="5" | Communication || rowspan="2" | Mail || [[Services/Mail|eMails]] || users || Mail box(es) with anti-spam/anti-virus, filtering…, mail redirections, mail hosting (MX1, MX2) |- | Mailing-Lists || users || Distribution lists for mails |- | rowspan="3" | IRC || IRC Network || all || MilkyPond Chat Network using a dedicated software or a web-interface |- | IRC Bouncer || users || [[wikipedia:IRC_bouncer#IRC|IRC proxy]] (IRC server relaying IRC communications, keeping connections open and remembering logs) |- | IRC to IM gateway || users || IRC server relaying communication to multiple instant messaging networks in a unified interface (supported network: ICQ/AIM/YM!/…, support as much networks as [[wikipedia:Pidgin_(software)#Supported_protocols|Pidgin]] + coincoin) |} == Public Services == * a stratum 2 NTP server, to setup time on your machines, and also part of the [http://www.pool.ntp.org/en/ NTP Pool Project] * a dictionnary server, using the DICT protocol, provided with a [http://dico.duckcorp.org/ web interface] == Shared Users Services == Even if the service is publicly accessible, and is used to share information with the world, parts of the it may be restricted by their respective owner. * [ftp://ftp.duckcorp.org/ public FTP server] (with ACLs) * [https://wiki.duckcorp.org/ public wiki] (with ACLs) * [https://projects.duckcorp.org/ public issue tracker] (with ACLs) * [https://rcs.duckcorp.org/ public VCS access] (with web viewers) * [http://debian.duckcorp.org/ public Debian repository] (needs rework) * [http://photos.duckcorp.org/ public photo gallery] (with ACLs) == Users Services == * Network facilities: ** [[Services/DNS|DNS hosting]] (NS1/NS2, DNSSEC) ** IPv6 tunnels ** [[Services/NSTX|NSTX]] (IP over DNS tunnels) * Communication facilities: ** XMPP (Jabber) Network (using the 'milkypond.org' domain, or a user domain) ** Triboune Libre ** SAFT * Application facilities: ** web hosting, with various possibilities for web programming (SSI, PHP, Perl, Python, Ruby, ...), and stats ** VCS hosting: git, SVN, BZR ** [[Services/Shell|shell access]] (site admin, run custom scripts, screen for text-mode geeks, ...) (for trusted users only) * Databases facilities: ** PostgreSQL ** MySQL ** LDAP e1aeaad5b5137a9ae46856af5188c26adf63487d 240 239 2012-01-23T00:53:20Z Duck 2 wikitext text/x-wiki Here is a short overview of the services provided by DuckCorp. Our services are supervised and important data are [[Services/Backup|saved regularly]]. {{warning}} [[Services/Security|Notes about security !]] {| class="wikitable" style="text-align: center; width: 100%;" |+ Available Services |- ! Category !! colspan="2" | Service !! Access !! Description |- | rowspan="7" | Communication || rowspan="2" | Mail || [[Services/Mail|eMails]] || users || Mail box(es) with anti-spam/anti-virus, filtering…, mail redirections, mail hosting (MX1, MX2) |- | Mailing-Lists || users || Distribution lists for mails |- | rowspan="3" | IRC || IRC Network || public || MilkyPond Chat Network using a dedicated software or a web-interface |- | IRC Bouncer || users || [[wikipedia:IRC_bouncer#IRC|IRC proxy]] (IRC server relaying IRC communications, keeping connections open and remembering logs) |- | IRC to IM gateway || users || IRC server relaying communication to multiple instant messaging networks in a unified interface (supported network: ICQ/AIM/YM!/…, support as much networks as [[wikipedia:Pidgin_(software)#Supported_protocols|Pidgin]] + coincoin) |- | colspan="2" | XMPP (Jabber) || users || Global Chat Network (inter-communication between many [[Xmpp#History|well-known public IM services]]) |- | colspan="2" | Triboune Libre || public || MilkyPond Web-chat system inspired by [http://linuxfr.org/board the famous one] on [http://linuxfr.org/ Linuxfr.org] |} == Public Services == * a stratum 2 NTP server, to setup time on your machines, and also part of the [http://www.pool.ntp.org/en/ NTP Pool Project] * a dictionnary server, using the DICT protocol, provided with a [http://dico.duckcorp.org/ web interface] == Shared Users Services == Even if the service is publicly accessible, and is used to share information with the world, parts of the it may be restricted by their respective owner. * [ftp://ftp.duckcorp.org/ public FTP server] (with ACLs) * [https://wiki.duckcorp.org/ public wiki] (with ACLs) * [https://projects.duckcorp.org/ public issue tracker] (with ACLs) * [https://rcs.duckcorp.org/ public VCS access] (with web viewers) * [http://debian.duckcorp.org/ public Debian repository] (needs rework) * [http://photos.duckcorp.org/ public photo gallery] (with ACLs) == Users Services == * Network facilities: ** [[Services/DNS|DNS hosting]] (NS1/NS2, DNSSEC) ** IPv6 tunnels ** [[Services/NSTX|NSTX]] (IP over DNS tunnels) * Communication facilities: ** SAFT * Application facilities: ** web hosting, with various possibilities for web programming (SSI, PHP, Perl, Python, Ruby, ...), and stats ** VCS hosting: git, SVN, BZR ** [[Services/Shell|shell access]] (site admin, run custom scripts, screen for text-mode geeks, ...) (for trusted users only) * Databases facilities: ** PostgreSQL ** MySQL ** LDAP 00bc93cdc76a5a28dce0984b9b0e1063017cdc47 241 240 2012-01-23T01:01:01Z Duck 2 wikitext text/x-wiki Here is a short overview of the services provided by DuckCorp. Our services are supervised and important data are [[Services/Backup|saved regularly]]. {{warning}} [[Services/Security|Notes about security !]] {| class="wikitable" style="text-align: center; width: 100%;" |+ Available Services |- ! Category !! colspan="2" | Service !! Access !! Description |- | rowspan="7" | Communication || rowspan="2" | Mail || [[Services/Mail|eMails]] || users || Mail box(es) with anti-spam/anti-virus, filtering…, mail redirections, mail hosting (MX1, MX2) |- | Mailing-Lists || users || Distribution lists for mails |- | rowspan="3" | IRC || IRC Network || public || MilkyPond Chat Network using a dedicated software or a Web-interface |- | IRC Bouncer || users || [[wikipedia:IRC_bouncer#IRC|IRC proxy]] (IRC server relaying IRC communications, keeping connections open and remembering logs) |- | IRC to IM gateway || users || IRC server relaying communication to multiple instant messaging networks in a unified interface (supported network: ICQ/AIM/YM!/…, support as much networks as [[wikipedia:Pidgin_(software)#Supported_protocols|Pidgin]] + coincoin) |- | colspan="2" | XMPP (Jabber) || users || Global Chat Network (inter-communication between many [[Xmpp#History|well-known public IM services]]) |- | colspan="2" | Triboune Libre || public || MilkyPond Web-chat system inspired by [http://linuxfr.org/board the famous one] on [http://linuxfr.org/ Linuxfr.org] |- | rowspan="2" | Utilities || colspan="2" | Time Server || public || System used to automatically setup time on your machines (and also part of the [http://www.pool.ntp.org/en/ NTP Pool Project]) |- | colspan="2" | Dictionary Server || public || Words searching system via a dedicated software (using the DICT protocol) or a Web-interface |} == Shared Users Services == Even if the service is publicly accessible, and is used to share information with the world, parts of the it may be restricted by their respective owner. * [ftp://ftp.duckcorp.org/ public FTP server] (with ACLs) * [https://wiki.duckcorp.org/ public wiki] (with ACLs) * [https://projects.duckcorp.org/ public issue tracker] (with ACLs) * [https://rcs.duckcorp.org/ public VCS access] (with web viewers) * [http://debian.duckcorp.org/ public Debian repository] (needs rework) * [http://photos.duckcorp.org/ public photo gallery] (with ACLs) == Users Services == * Network facilities: ** [[Services/DNS|DNS hosting]] (NS1/NS2, DNSSEC) ** IPv6 tunnels ** [[Services/NSTX|NSTX]] (IP over DNS tunnels) * Communication facilities: ** SAFT * Application facilities: ** web hosting, with various possibilities for web programming (SSI, PHP, Perl, Python, Ruby, ...), and stats ** VCS hosting: git, SVN, BZR ** [[Services/Shell|shell access]] (site admin, run custom scripts, screen for text-mode geeks, ...) (for trusted users only) * Databases facilities: ** PostgreSQL ** MySQL ** LDAP 4e9a1b70eb62183ba15d21696bcbd9dd0cd9c1fb 242 241 2012-01-23T01:07:38Z Duck 2 wikitext text/x-wiki Here is a short overview of the services provided by DuckCorp. Our services are supervised and important data are [[Services/Backup|saved regularly]]. {{warning}} [[Services/Security|Notes about security !]] {| class="wikitable" style="text-align: center; width: 100%;" |+ Available Services |- ! Category !! colspan="2" | Service !! Access !! Description |- | rowspan="7" | Communication || rowspan="2" | Mail || [[Services/Mail|eMails]] || users || Mail box(es) with anti-spam/anti-virus, filtering…, mail redirections, mail hosting (MX1, MX2) |- | Mailing-Lists || users || Distribution lists for mails |- | rowspan="3" | IRC || IRC Network || public || MilkyPond Chat Network using a dedicated software or a Web-interface |- | IRC Bouncer || users || [[wikipedia:IRC_bouncer#IRC|IRC proxy]] (IRC server relaying IRC communications, keeping connections open and remembering logs) |- | IRC to IM gateway || users || IRC server relaying communication to multiple instant messaging networks in a unified interface (supported network: ICQ/AIM/YM!/…, support as much networks as [[wikipedia:Pidgin_(software)#Supported_protocols|Pidgin]] + coincoin) |- | colspan="2" | XMPP (Jabber) || users || Global Chat Network (inter-communication between many [[Xmpp#History|well-known public IM services]]) |- | colspan="2" | Triboune Libre || public || MilkyPond Web-chat system inspired by [http://linuxfr.org/board the famous one] on [http://linuxfr.org/ Linuxfr.org] |- | rowspan="2" | Utilities || colspan="2" | Time Server || public || System used to automatically setup time on your machines (and also part of the [http://www.pool.ntp.org/en/ NTP Pool Project]) |- | colspan="2" | Dictionary Server || public || Words searching system via a dedicated software (using the DICT protocol) or a Web-interface |- | rowspan="3" | Development || colspan="2" | VCS || users || Code/configuration versioning tools (Git, SVN, Baz, Bzr…) |- | rowspan="2" | Databases || SQL || users || SQL server (PostgreSQL or MySQL) |- | LDAP || users || LDAP server (OpenLDAP) |} == Shared Users Services == Even if the service is publicly accessible, and is used to share information with the world, parts of the it may be restricted by their respective owner. * [ftp://ftp.duckcorp.org/ public FTP server] (with ACLs) * [https://wiki.duckcorp.org/ public wiki] (with ACLs) * [https://projects.duckcorp.org/ public issue tracker] (with ACLs) * [https://rcs.duckcorp.org/ public VCS access] (with web viewers) * [http://debian.duckcorp.org/ public Debian repository] (needs rework) * [http://photos.duckcorp.org/ public photo gallery] (with ACLs) == Users Services == * Network facilities: ** [[Services/DNS|DNS hosting]] (NS1/NS2, DNSSEC) ** IPv6 tunnels ** [[Services/NSTX|NSTX]] (IP over DNS tunnels) * Communication facilities: ** SAFT * Application facilities: ** web hosting, with various possibilities for web programming (SSI, PHP, Perl, Python, Ruby, ...), and stats ** [[Services/Shell|shell access]] (site admin, run custom scripts, screen for text-mode geeks, ...) (for trusted users only) 5e56f854eb436f35e58de984f4bdb1cccafcbd87 243 242 2012-01-23T01:15:26Z Duck 2 wikitext text/x-wiki Here is a short overview of the services provided by DuckCorp. Our services are supervised and important data are [[Services/Backup|saved regularly]]. {{warning}} [[Services/Security|Notes about security !]] {| class="wikitable" style="text-align: center; width: 100%;" |+ Available Services |- ! Category !! colspan="2" | Service !! Access !! Description |- | rowspan="7" | Communication || rowspan="2" | Mail || [[Services/Mail|eMails]] || users || Mail boxes with anti-spam/anti-virus, filtering…, or mail redirections |- | Mailing-Lists || users || Distribution lists for mails |- | rowspan="3" | IRC || IRC Network || public || MilkyPond Chat Network using a dedicated software or a Web-interface |- | IRC Bouncer || users || [[wikipedia:IRC_bouncer#IRC|IRC proxy]] (IRC server relaying IRC communications, keeping connections open and remembering logs) |- | IRC to IM gateway || users || IRC server relaying communication to multiple instant messaging networks in a unified interface (supported network: ICQ/AIM/YM!/…, support as much networks as [[wikipedia:Pidgin_(software)#Supported_protocols|Pidgin]] + coincoin) |- | colspan="2" | XMPP (Jabber) || users || Global Chat Network (inter-communication between many [[Xmpp#History|well-known public IM services]]) |- | colspan="2" | Triboune Libre || public || MilkyPond Web-chat system inspired by [http://linuxfr.org/board the famous one] on [http://linuxfr.org/ Linuxfr.org] |- | rowspan="2" | Utilities || colspan="2" | Time Server || public || System used to automatically setup time on your machines (and also part of the [http://www.pool.ntp.org/en/ NTP Pool Project]) |- | colspan="2" | Dictionary Server || public || Words searching system via a dedicated software (using the DICT protocol) or a Web-interface |- | rowspan="3" | Development || colspan="2" | VCS || users || Code/configuration versioning tools (Git, SVN, Baz, Bzr…) |- | rowspan="2" | Databases || SQL || users || SQL server (PostgreSQL or MySQL) |- | LDAP || users || LDAP server (OpenLDAP) |- | rowspan="2" | Hosting || colspan="2" | [[Services/DNS|DNS]] || users || Domain Name System (NS1/NS2, DNSSEC…) |- | colspan="2" | [[Services/MailHosting|Mail Domains]] || users || Mail hosting (MX1/MX2) |} == Shared Users Services == Even if the service is publicly accessible, and is used to share information with the world, parts of the it may be restricted by their respective owner. * [ftp://ftp.duckcorp.org/ public FTP server] (with ACLs) * [https://wiki.duckcorp.org/ public wiki] (with ACLs) * [https://projects.duckcorp.org/ public issue tracker] (with ACLs) * [https://rcs.duckcorp.org/ public VCS access] (with web viewers) * [http://debian.duckcorp.org/ public Debian repository] (needs rework) * [http://photos.duckcorp.org/ public photo gallery] (with ACLs) == Users Services == * Network facilities: ** IPv6 tunnels ** [[Services/NSTX|NSTX]] (IP over DNS tunnels) * Communication facilities: ** SAFT * Application facilities: ** web hosting, with various possibilities for web programming (SSI, PHP, Perl, Python, Ruby, ...), and stats ** [[Services/Shell|shell access]] (site admin, run custom scripts, screen for text-mode geeks, ...) (for trusted users only) a6da56263db603c6c8c9ac27a0dcc0b1ed90e40c 246 243 2012-01-23T01:40:27Z Duck 2 wikitext text/x-wiki Here is a short overview of the services provided by DuckCorp. Our services are supervised and important data are [[Services/Backup|saved regularly]]. {{warning}} [[Services/Security|Notes about security !]] {| class="wikitable" style="text-align: center; width: 100%;" |+ Available Services |- ! Category !! colspan="2" | Service !! Access !! Description |- | rowspan="7" | Communication || rowspan="2" | Mail || [[Services/Mail|eMails]] || users || Mail boxes with anti-spam/anti-virus, filtering…, or mail redirections |- | Mailing-Lists || users || Distribution lists for mails |- | rowspan="3" | IRC || IRC Network || public || MilkyPond Chat Network using a dedicated software or a Web-interface |- | IRC Bouncer || users || [[wikipedia:IRC_bouncer#IRC|IRC proxy]] (IRC server relaying IRC communications, keeping connections open and remembering logs) |- | IRC to IM gateway || users || IRC server relaying communication to multiple instant messaging networks in a unified interface (supported network: ICQ/AIM/YM!/…, support as much networks as [[wikipedia:Pidgin_(software)#Supported_protocols|Pidgin]] + coincoin) |- | colspan="2" | XMPP (Jabber) || users || Global Chat Network (inter-communication between many [[Xmpp#History|well-known public IM services]]) |- | colspan="2" | Triboune Libre || public || MilkyPond Web-chat system inspired by [http://linuxfr.org/board the famous one] on [http://linuxfr.org/ Linuxfr.org] |- | rowspan="2" | Utilities || colspan="2" | Time Server || public || System used to automatically setup time on your machines (and also part of the [http://www.pool.ntp.org/en/ NTP Pool Project]) |- | colspan="2" | Dictionary Server || public || Words searching system via a dedicated software (using the DICT protocol) or a Web-interface |- | rowspan="3" | Development || colspan="2" | VCS || users || Code/configuration versioning tools (Git, SVN, Baz, Bzr…) |- | rowspan="2" | Databases || SQL || users || SQL server (PostgreSQL or MySQL) |- | LDAP || users || LDAP server (OpenLDAP) |- | rowspan="2" | Hosting || colspan="2" | [[Services/DNS|DNS]] || users || Domain Name System (NS1/NS2, DNSSEC…) |- | colspan="2" | [[Services/MailHosting|Mail Domains]] || users || Mail hosting (MX1/MX2) |- | rowspan="2" | Network || colspan="2" | IPv6 tunnels || users || Access to the IPv6 world through an IPv4 connection |- | colspan="2" | [[Services/NSTX|NSTX]] || users || Access to the Internet through a restricted WIFI connection (via an IP over DNS tunnel) |} == Shared Users Services == Even if the service is publicly accessible, and is used to share information with the world, parts of the it may be restricted by their respective owner. * [ftp://ftp.duckcorp.org/ public FTP server] (with ACLs) * [https://wiki.duckcorp.org/ public wiki] (with ACLs) * [https://projects.duckcorp.org/ public issue tracker] (with ACLs) * [https://rcs.duckcorp.org/ public VCS access] (with web viewers) * [http://debian.duckcorp.org/ public Debian repository] (needs rework) * [http://photos.duckcorp.org/ public photo gallery] (with ACLs) == Users Services == * Communication facilities: ** SAFT * Application facilities: ** web hosting, with various possibilities for web programming (SSI, PHP, Perl, Python, Ruby, ...), and stats ** [[Services/Shell|shell access]] (site admin, run custom scripts, screen for text-mode geeks, ...) (for trusted users only) fe35d9c5838ded1eeb252dce5b27af0ab8bb4488 247 246 2012-01-23T01:44:09Z Duck 2 wikitext text/x-wiki Here is a short overview of the services provided by DuckCorp. Our services are supervised and important data are [[Services/Backup|saved regularly]]. {{warning}} [[Services/Security|Notes about security !]] {| class="wikitable" style="text-align: center; width: 100%;" |+ Available Services |- ! Category !! colspan="2" | Service !! Access !! Description |- | rowspan="7" | Communication || rowspan="2" | Mail || [[Services/Mail|eMails]] || users || Mail boxes with anti-spam/anti-virus, filtering…, or mail redirections |- | Mailing-Lists || users || Distribution lists for mails |- | rowspan="3" | IRC || IRC Network || public || MilkyPond Chat Network using a dedicated software or a Web-interface |- | IRC Bouncer || users || [[wikipedia:IRC_bouncer#IRC|IRC proxy]] (IRC server relaying IRC communications, keeping connections open and remembering logs) |- | IRC to IM gateway || users || IRC server relaying communication to multiple instant messaging networks in a unified interface (supported network: ICQ/AIM/YM!/…, support as much networks as [[wikipedia:Pidgin_(software)#Supported_protocols|Pidgin]] + coincoin) |- | colspan="2" | XMPP (Jabber) || users || Global Chat Network (inter-communication between many [[wikipedia:Xmpp#History|well-known public IM services]]) |- | colspan="2" | Triboune Libre || public || MilkyPond Web-chat system inspired by [http://linuxfr.org/board the famous one] on [http://linuxfr.org/ Linuxfr.org] |- | rowspan="2" | Utilities || colspan="2" | Time Server || public || System used to automatically setup time on your machines (and also part of the [http://www.pool.ntp.org/en/ NTP Pool Project]) |- | colspan="2" | Dictionary Server || public || Words searching system via a dedicated software (using the DICT protocol) or a Web-interface |- | rowspan="3" | Development || colspan="2" | VCS || users || Code/configuration versioning tools (Git, SVN, Baz, Bzr…) |- | rowspan="2" | Databases || SQL || users || SQL server (PostgreSQL or MySQL) |- | LDAP || users || LDAP server (OpenLDAP) |- | rowspan="2" | Hosting || colspan="2" | [[Services/DNS|DNS]] || users || Domain Name System (NS1/NS2, DNSSEC…) |- | colspan="2" | [[Services/MailHosting|Mail Domains]] || users || Mail hosting (MX1/MX2) |- | rowspan="2" | Network || colspan="2" | IPv6 tunnels || users || Access to the IPv6 world through an IPv4 connection |- | colspan="2" | [[Services/NSTX|NSTX]] || users || Access to the Internet through a restricted WIFI connection (via an IP over DNS tunnel) |} == Shared Users Services == Even if the service is publicly accessible, and is used to share information with the world, parts of the it may be restricted by their respective owner. * [ftp://ftp.duckcorp.org/ public FTP server] (with ACLs) * [https://wiki.duckcorp.org/ public wiki] (with ACLs) * [https://projects.duckcorp.org/ public issue tracker] (with ACLs) * [https://rcs.duckcorp.org/ public VCS access] (with web viewers) * [http://debian.duckcorp.org/ public Debian repository] (needs rework) * [http://photos.duckcorp.org/ public photo gallery] (with ACLs) == Users Services == * Communication facilities: ** SAFT * Application facilities: ** web hosting, with various possibilities for web programming (SSI, PHP, Perl, Python, Ruby, ...), and stats ** [[Services/Shell|shell access]] (site admin, run custom scripts, screen for text-mode geeks, ...) (for trusted users only) b3036c2fc851fa41a5686020e876200c1b18ea31 248 247 2012-01-23T01:46:15Z Duck 2 wikitext text/x-wiki Here is a short overview of the services provided by DuckCorp. Our services are supervised and important data are [[Services/Backup|saved regularly]]. {{warning}} [[Services/Security|Notes about security !]] {| class="wikitable" style="text-align: center; width: 100%;" |+ Available Services |- ! Category !! colspan="2" | Service !! Access !! Description |- | rowspan="7" | Communication || rowspan="2" | Mail || [[Services/Mail|eMails]] || users || Mail boxes with anti-spam/anti-virus, filtering…, or mail redirections |- | Mailing-Lists || users || Distribution lists for mails |- | rowspan="3" | IRC || IRC Network || public || MilkyPond Chat Network using a dedicated software or a Web-interface |- | IRC Bouncer || users || [[wikipedia:IRC_bouncer#IRC|IRC proxy]] (IRC server relaying IRC communications, keeping connections open and remembering logs) |- | IRC to IM gateway || users || IRC server relaying communication to multiple instant messaging networks in a unified interface (supported network: ICQ/AIM/YM!/…, support as much networks as [[wikipedia:Pidgin_(software)#Supported_protocols|Pidgin]] + coincoin) |- | colspan="2" | XMPP (Jabber) || users || Global Chat Network (inter-communication between many [[wikipedia:Xmpp#History|well-known public IM services]]) |- | colspan="2" | Triboune Libre || public || MilkyPond Web-chat system inspired by [http://linuxfr.org/board the famous one] on [http://linuxfr.org/ Linuxfr.org] |- | rowspan="2" | Utilities || colspan="2" | Time Server || public || System used to automatically setup time on your machines (and also part of the [http://www.pool.ntp.org/en/ NTP Pool Project]) |- | colspan="2" | Dictionary Server || public || Words searching system via a dedicated software (using the DICT protocol) or a Web-interface |- | rowspan="3" | Development || colspan="2" | [https://rcs.duckcorp.org/ VCS] || public/users || Code/configuration versioning tools (Git, SVN, Baz, Bzr…) |- | rowspan="2" | Databases || SQL || users || SQL server (PostgreSQL or MySQL) |- | LDAP || users || LDAP server (OpenLDAP) |- | rowspan="2" | Hosting || colspan="2" | [[Services/DNS|DNS]] || users || Domain Name System (NS1/NS2, DNSSEC…) |- | colspan="2" | [[Services/MailHosting|Mail Domains]] || users || Mail hosting (MX1/MX2) |- | rowspan="2" | Network || colspan="2" | IPv6 tunnels || users || Access to the IPv6 world through an IPv4 connection |- | colspan="2" | [[Services/NSTX|NSTX]] || users || Access to the Internet through a restricted WIFI connection (via an IP over DNS tunnel) |} == Shared Users Services == Even if the service is publicly accessible, and is used to share information with the world, parts of the it may be restricted by their respective owner. * [ftp://ftp.duckcorp.org/ public FTP server] (with ACLs) * [https://wiki.duckcorp.org/ public wiki] (with ACLs) * [https://projects.duckcorp.org/ public issue tracker] (with ACLs) * [http://debian.duckcorp.org/ public Debian repository] (needs rework) * [http://photos.duckcorp.org/ public photo gallery] (with ACLs) == Users Services == * Communication facilities: ** SAFT * Application facilities: ** web hosting, with various possibilities for web programming (SSI, PHP, Perl, Python, Ruby, ...), and stats ** [[Services/Shell|shell access]] (site admin, run custom scripts, screen for text-mode geeks, ...) (for trusted users only) ea3efc0b9fbf20f0fec865ec3dd92106804eff6e 249 248 2012-01-23T02:01:51Z Duck 2 wikitext text/x-wiki Here is a short overview of the services provided by DuckCorp. Our services are supervised and important data are [[Services/Backup|saved regularly]]. {{warning}} [[Services/Security|Notes about security !]] {| class="wikitable" style="text-align: center; width: 100%;" |+ Available Services |- ! Category !! colspan="2" | Service !! Access !! Description |- | rowspan="7" | Communication || rowspan="2" | Mail || [[Services/Mail|eMails]] || users || Mail boxes with anti-spam/anti-virus, filtering…, or mail redirections |- | Mailing-Lists || users || Distribution lists for mails |- | rowspan="3" | IRC || IRC Network || public || MilkyPond Chat Network using a dedicated software or a Web-interface |- | IRC Bouncer || users || [[wikipedia:IRC_bouncer#IRC|IRC proxy]] (IRC server relaying IRC communications, keeping connections open and remembering logs) |- | IRC to IM gateway || users || IRC server relaying communication to multiple instant messaging networks in a unified interface (supported network: ICQ/AIM/YM!/…, support as much networks as [[wikipedia:Pidgin_(software)#Supported_protocols|Pidgin]] + coincoin) |- | colspan="2" | XMPP (Jabber) || users || Global Chat Network (inter-communication between many [[wikipedia:Xmpp#History|well-known public IM services]]) |- | colspan="2" | Triboune Libre || public || MilkyPond Web-chat system inspired by [http://linuxfr.org/board the famous one] on [http://linuxfr.org/ Linuxfr.org] |- | rowspan="3" | File/Media Sharing || colspan="2" | [http://photos.duckcorp.org/ Gallery] || public/users || Photo and video gallery |- | rowspan="2" | Generic || [ftp://ftp.duckcorp.org/ File Repository] || public/users || Generic file sharing system (using FTP) |- | [https://stuff.milkypond.org/ Downloads Links] || public/users || Web-based generic file sharing |- | rowspan="2" | Utilities || colspan="2" | Time Server || public || System used to automatically setup time on your machines (and also part of the [http://www.pool.ntp.org/en/ NTP Pool Project]) |- | colspan="2" | Dictionary Server || public || Words searching system via a dedicated software (using the DICT protocol) or a Web-interface |- | rowspan="3" | Development || colspan="2" | [https://rcs.duckcorp.org/ VCS] || public/users || Code/configuration versioning tools (Git, SVN, Baz, Bzr…) |- | rowspan="2" | Databases || SQL || users || SQL server (PostgreSQL or MySQL) |- | LDAP || users || LDAP server (OpenLDAP) |- | rowspan="2" | Hosting || colspan="2" | [[Services/DNS|DNS]] || users || Domain Name System (NS1/NS2, DNSSEC…) |- | colspan="2" | [[Services/MailHosting|Mail Domains]] || users || Mail hosting (MX1/MX2) |- | rowspan="2" | Network || colspan="2" | IPv6 tunnels || users || Access to the IPv6 world through an IPv4 connection |- | colspan="2" | [[Services/NSTX|NSTX]] || users || Access to the Internet through a restricted WIFI connection (via an IP over DNS tunnel) |} == TODO == * SAFT: in Services/Shell * web hosting, with various possibilities for web programming (SSI, PHP, Perl, Python, Ruby, ...), and stats * [[Services/Shell|shell access]] (site admin, run custom scripts, screen for text-mode geeks, ...) (for trusted users only) * [https://wiki.duckcorp.org/ public wiki] (with ACLs) * [https://projects.duckcorp.org/ public issue tracker] (with ACLs) * [http://debian.duckcorp.org/ public Debian repository] (needs rework) * chitchat * gossip … 19937364c8e96bbce51b50877c05438cde28d615 250 249 2012-01-23T02:10:11Z Duck 2 wikitext text/x-wiki Here is a short overview of the services provided by DuckCorp. Our services are supervised and important data are [[Services/Backup|saved regularly]]. {{warning}} [[Services/Security|Notes about security !]] {| class="wikitable" style="text-align: center; width: 100%;" |+ Available Services |- ! Category !! colspan="2" | Service !! Access !! Description |- | rowspan="7" | Communication || rowspan="2" | Mail || [[Services/Mail|eMails]] || users || Mail boxes with anti-spam/anti-virus, filtering…, or mail redirections |- | Mailing-Lists || users || Distribution lists for mails |- | rowspan="3" | IRC || IRC Network || public || MilkyPond Chat Network using a dedicated software or a Web-interface |- | IRC Bouncer || users || [[wikipedia:IRC_bouncer#IRC|IRC proxy]] (IRC server relaying IRC communications, keeping connections open and remembering logs) |- | IRC to IM gateway || users || IRC server relaying communication to multiple instant messaging networks in a unified interface (supported network: ICQ/AIM/YM!/…, support as much networks as [[wikipedia:Pidgin_(software)#Supported_protocols|Pidgin]] + coincoin) |- | colspan="2" | XMPP (Jabber) || users || Global Chat Network (inter-communication between many [[wikipedia:Xmpp#History|well-known public IM services]]) |- | colspan="2" | Triboune Libre || public || MilkyPond Web-chat system inspired by [http://linuxfr.org/board the famous one] on [http://linuxfr.org/ Linuxfr.org] |- | rowspan="4" | File/Media Sharing || colspan="2" | [http://photos.duckcorp.org/ Gallery] || public/users || Photo and video gallery |- | rowspan="3" | Generic || [ftp://ftp.duckcorp.org/ File Repository] || public/users || Generic file sharing system (using FTP) |- | [https://stuff.milkypond.org/ Downloads Links] || public/users || Web-based generic file sharing |- | Shell Transfer || users || File transfer system using the SAFT protocol (shell access needed) |- | rowspan="2" | Utilities || colspan="2" | Time Server || public || System used to automatically setup time on your machines (and also part of the [http://www.pool.ntp.org/en/ NTP Pool Project]) |- | colspan="2" | Dictionary Server || public || Words searching system via a dedicated software (using the DICT protocol) or a Web-interface |- | rowspan="3" | Development || colspan="2" | [https://rcs.duckcorp.org/ VCS] || public/users || Code/configuration versioning tools (Git, SVN, Baz, Bzr…) |- | rowspan="2" | Databases || SQL || users || SQL server (PostgreSQL or MySQL) |- | LDAP || users || LDAP server (OpenLDAP) |- | rowspan="2" | Hosting || colspan="2" | [[Services/DNS|DNS]] || users || Domain Name System (NS1/NS2, DNSSEC…) |- | colspan="2" | [[Services/MailHosting|Mail Domains]] || users || Mail hosting (MX1/MX2) |- | rowspan="2" | Network || colspan="2" | IPv6 tunnels || users || Access to the IPv6 world through an IPv4 connection |- | colspan="2" | [[Services/NSTX|NSTX]] || users || Access to the Internet through a restricted WIFI connection (via an IP over DNS tunnel) |} == TODO == * SAFT: in Services/Shell * web hosting, with various possibilities for web programming (SSI, PHP, Perl, Python, Ruby, ...), and stats * [[Services/Shell|shell access]] (site admin, run custom scripts, screen for text-mode geeks, ...) (for trusted users only) * [https://wiki.duckcorp.org/ public wiki] (with ACLs) * [https://projects.duckcorp.org/ public issue tracker] (with ACLs) * [http://debian.duckcorp.org/ public Debian repository] (needs rework) * chitchat * gossip … 3ba301e8b379b4d4eacf7d325231b903551fa51e 251 250 2012-01-23T02:17:14Z Duck 2 wikitext text/x-wiki Here is a short overview of the services provided by DuckCorp. Our services are supervised and important data are [[Services/Backup|saved regularly]]. {{warning}} [[Services/Security|Notes about security !]] {| class="wikitable" style="text-align: center; width: 100%;" |+ Available Services |- ! Category !! colspan="2" | Service !! Access !! Description |- | rowspan="7" | Communication || rowspan="2" | Mail || [[Services/Mail|eMails]] || users || Mail boxes with anti-spam/anti-virus, filtering…, or mail redirections |- | Mailing-Lists || users || Distribution lists for mails |- | rowspan="3" | IRC || IRC Network || public || MilkyPond Chat Network using a dedicated software or a Web-interface |- | IRC Bouncer || users || [[wikipedia:IRC_bouncer#IRC|IRC proxy]] (IRC server relaying IRC communications, keeping connections open and remembering logs) |- | IRC to IM gateway || users || IRC server relaying communication to multiple instant messaging networks in a unified interface (supported network: ICQ/AIM/YM!/…, support as much networks as [[wikipedia:Pidgin_(software)#Supported_protocols|Pidgin]] + coincoin) |- | colspan="2" | XMPP (Jabber) || users || Global Chat Network (inter-communication between many [[wikipedia:Xmpp#History|well-known public IM services]]) |- | colspan="2" | Triboune Libre || public || MilkyPond Web-chat system inspired by [http://linuxfr.org/board the famous one] on [http://linuxfr.org/ Linuxfr.org] |- | rowspan="4" | File/Media Sharing || colspan="2" | [http://photos.duckcorp.org/ Media Gallery] || public/users || Photo and video gallery |- | rowspan="3" | Generic || [ftp://ftp.duckcorp.org/ File Repository] || public/users || Generic file sharing system (using FTP) |- | [https://stuff.milkypond.org/ Downloads Links] || public/users || Web-based generic file sharing |- | Shell Transfer || users || File transfer system using the SAFT protocol (shell access needed) |- | rowspan="2" | Utilities || colspan="2" | Time Server || public || System used to automatically setup time on your machines (and also part of the [http://www.pool.ntp.org/en/ NTP Pool Project]) |- | colspan="2" | Dictionary Server || public || Words searching system via a dedicated software (using the DICT protocol) or a Web-interface |- | rowspan="3" | Development || colspan="2" | [https://rcs.duckcorp.org/ VCS] || public/users || Code/configuration versioning tools (Git, SVN, Baz, Bzr…) |- | rowspan="2" | Databases || SQL || users || SQL server (PostgreSQL or MySQL) |- | LDAP || users || LDAP server (OpenLDAP) |- | rowspan="3" | Hosting || colspan="2" | [[Services/DNS|DNS]] || users || Domain Name System (NS1/NS2, DNSSEC…) |- | colspan="2" | [[Services/MailHosting|Mail Domains]] || users || Mail hosting (MX1/MX2) |- | colspan="2" | Web Sites || users || Web pages using HTML/XHTML, CSS, JS, and various programming languages (SSI, PHP, Perl, Python, Ruby…), and statistics (analytics data/reports) |- | rowspan="2" | Network || colspan="2" | IPv6 tunnels || users || Access to the IPv6 world through an IPv4 connection |- | colspan="2" | [[Services/NSTX|NSTX]] || users || Access to the Internet through a restricted WIFI connection (via an IP over DNS tunnel) |} == TODO == * SAFT: in Services/Shell * [[Services/Shell|shell access]] (site admin, run custom scripts, screen for text-mode geeks, ...) (for trusted users only) * [https://wiki.duckcorp.org/ public wiki] (with ACLs) * [https://projects.duckcorp.org/ public issue tracker] (with ACLs) * [http://debian.duckcorp.org/ public Debian repository] (needs rework) * chitchat * gossip … 2f0b582b6a517709f360a9f0da84890b72a545bb 252 251 2012-01-23T02:34:05Z Duck 2 wikitext text/x-wiki Here is a short overview of the services provided by DuckCorp. Our services are supervised and important data are [[Services/Backup|saved regularly]]. {{warning}} [[Services/Security|Notes about security !]] {| class="wikitable" style="text-align: center; width: 100%;" |+ Available Services |- ! Category !! colspan="2" | Service !! Access !! Description |- | rowspan="7" | Communication || rowspan="2" | Mail || [[Services/Mail|eMails]] || users || Mail boxes with anti-spam/anti-virus, filtering…, or mail redirections |- | Mailing-Lists || users || Distribution lists for mails |- | rowspan="3" | IRC || IRC Network || public || MilkyPond Chat Network using a dedicated software or a Web-interface |- | IRC Bouncer || users || [[wikipedia:IRC_bouncer#IRC|IRC proxy]] (IRC server relaying IRC communications, keeping connections open and remembering logs) |- | IRC to IM gateway || users || IRC server relaying communication to multiple instant messaging networks in a unified interface (supported network: ICQ/AIM/YM!/…, support as much networks as [[wikipedia:Pidgin_(software)#Supported_protocols|Pidgin]] + coincoin) |- | colspan="2" | XMPP (Jabber) || users || Global Chat Network (inter-communication between many [[wikipedia:Xmpp#History|well-known public IM services]]) |- | colspan="2" | Triboune Libre || public || MilkyPond Web-chat system inspired by [http://linuxfr.org/board the famous one] on [http://linuxfr.org/ Linuxfr.org] |- | rowspan="4" | File/Media Sharing || colspan="2" | [https://photos.duckcorp.org/ Media Gallery] || public/users || Photo and video gallery |- | rowspan="3" | Generic || [ftp://ftp.duckcorp.org/ File Repository] || public/users || Generic file sharing system (using FTP) |- | [https://stuff.milkypond.org/ Downloads Links] || public/users || Web-based generic file sharing |- | Shell Transfer || trusted || File transfer system using the SAFT protocol (shell access needed) |- | rowspan="3" | Utilities || colspan="2" | [https://gossip.duckcorp.org/ News WebReader] || users | News feeds reader through a web interface |- | colspan="2" | Time Server || public || System used to automatically setup time on your machines (and also part of the [http://www.pool.ntp.org/en/ NTP Pool Project]) |- | colspan="2" | Dictionary Server || public || Words searching system via a dedicated software (using the DICT protocol) or a Web-interface |- | rowspan="3" | Development || colspan="2" | [https://projects.duckcorp.org/ Project Management & Issue Tracking] || public/users || |- | colspan="2" | [https://rcs.duckcorp.org/ VCS] || public/users || Code/configuration versioning tools (Git, SVN, Baz, Bzr…) |- | rowspan="2" | Databases || SQL || users || SQL server (PostgreSQL or MySQL) |- | LDAP || users || LDAP server (OpenLDAP) |- | rowspan="4" | Hosting || colspan="2" | [[Services/DNS|DNS]] || users || Domain Name System (NS1/NS2, DNSSEC…) |- | colspan="2" | [[Services/MailHosting|Mail Domains]] || users || Mail hosting (MX1/MX2) |- | colspan="2" | Web Sites || users || Web pages using HTML/XHTML, CSS, JS, and various programming languages (SSI, PHP, Perl, Python, Ruby…), and statistics (analytics data/reports) |- | colspan="2" | [[Services/Shell|Shell]] || trusted || Useful for website administration, development, run custom scripts, persistent applications for text-mode geeks… |- | rowspan="2" | Network || colspan="2" | IPv6 tunnels || users || Access to the IPv6 world through an IPv4 connection |- | colspan="2" | [[Services/NSTX|NSTX]] || users || Access to the Internet through a restricted WIFI connection (via an IP over DNS tunnel) |} == TODO == * [https://wiki.duckcorp.org/ public wiki] (with ACLs) * in Services/Shell: link to SAFT * in Services/XMPP: chitchat * in Services/IRC: irconweb * new debian repository (when ready) … 8e067e8f3c2a16b2f8aab74228f06994c4b91bac 0 48 225 189 2011-08-11T11:45:48Z Duck 2 wikitext text/x-wiki Besides critical system and services data, most of users data are backuped up too. Data you can expect being saved: * mails, along with antispam learning data and SIEVE filters * shared services configurations and personnal data (webmail, webdesk, projects, jabber, web stats, VCS…) * web data (hosted websites) * FTP data * /home on all machines where users can have shell access * /private on Toushirou A few files or directory names are globally excluded from backup: * cache * .Trash In your personnal data, you can choose to exclude directories (and their children), either because you don't want us to copy your data elsewhere, or because it is not needed (allowing us to save data on the backup system). To do that, you simply need to create a ''.nobackup'' empty file inside the directories to ignore, nothing more. The backup system would detect it and skip the whole directory over. 8a1a7e3d28e31af06d26178bf9d758a31eeda1bc 0 31 226 141 2011-08-11T12:01:45Z Duck 2 wikitext text/x-wiki <fdp_graph> graph DcMap { label = "DuckCorp Architecture"; fontsize = 14; overlap = false; splines = true; edge [fontsize=10.0]; labelloc = "t"; internet [label="Internet", shape=tripleoctagon]; hivane [label="Hivane\nNetwork", shape=house]; hivane -- internet [label="Hivane\nTransit", style=dashed]; subgraph cluster_nerim { label = "Nerim Suite\n(Equinix PA3 Datacenter)"; color = blue; labeljust = "l"; toushirou [label="Tōshirō", URL="DcArchitecture/Tōshirō"]; thorfinn [label="Thorfinn\n(Nerim Root VDS)", URL="DcArchitecture/Thorfinn"]; } cluster_nerim -- hivane [label="Nerim / Hivane\nPeering", style=dashed]; subgraph cluster_alionis { label = "Alionis Suite\n(Villebon Datacenter)"; URL = "http://maps.google.com/maps/ms?ie=UTF8&hl=en&msa=0&msid=105368272885926046620.0004600d15bf1a76aa1a9&t=h&z=15"; color = black; labeljust = "l"; orfeo [label="Orfeo", URL="DcArchitecture/Orfeo"]; } cluster_alionis -- hivane [label="Hivane / Alionis\nPeering", style=dashed]; subgraph cluster_hq { label = "DuckCorp HQ (DuckLand)"; color = green; labeljust = "l"; elwing [label="Elwing", URL="DcArchitecture/Elwing"]; daneel [label="Daneel", URL="DcArchitecture/Daneel"]; earendil [label="Eärendil", URL="DcArchitecture/Eärendil"]; modem_dc [label="ADSL Modem\n(Linksys ADSL2MUE)", shape=box]; sw_dc [label="Switch", shape=box]; sw_dc -- {elwing earendil daneel}; elwing -- {modem_dc}; subgraph cluster_hurdfr { label = "HurdFr (DuckLand part)"; URL = "http://www.hurdfr.org/"; color = darkviolet; labeljust = "l"; amroth [label="Amroth", URL="DcArchitecture/Amroth"]; } amroth -- sw_dc; } cluster_hq -- hivane [label="Nerim / Hivane\nADSL", style=dashed]; subgraph cluster_frontier { label = "Frontier Housing"; color = orange; labeljust = "l"; jinta [label="Jinta\n(vserver)", URL="DcArchitecture/Jinta"]; } cluster_frontier -- internet [style=dashed]; } <fdp_graph> 02d3e52a314e371c5fc85de80d5ee2809927ffc2 227 226 2011-08-11T12:11:47Z Duck 2 wikitext text/x-wiki <fdp_graph> graph DcMap { label = "DuckCorp Architecture"; fontsize = 13; overlap = false; splines = true; edge [fontsize=10.0]; style = bold; node [fontsize=10.0]; labelloc = "t"; internet [label="Internet", fontsize=14, shape=tripleoctagon]; hivane [label="Hivane\nNetwork", fontsize=14, shape=house]; hivane -- internet [label="Hivane\nTransit", style=dashed]; subgraph cluster_nerim { label = "Nerim Suite\n(Equinix PA3 Datacenter)"; color = blue; labeljust = "l"; toushirou [label="Tōshirō", URL="DcArchitecture/Tōshirō"]; thorfinn [label="Thorfinn\n(Nerim Root VDS)", URL="DcArchitecture/Thorfinn"]; } cluster_nerim -- hivane [label="Nerim / Hivane\nPeering", style=dashed]; subgraph cluster_alionis { label = "Alionis Suite\n(Villebon Datacenter)"; URL = "http://maps.google.com/maps/ms?ie=UTF8&hl=en&msa=0&msid=105368272885926046620.0004600d15bf1a76aa1a9&t=h&z=15"; color = black; labeljust = "l"; orfeo [label="Orfeo", URL="DcArchitecture/Orfeo"]; } cluster_alionis -- hivane [label="Hivane / Alionis\nPeering", style=dashed]; subgraph cluster_hq { label = "DuckCorp HQ (DuckLand)"; color = green; labeljust = "l"; elwing [label="Elwing", URL="DcArchitecture/Elwing"]; daneel [label="Daneel", URL="DcArchitecture/Daneel"]; earendil [label="Eärendil", URL="DcArchitecture/Eärendil"]; modem_dc [label="ADSL Modem\n(Linksys ADSL2MUE)", shape=box]; sw_dc [label="Switch", shape=box]; sw_dc -- {elwing earendil daneel}; elwing -- {modem_dc}; subgraph cluster_hurdfr { label = "HurdFr (DuckLand part)"; URL = "http://www.hurdfr.org/"; color = darkviolet; labeljust = "l"; amroth [label="Amroth", URL="DcArchitecture/Amroth"]; } amroth -- sw_dc; } cluster_hq -- hivane [label="Nerim / Hivane\nADSL", style=dashed]; subgraph cluster_frontier { label = "Frontier Housing"; color = orange; labeljust = "l"; jinta [label="Jinta\n(vserver)", URL="DcArchitecture/Jinta"]; } cluster_frontier -- internet [style=dashed]; } <fdp_graph> 87f180de90b6b536cbfea5212c2f75a4478ddf4e 228 227 2011-08-11T12:14:28Z Duck 2 wikitext text/x-wiki <fdp_graph> graph DcMap { label = "DuckCorp Architecture"; fontsize = 13; overlap = false; splines = true; edge [fontsize=10.0]; style = bold; node [fontsize=10.0]; labelloc = "t"; internet [label="Internet", fontsize=14, shape=tripleoctagon]; hivane [label="Hivane\nNetwork", fontsize=14, shape=house]; hivane -- internet [label="Hivane\nTransit", style=dashed]; subgraph cluster_hq { label = "DuckCorp HQ (DuckLand)"; color = green; labeljust = "l"; elwing [label="Elwing", URL="DcArchitecture/Elwing"]; daneel [label="Daneel", URL="DcArchitecture/Daneel"]; earendil [label="Eärendil", URL="DcArchitecture/Eärendil"]; modem_dc [label="ADSL Modem\n(Linksys ADSL2MUE)", shape=box]; sw_dc [label="Switch", shape=box]; sw_dc -- {elwing earendil daneel}; elwing -- {modem_dc}; subgraph cluster_hurdfr { label = "HurdFr (DuckLand part)"; URL = "http://www.hurdfr.org/"; color = darkviolet; labeljust = "l"; amroth [label="Amroth", URL="DcArchitecture/Amroth"]; } amroth -- sw_dc; } cluster_hq -- hivane [label="Nerim / Hivane\nADSL", style=dashed]; subgraph cluster_alionis { label = "Alionis Suite\n(Villebon Datacenter)"; URL = "http://maps.google.com/maps/ms?ie=UTF8&hl=en&msa=0&msid=105368272885926046620.0004600d15bf1a76aa1a9&t=h&z=15"; color = black; labeljust = "l"; orfeo [label="Orfeo", URL="DcArchitecture/Orfeo"]; } cluster_alionis -- hivane [label="Hivane / Alionis\nPeering", style=dashed]; subgraph cluster_frontier { label = "Frontier Housing"; color = orange; labeljust = "l"; jinta [label="Jinta\n(vserver)", URL="DcArchitecture/Jinta"]; } cluster_frontier -- internet [style=dashed]; subgraph cluster_nerim { label = "Nerim Suite\n(Equinix PA3 Datacenter)"; color = blue; labeljust = "l"; toushirou [label="Tōshirō", URL="DcArchitecture/Tōshirō"]; thorfinn [label="Thorfinn\n(Nerim Root VDS)", URL="DcArchitecture/Thorfinn"]; } cluster_nerim -- hivane [label="Nerim / Hivane\nPeering", style=dashed]; } <fdp_graph> 44233eac273c20c83683646fc1729a380edf92d2 0 50 230 2012-01-22T18:08:35Z Duck 2 Created page with "== Remote Access == Via SSH with a RSA/DSA key on the fillowing hosts: * thorfinn.duckcorp.org (prefered for lengthy sessions, like screens) * toushirou.duckcorp.org (mostly use…" wikitext text/x-wiki == Remote Access == Via SSH with a RSA/DSA key on the fillowing hosts: * thorfinn.duckcorp.org (prefered for lengthy sessions, like screens) * toushirou.duckcorp.org (mostly useful to manage Web/FTP data) == Available Resources == The following resources are available and will remain until we advertise a scheduled removal. If you miss something you can send us a request. === Locales === * en_GB.UTF-8 * en_US.UTF-8 * fr_FR.UTF-8 * ja_JP.EUC-JP * ja_JP.UTF-8 === Programs === * weechat (with plugins) * irssi (with plugins) * mcabber 610e9c8314095f6b09990f32ad3f5891bdae1a3a 231 230 2012-01-22T18:21:56Z Duck 2 /* Available Resources */ wikitext text/x-wiki == Remote Access == Via SSH with a RSA/DSA key on the fillowing hosts: * thorfinn.duckcorp.org (prefered for lengthy sessions, like screens) * toushirou.duckcorp.org (mostly useful to manage Web/FTP data) == Available Resources == The following resources are available and will remain until we advertise a scheduled removal. If you miss something you can send us a request. === Locales === * en_GB.UTF-8 * en_US.UTF-8 * fr_FR.UTF-8 * ja_JP.EUC-JP * ja_JP.UTF-8 == Shells == * dash * bash * zsh * ksh * tcsh === Programs === * weechat (with plugins) * irssi (with plugins) * mcabber b1794c84dc0660d8659d74045e4709b430613026 232 231 2012-01-22T19:18:11Z Duck 2 /* Shells */ wikitext text/x-wiki == Remote Access == Via SSH with a RSA/DSA key on the fillowing hosts: * thorfinn.duckcorp.org (prefered for lengthy sessions, like screens) * toushirou.duckcorp.org (mostly useful to manage Web/FTP data) == Available Resources == The following resources are available and will remain until we advertise a scheduled removal. If you miss something you can send us a request. === Locales === * en_GB.UTF-8 * en_US.UTF-8 * fr_FR.UTF-8 * ja_JP.EUC-JP * ja_JP.UTF-8 === Shells === * dash * bash * zsh * ksh * tcsh === Programs === * weechat (with plugins) * irssi (with plugins) * mcabber aec5754d1a10e3a937b95368fb49983c58a8cdab 233 232 2012-01-22T20:28:46Z Duck 2 /* Programs */ wikitext text/x-wiki == Remote Access == Via SSH with a RSA/DSA key on the fillowing hosts: * thorfinn.duckcorp.org (prefered for lengthy sessions, like screens) * toushirou.duckcorp.org (mostly useful to manage Web/FTP data) == Available Resources == The following resources are available and will remain until we advertise a scheduled removal. If you miss something you can send us a request. === Locales === * en_GB.UTF-8 * en_US.UTF-8 * fr_FR.UTF-8 * ja_JP.EUC-JP * ja_JP.UTF-8 === Shells === * dash * bash * zsh * ksh * tcsh === Programs === * aspell * dict * emacs * irssi (with plugins) * latex (with xetex) * mcabber * sieve-connect * w3m * weechat (with plugins) Additional tools: * [[Services/VCS|VCS tools]] 32ea6e4589afd992c5f313de3d8d4250cd7d2156 234 233 2012-01-22T20:30:20Z Duck 2 /* Programs */ wikitext text/x-wiki == Remote Access == Via SSH with a RSA/DSA key on the fillowing hosts: * thorfinn.duckcorp.org (prefered for lengthy sessions, like screens) * toushirou.duckcorp.org (mostly useful to manage Web/FTP data) == Available Resources == The following resources are available and will remain until we advertise a scheduled removal. If you miss something you can send us a request. === Locales === * en_GB.UTF-8 * en_US.UTF-8 * fr_FR.UTF-8 * ja_JP.EUC-JP * ja_JP.UTF-8 === Shells === * dash * bash * zsh * ksh * tcsh === Programs === * aspell * dict * emacs * irssi (with plugins) * latex (with xetex) * mcabber * sieve-connect * w3m * weechat (with plugins) * vim Additional tools: * [[Services/VCS|VCS tools]] 7ab0dbc1745a1035f5755e61bc46dc7e15fe4114 235 234 2012-01-22T20:30:37Z Duck 2 /* Programs */ wikitext text/x-wiki == Remote Access == Via SSH with a RSA/DSA key on the fillowing hosts: * thorfinn.duckcorp.org (prefered for lengthy sessions, like screens) * toushirou.duckcorp.org (mostly useful to manage Web/FTP data) == Available Resources == The following resources are available and will remain until we advertise a scheduled removal. If you miss something you can send us a request. === Locales === * en_GB.UTF-8 * en_US.UTF-8 * fr_FR.UTF-8 * ja_JP.EUC-JP * ja_JP.UTF-8 === Shells === * dash * bash * zsh * ksh * tcsh === Programs === * aspell * dict * emacs * irssi (with plugins) * latex (with xetex) * mcabber * screen * sieve-connect * w3m * weechat (with plugins) * vim Additional tools: * [[Services/VCS|VCS tools]] 385d382b40ff6ac7d5e0a4e2477e1e7e1bc1da06 236 235 2012-01-22T22:30:09Z Duck 2 /* Programs */ wikitext text/x-wiki == Remote Access == Via SSH with a RSA/DSA key on the fillowing hosts: * thorfinn.duckcorp.org (prefered for lengthy sessions, like screens) * toushirou.duckcorp.org (mostly useful to manage Web/FTP data) == Available Resources == The following resources are available and will remain until we advertise a scheduled removal. If you miss something you can send us a request. === Locales === * en_GB.UTF-8 * en_US.UTF-8 * fr_FR.UTF-8 * ja_JP.EUC-JP * ja_JP.UTF-8 === Shells === * dash * bash * zsh * ksh * tcsh === Programs === * aspell * dict * emacs * irssi (with plugins) * latex (with xetex) * screen * sieve-connect * w3m * weechat (with plugins) * vim Additional tools: * [[Services/VCS|VCS tools]] 66a1412548e9ccdfe8c32415da9617d414942176 237 236 2012-01-22T22:30:36Z Duck 2 /* Programs */ wikitext text/x-wiki == Remote Access == Via SSH with a RSA/DSA key on the fillowing hosts: * thorfinn.duckcorp.org (prefered for lengthy sessions, like screens) * toushirou.duckcorp.org (mostly useful to manage Web/FTP data) == Available Resources == The following resources are available and will remain until we advertise a scheduled removal. If you miss something you can send us a request. === Locales === * en_GB.UTF-8 * en_US.UTF-8 * fr_FR.UTF-8 * ja_JP.EUC-JP * ja_JP.UTF-8 === Shells === * dash * bash * zsh * ksh * tcsh === Programs === * aspell * dict * emacs * irssi (with plugins) * latex (full TeXlive) * screen * sieve-connect * w3m * weechat (with plugins) * vim Additional tools: * [[Services/VCS|VCS tools]] ce7e74fe00b329916c4c08570861ba1f255a8bca 0 51 244 2012-01-23T01:26:40Z Duck 2 Created page with "What we can offer: * full hosting (MX1) on our servers * fallback retention (MX2) on our servers or, at your choice, partner servers (currently via Hivane) == Full Hosting == Y…" wikitext text/x-wiki What we can offer: * full hosting (MX1) on our servers * fallback retention (MX2) on our servers or, at your choice, partner servers (currently via Hivane) == Full Hosting == You can have multiple email addresses which can be: * real mailboxes * redirections towards third party addresses * wildcards based on your domains or sub-domains. Have a look at our [[Services/Mail|complete set of mail services]]. == Fallback retention == The current retention period on our servers is 2 weeks, but can be temporary or permanently increased if needed. Mails flowing back to your primary server can be protected using TLS with certificate verification if you wish. Antivirus and antispam filtering are not applied to relayed mails, so we do not mess with your prefered strategy on your primary server, nevertheless basic checks (EHLO, DNS…) and RBL scoring are done to avoid accepting tons of SPAMs. 88e91358dcfaa1b463abcb0d177255115fd53f46 0 39 253 252 2012-01-23T02:37:24Z Duck 2 wikitext text/x-wiki Here is a short overview of the services provided by DuckCorp. Our services are supervised and important data are [[Services/Backup|saved regularly]]. {{warning}} [[Services/Security|Notes about security !]] {| class="wikitable" style="text-align: center; width: 100%;" |+ Available Services |- ! Category !! colspan="2" | Service !! Access !! Description |- | rowspan="7" | Communication || rowspan="2" | Mail || [[Services/Mail|eMails]] || users || Mail boxes with anti-spam/anti-virus, filtering…, or mail redirections |- | Mailing-Lists || users || Distribution lists for mails |- | rowspan="3" | IRC || IRC Network || public || MilkyPond Chat Network using a dedicated software or a Web-interface |- | IRC Bouncer || users || [[wikipedia:IRC_bouncer#IRC|IRC proxy]] (IRC server relaying IRC communications, keeping connections open and remembering logs) |- | IRC to IM gateway || users || IRC server relaying communication to multiple instant messaging networks in a unified interface (supported network: ICQ/AIM/YM!/…, support as much networks as [[wikipedia:Pidgin_(software)#Supported_protocols|Pidgin]] + coincoin) |- | colspan="2" | XMPP (Jabber) || users || Global Chat Network (inter-communication between many [[wikipedia:Xmpp#History|well-known public IM services]]) |- | colspan="2" | Triboune Libre || public || MilkyPond Web-chat system inspired by [http://linuxfr.org/board the famous one] on [http://linuxfr.org/ Linuxfr.org] |- | rowspan="4" | File/Media Sharing || colspan="2" | [https://photos.duckcorp.org/ Media Gallery] || public/users || Photo and video gallery |- | rowspan="3" | Generic || [ftp://ftp.duckcorp.org/ File Repository] || public/users || Generic file sharing system (using FTP) |- | [https://stuff.milkypond.org/ Downloads Links] || public/users || Web-based generic file sharing |- | Shell Transfer || trusted || File transfer system using the SAFT protocol (shell access needed) |- | rowspan="3" | Utilities || colspan="2" | [https://gossip.duckcorp.org/ News WebReader] || users | News feeds reader through a web interface |- | colspan="2" | Time Server || public || System used to automatically setup time on your machines (and also part of the [http://www.pool.ntp.org/en/ NTP Pool Project]) |- | colspan="2" | Dictionary Server || public || Words searching system via a dedicated software (using the DICT protocol) or a Web-interface |- | rowspan="4" | Development || colspan="2" | [https://projects.duckcorp.org/ Project Management & Issue Tracking] || public/users || |- | colspan="2" | [https://rcs.duckcorp.org/ VCS] || public/users || Code/configuration versioning tools (Git, SVN, Baz, Bzr…) |- | rowspan="2" | Databases || SQL || users || SQL server (PostgreSQL or MySQL) |- | LDAP || users || LDAP server (OpenLDAP) |- | rowspan="5" | Hosting || colspan="2" | [[Services/DNS|DNS]] || users || Domain Name System (NS1/NS2, DNSSEC…) |- | colspan="2" | [[Services/MailHosting|Mail Domains]] || users || Mail hosting (MX1/MX2) |- | colspan="2" | Web Sites || users || Web pages using HTML/XHTML, CSS, JS, and various programming languages (SSI, PHP, Perl, Python, Ruby…), and statistics (analytics data/reports) |- | colspan="2" | XMPP Domains || users || XMPP Node for a custom domain |- | colspan="2" | [[Services/Shell|Shell]] || trusted || Useful for website administration, development, run custom scripts, persistent applications for text-mode geeks… |- | rowspan="2" | Network || colspan="2" | IPv6 tunnels || users || Access to the IPv6 world through an IPv4 connection |- | colspan="2" | [[Services/NSTX|NSTX]] || users || Access to the Internet through a restricted WIFI connection (via an IP over DNS tunnel) |} == TODO == * [https://wiki.duckcorp.org/ public wiki] (with ACLs) * in Services/Shell: link to SAFT * in Services/XMPP: chitchat * in Services/IRC: irconweb * new debian repository (when ready) … 2d5ea8a7581787a1657842297c3cfe364d6f3175 254 253 2012-01-23T02:41:32Z Duck 2 wikitext text/x-wiki Here is a short overview of the services provided by DuckCorp. Our services are supervised and important data are [[Services/Backup|saved regularly]]. {{warning}} [[Services/Security|Notes about security !]] {| class="wikitable" style="text-align: center; width: 100%;" |+ Available Services |- ! Category !! colspan="2" | Service !! Access !! Description |- | rowspan="7" | Communication || rowspan="2" | Mail || [[Services/Mail|eMails]] || users || Mail boxes with anti-spam/anti-virus, filtering…, or mail redirections |- | Mailing-Lists || users || Distribution lists for mails |- | rowspan="3" | IRC || IRC Network || public || MilkyPond Chat Network using a dedicated software or a Web-interface |- | IRC Bouncer || users || [[wikipedia:IRC_bouncer#IRC|IRC proxy]] (IRC server relaying IRC communications, keeping connections open and remembering logs) |- | IRC to IM gateway || users || IRC server relaying communication to multiple instant messaging networks in a unified interface (supported network: ICQ/AIM/YM!/…, support as much networks as [[wikipedia:Pidgin_(software)#Supported_protocols|Pidgin]] + coincoin) |- | colspan="2" | XMPP (Jabber) || users || Global Chat Network (inter-communication between many [[wikipedia:Xmpp#History|well-known public IM services]]) |- | colspan="2" | Triboune Libre || public || MilkyPond Web-chat system inspired by [http://linuxfr.org/board the famous one] on [http://linuxfr.org/ Linuxfr.org] |- | rowspan="4" | File/Media Sharing || colspan="2" | [https://photos.duckcorp.org/ Media Gallery] || public/users || Photo and video gallery |- | rowspan="3" | Generic || [ftp://ftp.duckcorp.org/ File Repository] || public/users || Generic file sharing system (using FTP) |- | [https://stuff.milkypond.org/ Downloads Links] || public/users || Web-based generic file sharing |- | Shell Transfer || trusted || File transfer system using the SAFT protocol (shell access needed) |- | rowspan="3" | Utilities || colspan="2" | [https://gossip.duckcorp.org/ News WebReader] || users || News feeds reader through a web interface |- | colspan="2" | Time Server || public || System used to automatically setup time on your machines (and also part of the [http://www.pool.ntp.org/en/ NTP Pool Project]) |- | colspan="2" | Dictionary Server || public || Words searching system via a dedicated software (using the DICT protocol) or a Web-interface |- | rowspan="4" | Development || colspan="2" | [https://projects.duckcorp.org/ Project Management & Issue Tracking] || public/users || |- | colspan="2" | [https://rcs.duckcorp.org/ VCS] || public/users || Code/configuration versioning tools (Git, SVN, Baz, Bzr…) |- | rowspan="2" | Databases || SQL || users || SQL server (PostgreSQL or MySQL) |- | LDAP || users || LDAP server (OpenLDAP) |- | rowspan="5" | Hosting || colspan="2" | [[Services/DNS|DNS]] || users || Domain Name System (NS1/NS2, DNSSEC…) |- | colspan="2" | [[Services/MailHosting|Mail Domains]] || users || Mail hosting (MX1/MX2) |- | colspan="2" | Web Sites || users || Web pages using HTML/XHTML, CSS, JS, and various programming languages (SSI, PHP, Perl, Python, Ruby…), and statistics (analytics data/reports) |- | colspan="2" | XMPP Domains || users || XMPP Node for a custom domain |- | colspan="2" | [[Services/Shell|Shell]] || trusted || Useful for website administration, development, run custom scripts, persistent applications for text-mode geeks… |- | rowspan="2" | Network || colspan="2" | IPv6 tunnels || users || Access to the IPv6 world through an IPv4 connection |- | colspan="2" | [[Services/NSTX|NSTX]] || users || Access to the Internet through a restricted WIFI connection (via an IP over DNS tunnel) |} == TODO == * [https://wiki.duckcorp.org/ public wiki] (with ACLs) * in Services/Shell: link to SAFT * in Services/XMPP: chitchat * in Services/IRC: irconweb * new debian repository (when ready) … 85ad87f51118ef87f9a08dc9fc98559f7ab9d233 255 254 2012-01-23T02:44:23Z Duck 2 wikitext text/x-wiki Here is a short overview of the services provided by DuckCorp. Our services are supervised and important data are [[Services/Backup|saved regularly]]. {{warning}} [[Services/Security|Notes about security !]] {| class="wikitable" style="text-align: center; width: 100%;" |+ Available Services |- ! Category !! colspan="2" | Service !! Access !! Description |- | rowspan="7" | Communication || rowspan="2" | Mail || [[Services/Mail|eMails]] || users || Mail boxes with anti-spam/anti-virus, filtering…, or mail redirections |- | Mailing-Lists || users || Distribution lists for mails |- | rowspan="3" | IRC || IRC Network || public || MilkyPond Chat Network using a dedicated software or a Web-interface |- | IRC Bouncer || users || [[wikipedia:IRC_bouncer#IRC|IRC proxy]] (IRC server relaying IRC communications, keeping connections open and remembering logs) |- | IRC to IM gateway || users || IRC server relaying communication to multiple instant messaging networks in a unified interface (supported network: ICQ/AIM/YM!/…, support as much networks as [[wikipedia:Pidgin_(software)#Supported_protocols|Pidgin]] + coincoin) |- | colspan="2" | XMPP (Jabber) || users || Global Chat Network (inter-communication between many [[wikipedia:Xmpp#History|well-known public IM services]]) |- | colspan="2" | Triboune Libre || public || MilkyPond Web-chat system inspired by [http://linuxfr.org/board the famous one] on [http://linuxfr.org/ Linuxfr.org] |- | rowspan="4" | File/Media Sharing || colspan="2" | [https://photos.duckcorp.org/ Media Gallery] || public/users || Photo and video gallery |- | rowspan="3" | Generic || [ftp://ftp.duckcorp.org/ File Repository] || public/users || Generic file sharing system (using FTP) |- | [https://stuff.milkypond.org/ Downloads Links] || public/users || Web-based generic file sharing |- | Shell Transfer || trusted || File transfer system using the SAFT protocol (shell access needed) |- | rowspan="3" | Utilities || colspan="2" | [https://gossip.duckcorp.org/ News WebReader] || users || News feeds reader through a web interface |- | colspan="2" | Time Server || public || System used to automatically setup time on your machines (and also part of the [http://www.pool.ntp.org/en/ NTP Pool Project]) |- | colspan="2" | Dictionary Server || public || Words searching system via a dedicated software (using the DICT protocol) or a Web-interface |- | rowspan="4" | Development || colspan="2" | [https://projects.duckcorp.org/ Project Management & Issue Tracking] || public/users || |- | colspan="2" | [https://rcs.duckcorp.org/ VCS] || public/users || Code/configuration versioning tools (Git, SVN, Baz, Bzr…) |- | rowspan="2" | Databases || SQL || users || SQL server (PostgreSQL or MySQL) |- | LDAP || users || LDAP server (OpenLDAP) |- | rowspan="5" | Hosting || colspan="2" | [[Services/DNS|DNS]] || users || Domain Name System (NS1/NS2, DNSSEC…) |- | colspan="2" | [[Services/MailHosting|Mail Domains]] || users || Mail hosting (MX1/MX2) |- | colspan="2" | Web Sites/Applications || users || Web pages using HTML/XHTML, CSS, JS, and various server-side programming languages (SSI, PHP, Perl, Python, Ruby…), and statistics (analytics data/reports) |- | colspan="2" | XMPP Domains || users || XMPP Node for a custom domain |- | colspan="2" | [[Services/Shell|Shell]] || trusted || Useful for website administration, development, run custom scripts, persistent applications for text-mode geeks… |- | rowspan="2" | Network || colspan="2" | IPv6 tunnels || users || Access to the IPv6 world through an IPv4 connection |- | colspan="2" | [[Services/NSTX|NSTX]] || users || Access to the Internet through a restricted WIFI connection (via an IP over DNS tunnel) |} == TODO == * [https://wiki.duckcorp.org/ public wiki] (with ACLs) * in Services/Shell: link to SAFT * in Services/XMPP: chitchat * in Services/IRC: irconweb * new debian repository (when ready) … 068d8944cb776b39b5e2624fa7f0e6e41a363b04 261 255 2012-01-23T22:33:34Z Duck 2 wikitext text/x-wiki Here is a short overview of the services provided by DuckCorp. Our services are supervised and important data are [[Services/Backup|saved regularly]]. {{warning}} [[Services/Security|Notes about security !]] {| class="wikitable" style="text-align: center; width: 100%;" |+ Available Services |- ! Category !! colspan="2" | Service !! Access !! Description |- | rowspan="7" | Communication || rowspan="2" | Mail || [[Services/Mail|eMails]] || users || Mail boxes with anti-spam/anti-virus, filtering…, or mail redirections |- | Mailing-Lists || users || Distribution lists for mails |- | rowspan="3" | IRC || IRC Network || public || MilkyPond Chat Network using a dedicated software or a Web-interface |- | IRC Bouncer || users || [[wikipedia:IRC_bouncer#IRC|IRC proxy]] (IRC server relaying IRC communications, keeping connections open and remembering logs) |- | IRC to IM gateway || users || IRC server relaying communication to multiple instant messaging networks in a unified interface (supported network: ICQ/AIM/YM!/…, support as much networks as [[wikipedia:Pidgin_(software)#Supported_protocols|Pidgin]] + coincoin) |- | colspan="2" | XMPP (Jabber) || users || Global Chat Network (inter-communication between many [[wikipedia:Xmpp#History|well-known public IM services]]) |- | colspan="2" | Triboune Libre || public || MilkyPond Web-chat system inspired by [http://linuxfr.org/board the famous one] on [http://linuxfr.org/ Linuxfr.org] |- | rowspan="4" | File/Media Sharing || colspan="2" | [[Services/Gallery|Media Gallery]] || public/users || Photo and video gallery |- | rowspan="3" | Generic || [ftp://ftp.duckcorp.org/ File Repository] || public/users || Generic file sharing system (using FTP) |- | [https://stuff.milkypond.org/ Downloads Links] || public/users || Web-based generic file sharing |- | Shell Transfer || trusted || File transfer system using the SAFT protocol (shell access needed) |- | rowspan="3" | Utilities || colspan="2" | [https://gossip.duckcorp.org/ News WebReader] || users || News feeds reader through a web interface |- | colspan="2" | Time Server || public || System used to automatically setup time on your machines (and also part of the [http://www.pool.ntp.org/en/ NTP Pool Project]) |- | colspan="2" | Dictionary Server || public || Words searching system via a dedicated software (using the DICT protocol) or a Web-interface |- | rowspan="4" | Development || colspan="2" | [https://projects.duckcorp.org/ Project Management & Issue Tracking] || public/users || |- | colspan="2" | [https://rcs.duckcorp.org/ VCS] || public/users || Code/configuration versioning tools (Git, SVN, Baz, Bzr…) |- | rowspan="2" | Databases || SQL || users || SQL server (PostgreSQL or MySQL) |- | LDAP || users || LDAP server (OpenLDAP) |- | rowspan="5" | Hosting || colspan="2" | [[Services/DNS|DNS]] || users || Domain Name System (NS1/NS2, DNSSEC…) |- | colspan="2" | [[Services/MailHosting|Mail Domains]] || users || Mail hosting (MX1/MX2) |- | colspan="2" | Web Sites/Applications || users || Web pages using HTML/XHTML, CSS, JS, and various server-side programming languages (SSI, PHP, Perl, Python, Ruby…), and statistics (analytics data/reports) |- | colspan="2" | XMPP Domains || users || XMPP Node for a custom domain |- | colspan="2" | [[Services/Shell|Shell]] || trusted || Useful for website administration, development, run custom scripts, persistent applications for text-mode geeks… |- | rowspan="2" | Network || colspan="2" | IPv6 tunnels || users || Access to the IPv6 world through an IPv4 connection |- | colspan="2" | [[Services/NSTX|NSTX]] || users || Access to the Internet through a restricted WIFI connection (via an IP over DNS tunnel) |} == TODO == * [https://wiki.duckcorp.org/ public wiki] (with ACLs) * in Services/Shell: link to SAFT * in Services/XMPP: chitchat * in Services/IRC: irconweb * new debian repository (when ready) … 44155dc0a88d11f729abf265d98ae4c5fce8910f 270 261 2012-01-23T23:01:16Z Duck 2 wikitext text/x-wiki Here is a short overview of the services provided by DuckCorp. Our services are supervised and important data are [[Services/Backup|saved regularly]]. {{warning}} [[Services/Security|Notes about security !]] {| class="wikitable" style="text-align: center; width: 100%;" |+ Available Services |- ! Category !! colspan="2" | Service !! Access !! Description |- | rowspan="7" | Communication || rowspan="2" | Mail || [[Services/Mail|eMails]] || users || Mail boxes with anti-spam/anti-virus, filtering…, or mail redirections |- | Mailing-Lists || users || Distribution lists for mails |- | rowspan="3" | IRC || IRC Network || public || MilkyPond Chat Network using a dedicated software or a Web-interface |- | IRC Bouncer || users || [[wikipedia:IRC_bouncer#IRC|IRC proxy]] (IRC server relaying IRC communications, keeping connections open and remembering logs) |- | IRC to IM gateway || users || IRC server relaying communication to multiple instant messaging networks in a unified interface (supported network: ICQ/AIM/YM!/…, support as much networks as [[wikipedia:Pidgin_(software)#Supported_protocols|Pidgin]] + coincoin) |- | colspan="2" | XMPP (Jabber) || users || Global Chat Network (inter-communication between many [[wikipedia:Xmpp#History|well-known public IM services]]) |- | colspan="2" | Triboune Libre || public || MilkyPond Web-chat system inspired by [http://linuxfr.org/board the famous one] on [http://linuxfr.org/ Linuxfr.org] |- | rowspan="4" | File/Media Sharing || colspan="2" | [[Services/Gallery|Media Gallery]] || public/users || Photo and video gallery |- | rowspan="3" | Generic || [[Services/FTP|File Repository]] || public/users || Generic file sharing system (using FTP) |- | [https://stuff.milkypond.org/ Downloads Links] || public/users || Web-based generic file sharing |- | Shell Transfer || trusted || File transfer system using the SAFT protocol (shell access needed) |- | rowspan="3" | Utilities || colspan="2" | [https://gossip.duckcorp.org/ News WebReader] || users || News feeds reader through a web interface |- | colspan="2" | Time Server || public || System used to automatically setup time on your machines (and also part of the [http://www.pool.ntp.org/en/ NTP Pool Project]) |- | colspan="2" | Dictionary Server || public || Words searching system via a dedicated software (using the DICT protocol) or a Web-interface |- | rowspan="4" | Development || colspan="2" | [https://projects.duckcorp.org/ Project Management & Issue Tracking] || public/users || |- | colspan="2" | [https://rcs.duckcorp.org/ VCS] || public/users || Code/configuration versioning tools (Git, SVN, Baz, Bzr…) |- | rowspan="2" | Databases || SQL || users || SQL server (PostgreSQL or MySQL) |- | LDAP || users || LDAP server (OpenLDAP) |- | rowspan="5" | Hosting || colspan="2" | [[Services/DNS|DNS]] || users || Domain Name System (NS1/NS2, DNSSEC…) |- | colspan="2" | [[Services/MailHosting|Mail Domains]] || users || Mail hosting (MX1/MX2) |- | colspan="2" | Web Sites/Applications || users || Web pages using HTML/XHTML, CSS, JS, and various server-side programming languages (SSI, PHP, Perl, Python, Ruby…), and statistics (analytics data/reports) |- | colspan="2" | XMPP Domains || users || XMPP Node for a custom domain |- | colspan="2" | [[Services/Shell|Shell]] || trusted || Useful for website administration, development, run custom scripts, persistent applications for text-mode geeks… |- | rowspan="2" | Network || colspan="2" | IPv6 tunnels || users || Access to the IPv6 world through an IPv4 connection |- | colspan="2" | [[Services/NSTX|NSTX]] || users || Access to the Internet through a restricted WIFI connection (via an IP over DNS tunnel) |} == TODO == * [https://wiki.duckcorp.org/ public wiki] (with ACLs) * in Services/Shell: link to SAFT * in Services/XMPP: chitchat * in Services/IRC: irconweb * new debian repository (when ready) … ce596afb71343c27794f56a5ffae8c027a726c91 274 270 2012-01-24T00:11:11Z Duck 2 wikitext text/x-wiki Here is a short overview of the services provided by DuckCorp. Our services are supervised and important data are [[Services/Backup|saved regularly]]. {{warning}} [[Services/Security|Notes about security !]] {| class="wikitable" style="text-align: center; width: 100%;" |+ Available Services |- ! Category !! colspan="2" | Service !! Access !! Description |- | rowspan="7" | Communication || rowspan="2" | Mail || [[Services/Mail|eMails]] || users || Mail boxes with anti-spam/anti-virus, filtering…, or mail redirections |- | Mailing-Lists || users || Distribution lists for mails |- | rowspan="3" | IRC || IRC Network || public || MilkyPond Chat Network using a dedicated software or a Web-interface |- | IRC Bouncer || users || [[wikipedia:IRC_bouncer#IRC|IRC proxy]] (IRC server relaying IRC communications, keeping connections open and remembering logs) |- | IRC to IM gateway || users || IRC server relaying communication to multiple instant messaging networks in a unified interface (supported network: ICQ/AIM/YM!/…, support as much networks as [[wikipedia:Pidgin_(software)#Supported_protocols|Pidgin]] + coincoin) |- | colspan="2" | XMPP (Jabber) || users || Global Chat Network (inter-communication between many [[wikipedia:Xmpp#History|well-known public IM services]]) |- | colspan="2" | Triboune Libre || public || MilkyPond Web-chat system inspired by [http://linuxfr.org/board the famous one] on [http://linuxfr.org/ Linuxfr.org] |- | rowspan="4" | File/Media Sharing || colspan="2" | [[Services/Gallery|Media Gallery]] || public/users || Photo and video gallery |- | rowspan="3" | Generic || [[Services/FTP|File Repository]] || public/users || Generic file sharing system (using FTP) |- | [https://stuff.milkypond.org/ Downloads Links] || public/users || Web-based generic file sharing |- | Shell Transfer || trusted || File transfer system using the SAFT protocol (shell access needed) |- | rowspan="3" | Utilities || colspan="2" | [https://gossip.duckcorp.org/ News WebReader] || users || News feeds reader through a web interface |- | colspan="2" | Time Server || public || System used to automatically setup time on your machines (and also part of the [http://www.pool.ntp.org/en/ NTP Pool Project]) |- | colspan="2" | Dictionary Server || public || Words searching system via a dedicated software (using the DICT protocol) or a Web-interface |- | rowspan="6" | Development || colspan="2" | [https://projects.duckcorp.org/ Project Management & Issue Tracking] || public/users || |- | colspan="2" | Code Review || public/users || |- | colspan="2" | [https://rcs.duckcorp.org/ VCS] || public/users || Code/configuration versioning tools (Git, SVN, Baz, Bzr…) |- | rowspan="2" | Databases || SQL || users || SQL server (PostgreSQL or MySQL) |- | LDAP || users || LDAP server (OpenLDAP) |- | colspan="2" | [[Services/SoftwareRepository|Software Repository]] || public/users || Software repository, to provide custom packages (think Debian debs) or installation media (thinks DVDs) |- | rowspan="5" | Hosting || colspan="2" | [[Services/DNS|DNS]] || users || Domain Name System (NS1/NS2, DNSSEC…) |- | colspan="2" | [[Services/MailHosting|Mail Domains]] || users || Mail hosting (MX1/MX2) |- | colspan="2" | Web Sites/Applications || users || Web pages using HTML/XHTML, CSS, JS, and various server-side programming languages (SSI, PHP, Perl, Python, Ruby…), and statistics (analytics data/reports) |- | colspan="2" | XMPP Domains || users || XMPP Node for a custom domain |- | colspan="2" | [[Services/Shell|Shell]] || trusted || Useful for website administration, development, run custom scripts, persistent applications for text-mode geeks… |- | rowspan="2" | Network || colspan="2" | IPv6 tunnels || users || Access to the IPv6 world through an IPv4 connection |- | colspan="2" | [[Services/NSTX|NSTX]] || users || Access to the Internet through a restricted WIFI connection (via an IP over DNS tunnel) |} == TODO == * [https://wiki.duckcorp.org/ public wiki] (with ACLs) * in Services/Shell: link to SAFT * in Services/XMPP: chitchat * in Services/IRC: irconweb * new debian repository (when ready) … 3eae17fc7ec295d07ae1139ebcbd9154f2a3da7f 275 274 2012-01-24T00:23:17Z Duck 2 wikitext text/x-wiki Here is a short overview of the services provided by DuckCorp. Our services are supervised and important data are [[Services/Backup|saved regularly]]. {{warning}} [[Services/Security|Notes about security !]] {| class="wikitable" style="text-align: center; width: 100%;" |+ Available Services |- ! Category !! colspan="2" | Service !! Access !! Description |- | rowspan="7" | Communication || rowspan="2" | Mail || [[Services/Mail|eMails]] || users || Mail boxes with anti-spam/anti-virus, filtering…, or mail redirections |- | [[Services/ML|Mailing-Lists]] || users || Distribution lists for mails |- | rowspan="3" | IRC || [[Services/IRC|IRC Network]] || public || MilkyPond Chat Network using a dedicated software or a Web-interface |- | IRC Bouncer || users || [[Services/IRC-Bouncer|IRC proxy]] (IRC server relaying IRC communications, keeping connections open and remembering logs) |- | [[Services/IRC-IM-GW|IRC to IM gateway]] || users || IRC server relaying communication to multiple instant messaging networks in a unified interface (supported network: ICQ/AIM/YM!/…, support as much networks as [[wikipedia:Pidgin_(software)#Supported_protocols|Pidgin]] + coincoin) |- | colspan="2" | [[Services/XMPP|XMPP (Jabber)]] || users || Global Chat Network (inter-communication between many [[wikipedia:Xmpp#History|well-known public IM services]]) |- | colspan="2" | [[Services/Tribioune|Triboune Libre]] || public || MilkyPond Web-chat system inspired by [http://linuxfr.org/board the famous one] on [http://linuxfr.org/ Linuxfr.org] |- | rowspan="4" | File/Media Sharing || colspan="2" | [[Services/Gallery|Media Gallery]] || public/users || Photo and video gallery |- | rowspan="3" | Generic || [[Services/FTP|File Repository]] || public/users || Generic file sharing system (using FTP) |- | [[Services/WebFileExchange|Downloads Links]] || public/users || Web-based generic file sharing |- | [[Services/SAFT|Shell Transfer]] || trusted || File transfer system using the SAFT protocol (shell access needed) |- | rowspan="3" | Utilities || colspan="2" | [[Services/WebFeeds|News WebReader]] || users || News feeds reader through a web interface |- | colspan="2" | [[Services/NTP|Time Server]] || public || System used to automatically setup time on your machines (and also part of the [http://www.pool.ntp.org/en/ NTP Pool Project]) |- | colspan="2" | [[Services/Dico|Dictionary Server]] || public || Words searching system via a dedicated software (using the DICT protocol) or a Web-interface |- | rowspan="6" | Development || colspan="2" | [[Services/Projects|Project Management & Issue Tracking]] || public/users || |- | colspan="2" | [[Services/CodeReview|Code Review]] || public/users || |- | colspan="2" | [[Services/VCS|VCS]] || public/users || Code/configuration versioning tools (Git, SVN, Baz, Bzr…) |- | rowspan="2" | Databases || SQL || users || SQL server (PostgreSQL or MySQL) |- | LDAP || users || LDAP server (OpenLDAP) |- | colspan="2" | [[Services/SoftwareRepository|Software Repository]] || public/users || Software repository, to provide custom packages (think Debian debs) or installation media (thinks DVDs) |- | rowspan="5" | Hosting || colspan="2" | [[Services/DNS|DNS]] || users || Domain Name System (NS1/NS2, DNSSEC…) |- | colspan="2" | [[Services/MailHosting|Mail Domains]] || users || Mail hosting (MX1/MX2) |- | colspan="2" | Web Sites/Applications || users || Web pages using HTML/XHTML, CSS, JS, and various server-side programming languages (SSI, PHP, Perl, Python, Ruby…), and statistics (analytics data/reports) |- | colspan="2" | XMPP Domains || users || XMPP Node for a custom domain |- | colspan="2" | [[Services/Shell|Shell]] || trusted || Useful for website administration, development, run custom scripts, persistent applications for text-mode geeks… |- | rowspan="2" | Network || colspan="2" | IPv6 tunnels || users || Access to the IPv6 world through an IPv4 connection |- | colspan="2" | [[Services/NSTX|NSTX]] || users || Access to the Internet through a restricted WIFI connection (via an IP over DNS tunnel) |} == TODO == * [https://wiki.duckcorp.org/ public wiki] (with ACLs) * in Services/Shell: link to SAFT * in Services/XMPP: chitchat * in Services/IRC: irconweb * in Services/IRC-Bouncer: wikipedia:IRC_bouncer#IRC * in Services/WebFileExchange: https://stuff.milkypond.org/ * in Services/WebFeeds: https://gossip.duckcorp.org/ * in Services/Projects: https://projects.duckcorp.org/ * in Services/VCS: https://rcs.duckcorp.org/ * new debian repository (when ready) … f2515986bf84c690f9580f9fd6d559a558f50b6b 276 275 2012-01-24T00:26:17Z Duck 2 wikitext text/x-wiki Here is a short overview of the services provided by DuckCorp. Our services are supervised and important data are [[Services/Backup|saved regularly]]. {{warning}} [[Services/Security|Notes about security !]] {| class="wikitable" style="text-align: center; width: 100%;" |+ Available Services |- ! Category !! colspan="2" | Service !! Access !! Description |- | rowspan="7" | Communication || rowspan="2" | Mail || [[Services/Mail|eMails]] || users || Mail boxes with anti-spam/anti-virus, filtering…, or mail redirections |- | [[Services/ML|Mailing-Lists]] || users || Distribution lists for mails |- | rowspan="3" | IRC || [[Services/IRC|IRC Network]] || public || MilkyPond Chat Network using a dedicated software or a Web-interface |- | [[Services/IRC-Bouncer|IRC Bouncer]] || users || IRC proxy (IRC server relaying IRC communications, keeping connections open and remembering logs) |- | [[Services/IRC-IM-GW|IRC to IM gateway]] || users || IRC server relaying communication to multiple instant messaging networks in a unified interface (supported network: ICQ/AIM/YM!/…, support as much networks as [[wikipedia:Pidgin_(software)#Supported_protocols|Pidgin]] + coincoin) |- | colspan="2" | [[Services/XMPP|XMPP (Jabber)]] || users || Global Chat Network (inter-communication between many [[wikipedia:Xmpp#History|well-known public IM services]]) |- | colspan="2" | [[Services/Tribioune|Triboune Libre]] || public || MilkyPond Web-chat system inspired by [http://linuxfr.org/board the famous one] on [http://linuxfr.org/ Linuxfr.org] |- | rowspan="4" | File/Media Sharing || colspan="2" | [[Services/Gallery|Media Gallery]] || public/users || Photo and video gallery |- | rowspan="3" | Generic || [[Services/FTP|File Repository]] || public/users || Generic file sharing system (using FTP) |- | [[Services/WebFileExchange|Downloads Links]] || public/users || Web-based generic file sharing |- | [[Services/SAFT|Shell Transfer]] || trusted || File transfer system using the SAFT protocol (shell access needed) |- | rowspan="3" | Utilities || colspan="2" | [[Services/WebFeeds|News WebReader]] || users || News feeds reader through a web interface |- | colspan="2" | [[Services/NTP|Time Server]] || public || System used to automatically setup time on your machines (and also part of the [http://www.pool.ntp.org/en/ NTP Pool Project]) |- | colspan="2" | [[Services/Dico|Dictionary Server]] || public || Words searching system via a dedicated software (using the DICT protocol) or a Web-interface |- | rowspan="6" | Development || colspan="2" | [[Services/Projects|Project Management & Issue Tracking]] || public/users || |- | colspan="2" | [[Services/CodeReview|Code Review]] || public/users || |- | colspan="2" | [[Services/VCS|VCS]] || public/users || Code/configuration versioning tools (Git, SVN, Baz, Bzr…) |- | rowspan="2" | Databases || [[Services/SQL|SQL]] || users || SQL server (PostgreSQL or MySQL) |- | [[Services/LDAP|LDAP]] || users || LDAP server (OpenLDAP) |- | colspan="2" | [[Services/SoftwareRepository|Software Repository]] || public/users || Software repository, to provide custom packages (think Debian debs) or installation media (thinks DVDs) |- | rowspan="5" | Hosting || colspan="2" | [[Services/DNS|DNS]] || users || Domain Name System (NS1/NS2, DNSSEC…) |- | colspan="2" | [[Services/MailHosting|Mail Domains]] || users || Mail hosting (MX1/MX2) |- | colspan="2" | [[Services/WebHosting|Web Sites/Applications]] || users || Web pages using HTML/XHTML, CSS, JS, and various server-side programming languages (SSI, PHP, Perl, Python, Ruby…), and statistics (analytics data/reports) |- | colspan="2" | [[Services/XMPPHosting|XMPP Domains]] || users || XMPP Node for a custom domain |- | colspan="2" | [[Services/Shell|Shell]] || trusted || Useful for website administration, development, run custom scripts, persistent applications for text-mode geeks… |- | rowspan="2" | Network || colspan="2" | [[Services/IPv6-Broker|IPv6 tunnels]] || users || Access to the IPv6 world through an IPv4 connection |- | colspan="2" | [[Services/NSTX|NSTX]] || users || Access to the Internet through a restricted WIFI connection (via an IP over DNS tunnel) |} == TODO == * [https://wiki.duckcorp.org/ public wiki] (with ACLs) * in Services/Shell: link to SAFT * in Services/XMPP: chitchat * in Services/IRC: irconweb * in Services/IRC-Bouncer: wikipedia:IRC_bouncer#IRC * in Services/WebFileExchange: https://stuff.milkypond.org/ * in Services/WebFeeds: https://gossip.duckcorp.org/ * in Services/Projects: https://projects.duckcorp.org/ * in Services/VCS: https://rcs.duckcorp.org/ … cf332d23c6d74ccb6f566cab9253d12796345c10 277 276 2012-01-24T01:52:36Z Duck 2 wikitext text/x-wiki Here is a short overview of the services provided by DuckCorp. Our services are supervised and important data are [[Services/Backup|saved regularly]]. {{warning}} [[Services/Security|Notes about security !]] {| class="wikitable" style="text-align: center; width: 100%;" |+ Available Services |- ! Category !! colspan="2" | Service !! Access !! Description |- | rowspan="7" | Communication || rowspan="2" | Mail || [[Services/Mail|eMails]] || users || Mail boxes with anti-spam/anti-virus, filtering…, or mail redirections |- | [[Services/ML|Mailing-Lists]] || users || Distribution lists for mails |- | rowspan="3" | IRC || [[Services/IRC|IRC Network]] || public || MilkyPond Chat Network using a dedicated software or a Web-interface |- | [[Services/IRC-Bouncer|IRC Bouncer]] || users || IRC proxy (IRC server relaying IRC communications, keeping connections open and remembering logs) |- | [[Services/IRC-IM-GW|IRC to IM gateway]] || users || IRC server relaying communication to multiple instant messaging networks in a unified interface (supported network: ICQ/AIM/YM!/…, support as much networks as [[wikipedia:Pidgin_(software)#Supported_protocols|Pidgin]] + coincoin) |- | colspan="2" | [[Services/XMPP|XMPP (Jabber)]] || users || Global Chat Network (inter-communication between many [[wikipedia:Xmpp#History|well-known public IM services]]) |- | colspan="2" | [[Services/Tribioune|Triboune Libre]] || public || MilkyPond Web-chat system inspired by [http://linuxfr.org/board the famous one] on [http://linuxfr.org/ Linuxfr.org] |- | rowspan="5" | Sharing || colspan="2" | [[Services/Gallery|Media Gallery]] || public/users || Photo and video gallery |- | colspan="2" | [[Services/Wiki|Wiki]] || public/users || Technical knowledge, useful tips… |- | rowspan="3" | Generic || [[Services/FTP|File Repository]] || public/users || Generic file sharing system (using FTP) |- | [[Services/WebFileExchange|Downloads Links]] || public/users || Web-based generic file sharing |- | [[Services/SAFT|Shell Transfer]] || trusted || File transfer system using the SAFT protocol (shell access needed) |- | rowspan="3" | Utilities || colspan="2" | [[Services/WebFeeds|News WebReader]] || users || News feeds reader through a web interface |- | colspan="2" | [[Services/NTP|Time Server]] || public || System used to automatically setup time on your machines (and also part of the [http://www.pool.ntp.org/en/ NTP Pool Project]) |- | colspan="2" | [[Services/Dico|Dictionary Server]] || public || Words searching system via a dedicated software (using the DICT protocol) or a Web-interface |- | rowspan="6" | Development || colspan="2" | [[Services/Projects|Project Management & Issue Tracking]] || public/users || |- | colspan="2" | [[Services/CodeReview|Code Review]] || public/users || |- | colspan="2" | [[Services/VCS|VCS]] || public/users || Code/configuration versioning tools (Git, SVN, Baz, Bzr…) |- | rowspan="2" | Databases || [[Services/SQL|SQL]] || users || SQL server (PostgreSQL or MySQL) |- | [[Services/LDAP|LDAP]] || users || LDAP server (OpenLDAP) |- | colspan="2" | [[Services/SoftwareRepository|Software Repository]] || public/users || Software repository, to provide custom packages (think Debian debs) or installation media (thinks DVDs) |- | rowspan="5" | Hosting || colspan="2" | [[Services/DNS|DNS]] || users || Domain Name System (NS1/NS2, DNSSEC…) |- | colspan="2" | [[Services/MailHosting|Mail Domains]] || users || Mail hosting (MX1/MX2) |- | colspan="2" | [[Services/WebHosting|Web Sites/Applications]] || users || Web pages using HTML/XHTML, CSS, JS, and various server-side programming languages (SSI, PHP, Perl, Python, Ruby…), and statistics (analytics data/reports) |- | colspan="2" | [[Services/XMPPHosting|XMPP Domains]] || users || XMPP Node for a custom domain |- | colspan="2" | [[Services/Shell|Shell]] || trusted || Useful for website administration, development, run custom scripts, persistent applications for text-mode geeks… |- | rowspan="2" | Network || colspan="2" | [[Services/IPv6-Broker|IPv6 tunnels]] || users || Access to the IPv6 world through an IPv4 connection |- | colspan="2" | [[Services/NSTX|NSTX]] || users || Access to the Internet through a restricted WIFI connection (via an IP over DNS tunnel) |} == TODO == * in Services/Wiki: https://wiki.duckcorp.org/ * in Services/Shell: link to SAFT * in Services/XMPP: chitchat * in Services/IRC: irconweb * in Services/IRC-Bouncer: wikipedia:IRC_bouncer#IRC * in Services/WebFileExchange: https://stuff.milkypond.org/ * in Services/WebFeeds: https://gossip.duckcorp.org/ * in Services/Projects: https://projects.duckcorp.org/ * in Services/VCS: https://rcs.duckcorp.org/ … a8ed9e3079def333da6cc78b3a6b863a148f71df 297 277 2012-01-25T02:06:27Z Duck 2 wikitext text/x-wiki Here is a short overview of the services provided by DuckCorp. Our services are supervised and important data are [[Services/Backup|saved regularly]]. {{warning}} [[Services/Security|Notes about security !]] {| class="wikitable" style="text-align: center; width: 100%;" |+ Available Services |- ! Category !! colspan="2" | Service !! Access !! Description |- | rowspan="7" | Communication || rowspan="2" | Mail || [[Services/Mail|eMails]] || users || Mail boxes with anti-spam/anti-virus, filtering…, or mail redirections |- | [[Services/ML|Mailing-Lists]] || users || Distribution lists for mails |- | rowspan="3" | IRC || [[Services/IRC|IRC Network]] || public || MilkyPond Chat Network using a dedicated software or a Web-interface |- | [[Services/IRC-Bouncer|IRC Bouncer]] || users || IRC proxy (IRC server relaying IRC communications, keeping connections open and remembering logs) |- | [[Services/IRC-IM-GW|IRC to IM gateway]] || users || IRC server relaying communication to multiple instant messaging networks in a unified interface (supported network: ICQ/AIM/YM!/…, support as much networks as [[wikipedia:Pidgin_(software)#Supported_protocols|Pidgin]] + coincoin) |- | colspan="2" | [[Services/XMPP|XMPP (Jabber)]] || users || Global Chat Network (inter-communication between many [[wikipedia:Xmpp#History|well-known public IM services]]) |- | colspan="2" | [[Services/Tribioune|Triboune Libre]] || public || MilkyPond Web-chat system inspired by [http://linuxfr.org/board the famous one] on [http://linuxfr.org/ Linuxfr.org] |- | rowspan="5" | Sharing || colspan="2" | [[Services/Gallery|Media Gallery]] || public/users || Photo and video gallery |- | colspan="2" | [[Services/Wiki|Wiki]] || public/users || Technical knowledge, useful tips… |- | rowspan="3" | Generic || [[Services/FTP|File Repository]] || public/users || Generic file sharing system (using FTP) |- | [[Services/WebFileExchange|Downloads Links]] || public/users || Web-based generic file sharing |- | [[Services/SAFT|Shell Transfer]] || trusted || File transfer system using the SAFT protocol (shell access needed) |- | rowspan="3" | Utilities || colspan="2" | [[Services/WebFeeds|News WebReader]] || users || News feeds reader through a web interface |- | colspan="2" | [[Services/NTP|Time Server]] || public || System used to automatically setup time on your machines (and also part of the [http://www.pool.ntp.org/en/ NTP Pool Project]) |- | colspan="2" | [[Services/Dico|Dictionary Server]] || public || Words searching system via a dedicated software (using the DICT protocol) or a Web-interface |- | rowspan="6" | Development || colspan="2" | [[Services/Projects|Project Management & Issue Tracking]] || public/users || |- | colspan="2" | [[Services/CodeReview|Code Review]] || public/users || |- | colspan="2" | [[Services/VCS|VCS]] || public/users || Code/configuration versioning tools (Git, SVN, Baz, Bzr…) |- | rowspan="2" | Databases || [[Services/SQL|SQL]] || users || SQL server (PostgreSQL or MySQL) |- | [[Services/LDAP|LDAP]] || users || LDAP server (OpenLDAP) |- | colspan="2" | [[Services/SoftwareRepository|Software Repository]] || public/users || Software repository, to provide custom packages (think Debian debs) or installation media (thinks DVDs) |- | rowspan="5" | Hosting || colspan="2" | [[Services/DNS|DNS]] || users || Domain Name System (NS1/NS2, DNSSEC…) |- | colspan="2" | [[Services/MailHosting|Mail Domains]] || users || Mail hosting (MX1/MX2) |- | colspan="2" | [[Services/WebHosting|Web Sites/Applications]] || users || Web pages using HTML/XHTML, CSS, JS, and various server-side programming languages (SSI, PHP, Perl, Python, Ruby…), and statistics (analytics data/reports) |- | colspan="2" | [[Services/XMPPHosting|XMPP Domains]] || users || XMPP Node for a custom domain |- | colspan="2" | [[Services/Shell|Shell]] || trusted || Useful for website administration, development, run custom scripts, persistent applications for text-mode geeks… |- | rowspan="2" | Network || colspan="2" | [[Services/IPv6-Broker|IPv6 tunnels]] || users || Access to the IPv6 world through an IPv4 connection |- | colspan="2" | [[Services/NSTX|NSTX]] || users || Access to the Internet through a restricted WIFI connection (via an IP over DNS tunnel) |} == TODO == * in Services/Wiki: https://wiki.duckcorp.org/ * in Services/Shell: link to SAFT * in Services/XMPP: chitchat * in Services/WebFileExchange: https://stuff.milkypond.org/ * in Services/WebFeeds: https://gossip.duckcorp.org/ * in Services/Projects: https://projects.duckcorp.org/ * in Services/VCS: https://rcs.duckcorp.org/ … abdc48aa9aa69db4cc69a9b571efcdc39d53c6fe 298 297 2012-01-25T02:14:01Z Duck 2 wikitext text/x-wiki Here is a short overview of the services provided by DuckCorp. Our services are supervised and important data are [[Services/Backup|saved regularly]]. {{warning}} [[Services/Security|Notes about security !]] {| class="wikitable" style="text-align: center; width: 100%;" |+ Available Services |- ! Category !! colspan="2" | Service !! Access !! Description |- | rowspan="7" | Communication || rowspan="2" | Mail || [[Services/Mail|eMails]] || users || style="text-align: left;" | Mail boxes with anti-spam/anti-virus, filtering…, or mail redirections |- | [[Services/ML|Mailing-Lists]] || users || style="text-align: left;" | Distribution lists for mails |- | rowspan="3" | IRC || [[Services/IRC|IRC Network]] || public || style="text-align: left;" | MilkyPond Chat Network using a dedicated software or a Web-interface |- | [[Services/IRC-Bouncer|IRC Bouncer]] || users || style="text-align: left;" | IRC proxy (IRC server relaying IRC communications, keeping connections open and remembering logs) |- | [[Services/IRC-IM-GW|IRC to IM gateway]] || users || style="text-align: left;" | IRC server relaying communication to multiple instant messaging networks in a unified interface (supported network: ICQ/AIM/YM!/…, support as much networks as [[wikipedia:Pidgin_(software)#Supported_protocols|Pidgin]] + coincoin) |- | colspan="2" | [[Services/XMPP|XMPP (Jabber)]] || users || style="text-align: left;" | Global Chat Network (inter-communication between many [[wikipedia:Xmpp#History|well-known public IM services]]) |- | colspan="2" | [[Services/Tribioune|Triboune Libre]] || public || style="text-align: left;" | MilkyPond Web-chat system inspired by [http://linuxfr.org/board the famous one] on [http://linuxfr.org/ Linuxfr.org] |- | rowspan="5" | Sharing || colspan="2" | [[Services/Gallery|Media Gallery]] || public/users || style="text-align: left;" | Photo and video gallery |- | colspan="2" | [[Services/Wiki|Wiki]] || public/users || style="text-align: left;" | Technical knowledge, useful tips… |- | rowspan="3" | Generic || [[Services/FTP|File Repository]] || public/users || style="text-align: left;" | Generic file sharing system (using FTP) |- | [[Services/WebFileExchange|Downloads Links]] || public/users || style="text-align: left;" | Web-based generic file sharing |- | [[Services/SAFT|Shell Transfer]] || trusted || style="text-align: left;" | File transfer system using the SAFT protocol (shell access needed) |- | rowspan="3" | Utilities || colspan="2" | [[Services/WebFeeds|News WebReader]] || users || style="text-align: left;" | News feeds reader through a web interface |- | colspan="2" | [[Services/NTP|Time Server]] || public || style="text-align: left;" | System used to automatically setup time on your machines (and also part of the [http://www.pool.ntp.org/en/ NTP Pool Project]) |- | colspan="2" | [[Services/Dico|Dictionary Server]] || public || style="text-align: left;" | Words searching system via a dedicated software (using the DICT protocol) or a Web-interface |- | rowspan="6" | Development || colspan="2" | [[Services/Projects|Project Management & Issue Tracking]] || public/users || style="text-align: left;" | |- | colspan="2" | [[Services/CodeReview|Code Review]] || public/users || style="text-align: left;" | |- | colspan="2" | [[Services/VCS|VCS]] || public/users || style="text-align: left;" | Code/configuration versioning tools (Git, SVN, Baz, Bzr…) |- | rowspan="2" | Databases || [[Services/SQL|SQL]] || users || style="text-align: left;" | SQL server (PostgreSQL or MySQL) |- | [[Services/LDAP|LDAP]] || users || style="text-align: left;" | LDAP server (OpenLDAP) |- | colspan="2" | [[Services/SoftwareRepository|Software Repository]] || public/users || style="text-align: left;" | Software repository, to provide custom packages (think Debian debs) or installation media (thinks DVDs) |- | rowspan="5" | Hosting || colspan="2" | [[Services/DNS|DNS]] || users || style="text-align: left;" | Domain Name System (NS1/NS2, DNSSEC…) |- | colspan="2" | [[Services/MailHosting|Mail Domains]] || users || style="text-align: left;" | Mail hosting (MX1/MX2) |- | colspan="2" | [[Services/WebHosting|Web Sites/Applications]] || users || style="text-align: left;" | Web pages using HTML/XHTML, CSS, JS, and various server-side programming languages (SSI, PHP, Perl, Python, Ruby…), and statistics (analytics data/reports) |- | colspan="2" | [[Services/XMPPHosting|XMPP Domains]] || users || style="text-align: left;" | XMPP Node for a custom domain |- | colspan="2" | [[Services/Shell|Shell]] || trusted || style="text-align: left;" | Useful for website administration, development, run custom scripts, persistent applications for text-mode geeks… |- | rowspan="2" | Network || colspan="2" | [[Services/IPv6-Broker|IPv6 tunnels]] || users || style="text-align: left;" | Access to the IPv6 world through an IPv4 connection |- | colspan="2" | [[Services/NSTX|NSTX]] || users || style="text-align: left;" | Access to the Internet through a restricted WIFI connection (via an IP over DNS tunnel) |} == TODO == * in Services/Wiki: https://wiki.duckcorp.org/ * in Services/Shell: link to SAFT * in Services/XMPP: chitchat * in Services/WebFileExchange: https://stuff.milkypond.org/ * in Services/WebFeeds: https://gossip.duckcorp.org/ * in Services/Projects: https://projects.duckcorp.org/ * in Services/VCS: https://rcs.duckcorp.org/ … efd3d4f57208ea7ecca9843be4084e5c23242ee8 0 50 256 237 2012-01-23T02:49:46Z Duck 2 /* Programs */ wikitext text/x-wiki == Remote Access == Via SSH with a RSA/DSA key on the fillowing hosts: * thorfinn.duckcorp.org (prefered for lengthy sessions, like screens) * toushirou.duckcorp.org (mostly useful to manage Web/FTP data) == Available Resources == The following resources are available and will remain until we advertise a scheduled removal. If you miss something you can send us a request. === Locales === * en_GB.UTF-8 * en_US.UTF-8 * fr_FR.UTF-8 * ja_JP.EUC-JP * ja_JP.UTF-8 === Shells === * dash * bash * zsh * ksh * tcsh === Programs === * aspell * dict * emacs * irssi (with plugins) * latex (full TeXlive) * screen * sieve-connect * vim * w3m * weechat (with plugins) Additional tools: * [[Services/VCS|VCS tools]] abb8b08dea2dd46eb0ec8dc3dfb6eaec8179fb2d 267 256 2012-01-23T22:53:30Z Duck 2 wikitext text/x-wiki == Prerequisite == You need to ask an administrator for an account, but we need to know you well-enough to ensure you are trustable. This is '''not''' a VIP requirement, but such access can be very dangerous and we don't know any other way to avoid a disaster, sorry. == Access == Via SSH with a RSA/DSA key on the fillowing hosts: * thorfinn.duckcorp.org (prefered for lengthy sessions, like screens) * toushirou.duckcorp.org (mostly useful to manage Web/FTP data) == Available Resources == The following resources are available and will remain until we advertise a scheduled removal. If you miss something you can send us a request. === Locales === * en_GB.UTF-8 * en_US.UTF-8 * fr_FR.UTF-8 * ja_JP.EUC-JP * ja_JP.UTF-8 === Shells === * dash * bash * zsh * ksh * tcsh === Programs === * aspell * dict * emacs * irssi (with plugins) * latex (full TeXlive) * screen * sieve-connect * vim * w3m * weechat (with plugins) Additional tools: * [[Services/VCS|VCS tools]] 204b27842bef794af2f7011585c4b61dc71b5ea1 285 267 2012-01-24T23:34:20Z Duck 2 wikitext text/x-wiki == Prerequisite == You need to ask an administrator for an account, but we need to know you well-enough to ensure you are trustable. This is '''not''' a VIP requirement, but such access can be very dangerous and we don't know any other way to avoid a disaster, sorry. == Access == Via SSH with a RSA/DSA key on the fillowing hosts: * thorfinn.duckcorp.org (prefered for lengthy sessions, like screens) * toushirou.duckcorp.org (mostly useful to manage Web/FTP data) == Available Resources == The following resources are available and will remain until we advertise a scheduled removal. If you miss something you can send us a request. === Locales === * en_GB.UTF-8 * en_US.UTF-8 * fr_FR.UTF-8 * ja_JP.EUC-JP * ja_JP.UTF-8 === Shells === * dash * bash * zsh * ksh * tcsh === Programs === * aspell * dict * emacs * irssi (with plugins) * latex (full TeXlive) * screen * sieve-connect * vim * w3m * weechat (with plugins) Additional tools: * [[Services/VCS|VCS tools]] == Technical Details == This service is made using: * [http://www.openssh.org/ OpenSSH] c6b08b4799cee63056f3b88ea8b43d4e023ca758 0 43 258 159 2012-01-23T19:33:53Z Duck 2 wikitext text/x-wiki DC can provide primary or secondary DNS servers for your zones. == Master Zones Administration == To have your master zone modified on our servers, you can: * use our [[UserMagicalInterface]] * ask administrators == DNS Security == To provide as much security as possible, DC supports the following mechanisms. === [[wikipedia:TSIG|TSIG]] === This protocol allows a secure transfer of zones between primary and secondary servers. The DC's DNS servers support TSIG and comminication between them are always secured. The following entities are known to support TSIG and can then securely transfer zones to/from DC: * [http://www.hivane.net/ Hivane] === [[wikipedia:Domain_Name_System_Security_Extensions|DNSSEC]] === ==== What is DNSSEC? ==== This protocol aims at establishing a chain of trust, from the root of the DNS, to ensure response to queries on a zone has not been altered on the way. With the root zone public key, it is possible to validate the replies step by step down to your zone, for example: root public key -> ''.'' zone -> NS for ''org.'' -> ''org.'' zone -> NS for ''milkypond.org.'' -> ''milkypond.org.'' zone -> ''irc.milkypond.org.'' entry. Unfortunately, many DNS providers do not support DNSSEC (Gandi is one of them :-/). In order to help people work on securing their zone, and be ready when their provider is, the [http://www.isc.org/ ISC] created a solution to validate zones using another secure path: by publishing security associations in a special zone (''dlv.isc.org'', called the DLV Registry), which itself can be validated the normal way. This is only a stopgap, but as providers seems not to be in a hurry to do their job, DC decided to use it. ==== How to use it for my zones? ==== DC DNS servers are able to handle the complicated procedure needed to sign a zone for you. You can just modify it the classic way, and have it signed automatically. You just need to ask us to switch the zone to the secure mode. If your provider gladly support DNSSEC, we can provide the necessary information for the chain of trust; if not, we can use the DLV registry. Beware DNS always means propagation delays, so you may have to wait a few days before the switch is completed and your zone fully secured over the whole world. ==== How to test my zone is secured? ==== First, you need a validating DNS server (explanations for ''bind9'' on Debian): * get the root zone public key (using this script for example: [[File:Get dns root zone key.sh]]) * add the key to your configuration (in ''/etc/bind/named.conf''): include "/etc/bind/root.keys"; * add in your global options (''/etc/bind/named.conf.options''): dnssec-enable yes; dnssec-validation yes; dnssec-lookaside auto; * restart bind The DLV Registry public key is already provided in the ''bind9'' package. Then, you can check it with the ''dig'' tool (available in the ''dnsutils'' Debian package): dig +dnssec <zone> Look at the flags: it is secured if you find the ''ad'' flag. If there is the ''aa'' flag instead, then you are interrogating on of the authoritative DNS servers for the zone, it is also secure, but better test it on another server to be sure it is propagated. {{warning}} If you check an entry of your zone which is a CNAME, beware the CNAME is resolved and if the destination name cannot be validated, then your entry won't either. 36660adffa08a1293f873b2324f1105b54935d1f 266 258 2012-01-23T22:48:10Z Duck 2 wikitext text/x-wiki We can provide primary or secondary DNS servers for your zones. == Prerequisite == You need to buy a domain from a registrar and ask an administrator to configure this service. == Master Zones Administration == To have your master zone modified on our servers, you can: * use our [[UserMagicalInterface]] * ask administrators == DNS Security == To provide as much security as possible, DC supports the following mechanisms. === [[wikipedia:TSIG|TSIG]] === This protocol allows a secure transfer of zones between primary and secondary servers. The DC's DNS servers support TSIG and comminication between them are always secured. The following entities are known to support TSIG and can then securely transfer zones to/from DC: * [http://www.hivane.net/ Hivane] === [[wikipedia:Domain_Name_System_Security_Extensions|DNSSEC]] === ==== What is DNSSEC? ==== This protocol aims at establishing a chain of trust, from the root of the DNS, to ensure response to queries on a zone has not been altered on the way. With the root zone public key, it is possible to validate the replies step by step down to your zone, for example: root public key -> ''.'' zone -> NS for ''org.'' -> ''org.'' zone -> NS for ''milkypond.org.'' -> ''milkypond.org.'' zone -> ''irc.milkypond.org.'' entry. Unfortunately, many DNS providers do not support DNSSEC (Gandi is one of them :-/). In order to help people work on securing their zone, and be ready when their provider is, the [http://www.isc.org/ ISC] created a solution to validate zones using another secure path: by publishing security associations in a special zone (''dlv.isc.org'', called the DLV Registry), which itself can be validated the normal way. This is only a stopgap, but as providers seems not to be in a hurry to do their job, DC decided to use it. ==== How to use it for my zones? ==== DC DNS servers are able to handle the complicated procedure needed to sign a zone for you. You can just modify it the classic way, and have it signed automatically. You just need to ask us to switch the zone to the secure mode. If your provider gladly support DNSSEC, we can provide the necessary information for the chain of trust; if not, we can use the DLV registry. Beware DNS always means propagation delays, so you may have to wait a few days before the switch is completed and your zone fully secured over the whole world. ==== How to test my zone is secured? ==== First, you need a validating DNS server (explanations for ''bind9'' on Debian): * get the root zone public key (using this script for example: [[File:Get dns root zone key.sh]]) * add the key to your configuration (in ''/etc/bind/named.conf''): include "/etc/bind/root.keys"; * add in your global options (''/etc/bind/named.conf.options''): dnssec-enable yes; dnssec-validation yes; dnssec-lookaside auto; * restart bind The DLV Registry public key is already provided in the ''bind9'' package. Then, you can check it with the ''dig'' tool (available in the ''dnsutils'' Debian package): dig +dnssec <zone> Look at the flags: it is secured if you find the ''ad'' flag. If there is the ''aa'' flag instead, then you are interrogating on of the authoritative DNS servers for the zone, it is also secure, but better test it on another server to be sure it is propagated. {{warning}} If you check an entry of your zone which is a CNAME, beware the CNAME is resolved and if the destination name cannot be validated, then your entry won't either. d04c7bd5786c555245c73f54f988ef6acabc8854 283 266 2012-01-24T23:30:59Z Duck 2 wikitext text/x-wiki We can provide primary or secondary DNS servers for your zones. == Prerequisite == You need to buy a domain from a registrar and ask an administrator to configure this service. == Master Zones Administration == To have your master zone modified on our servers, you can: * use our [[UserMagicalInterface]] * ask administrators == DNS Security == To provide as much security as possible, DC supports the following mechanisms. === [[wikipedia:TSIG|TSIG]] === This protocol allows a secure transfer of zones between primary and secondary servers. The DC's DNS servers support TSIG and comminication between them are always secured. The following entities are known to support TSIG and can then securely transfer zones to/from DC: * [http://www.hivane.net/ Hivane] === [[wikipedia:Domain_Name_System_Security_Extensions|DNSSEC]] === ==== What is DNSSEC? ==== This protocol aims at establishing a chain of trust, from the root of the DNS, to ensure response to queries on a zone has not been altered on the way. With the root zone public key, it is possible to validate the replies step by step down to your zone, for example: root public key -> ''.'' zone -> NS for ''org.'' -> ''org.'' zone -> NS for ''milkypond.org.'' -> ''milkypond.org.'' zone -> ''irc.milkypond.org.'' entry. Unfortunately, many DNS providers do not support DNSSEC (Gandi is one of them :-/). In order to help people work on securing their zone, and be ready when their provider is, the [http://www.isc.org/ ISC] created a solution to validate zones using another secure path: by publishing security associations in a special zone (''dlv.isc.org'', called the DLV Registry), which itself can be validated the normal way. This is only a stopgap, but as providers seems not to be in a hurry to do their job, DC decided to use it. ==== How to use it for my zones? ==== DC DNS servers are able to handle the complicated procedure needed to sign a zone for you. You can just modify it the classic way, and have it signed automatically. You just need to ask us to switch the zone to the secure mode. If your provider gladly support DNSSEC, we can provide the necessary information for the chain of trust; if not, we can use the DLV registry. Beware DNS always means propagation delays, so you may have to wait a few days before the switch is completed and your zone fully secured over the whole world. ==== How to test my zone is secured? ==== First, you need a validating DNS server (explanations for ''bind9'' on Debian): * get the root zone public key (using this script for example: [[File:Get dns root zone key.sh]]) * add the key to your configuration (in ''/etc/bind/named.conf''): include "/etc/bind/root.keys"; * add in your global options (''/etc/bind/named.conf.options''): dnssec-enable yes; dnssec-validation yes; dnssec-lookaside auto; * restart bind The DLV Registry public key is already provided in the ''bind9'' package. Then, you can check it with the ''dig'' tool (available in the ''dnsutils'' Debian package): dig +dnssec <zone> Look at the flags: it is secured if you find the ''ad'' flag. If there is the ''aa'' flag instead, then you are interrogating on of the authoritative DNS servers for the zone, it is also secure, but better test it on another server to be sure it is propagated. {{warning}} If you check an entry of your zone which is a CNAME, beware the CNAME is resolved and if the destination name cannot be validated, then your entry won't either. == Documentation == * generic documentation on [[wikipedia:Domain_Name_System|DNS]] == Technical Details == This service is made using: * [http://bind9.net/ Bind9] * [http://www.opendnssec.org/ OpenDNSSEC] 4c2ca43c593ceda59dda712d6c8a014c7151adfa 0 51 259 244 2012-01-23T19:34:49Z Duck 2 wikitext text/x-wiki Available services: * full hosting (MX1) on our servers * fallback retention (MX2) on our servers or, at your choice, partner servers (currently via Hivane) == Full Hosting == You can have multiple email addresses which can be: * real mailboxes * redirections towards third party addresses * wildcards based on your domains or sub-domains. Have a look at our [[Services/Mail|complete set of mail services]]. == Fallback retention == The current retention period on our servers is 2 weeks, but can be temporary or permanently increased if needed. Mails flowing back to your primary server can be protected using TLS with certificate verification if you wish. Antivirus and antispam filtering are not applied to relayed mails, so we do not mess with your prefered strategy on your primary server, nevertheless basic checks (EHLO, DNS…) and RBL scoring are done to avoid accepting tons of SPAMs. 73d6d9ca018edcbfe43edfebce398009516ec4e3 268 259 2012-01-23T22:56:36Z Duck 2 wikitext text/x-wiki Available services: * full hosting (MX1) on our servers * fallback retention (MX2) on our servers or, at your choice, partner servers (currently via Hivane) == Prerequisite == You need to buy a domain from a registrar, setup a DNS (can be [[Services/DNS|hosted here]] too), and ask an administrator to configure this service. == Full Hosting == You can have multiple email addresses which can be: * real mailboxes * redirections towards third party addresses * wildcards based on your domains or sub-domains. Have a look at our [[Services/Mail|complete set of mail services]]. == Fallback retention == The current retention period on our servers is 2 weeks, but can be temporary or permanently increased if needed. Mails flowing back to your primary server can be protected using TLS with certificate verification if you wish. Antivirus and antispam filtering are not applied to relayed mails, so we do not mess with your prefered strategy on your primary server, nevertheless basic checks (EHLO, DNS…) and RBL scoring are done to avoid accepting tons of SPAMs. 5a750a669c7bd95303d42ce2754a8c0f3890ddb3 284 268 2012-01-24T23:33:22Z Duck 2 wikitext text/x-wiki Available services: * full hosting (MX1) on our servers * fallback retention (MX2) on our servers or, at your choice, partner servers (currently via Hivane) == Prerequisite == You need to buy a domain from a registrar, setup a DNS (can be [[Services/DNS|hosted here]] too), and ask an administrator to configure this service. == Full Hosting == You can have multiple email addresses which can be: * real mailboxes * redirections towards third party addresses * wildcards based on your domains or sub-domains. Have a look at our [[Services/Mail|complete set of mail services]]. == Fallback retention == The current retention period on our servers is 2 weeks, but can be temporary or permanently increased if needed. Mails flowing back to your primary server can be protected using TLS with certificate verification if you wish. Antivirus and antispam filtering are not applied to relayed mails, so we do not mess with your prefered strategy on your primary server, nevertheless basic checks (EHLO, DNS…) and RBL scoring are done to avoid accepting tons of SPAMs. == Technical Details == See the [[Services/Mail#Technical_Details|eMail service page]]. 7fb44f0563954b0b94465c6dfb730e54d4ad9e43 0 49 260 245 2012-01-23T19:35:02Z Duck 2 wikitext text/x-wiki Available services: * multiple email addresses (mailboxes or redirections) based on ''milkypond.org'' (or maybe ''duckcorp.org'') domain(s) or you own domain(s) * roaming accounts to be able to send emails wherever you are == Access Methods == You can retrieve your mails, in case of a real mailbox, using: * IMAP+TLS (TCP 143) / IMAPS (TCP 993) on imap.duckcorp.org * or POP3+TLS (TCP 110) / POP3S (TCP 995) on pop.duckcorp.org * or one of the [https://webmail.duckcorp.org/ provided webmails] The IMAP protocol is recommended over POP3, as it provides many interresting features. If you want to download all your mails absolutely at home, loosing the ability to read your mail from anywhere on the planet, you can do that with IMAP too (look at your mail client settings). You can use our servers to send mails out too via smtp.duckcorp.org using: * SMTP+TLS (TCP 25) / SMTPS (TCP 465) * and SASL authentication == Mailboxes Features == === Antivirus and Antispam === Mails stored on our server are checked upon arrival for viruses and SPAMs. Mail redirected to a third party mailbox are not, not to mess with the strategy of the the final destination (which could arm learning greatly). Mails being viruses are suppressed automatically upon arrival. Once in a week, an extra antivirus check is done on all hosted mailboxes, to remove viruses not detected at the time it arrived (our antivirus database is updated daily), so you may see such mail disappear from your mailbox, don't fear. SPAMs are more difficult to detect, and it is an error-prone process, so we chose to use a learning software intead of using a global database. On the bright side of things, you would never loose mails and the software should be able to learn what is a SPAM from '''your''' point of view (which has proved to differ slightly between our users), but on the grey side you will have to teach him regulary to avoid errors. When your account is created, it acts like an empty headed body letting everything through, but after a few weeks of teaching it is able to recognise most of your habits and block a lot of annoying SPAM. To teach the system, you can: * use the [https://spamfilter.duckcorp.org/ web interface] to retrain from errors in the ''History'' page * resend SPAM to dc-spam@duckcorp.org and HAM (non-SPAM) to dc-ham@duckcorp.org *: {{warning}} PLEASE TAKE CARE to use the ''resend'' function of your mailer and never use ''forward'', which would result in '''yourself''' being considered as spam or ham You can yourself setup a few parameters in the ''Preferences'' page of the [https://spamfilter.duckcorp.org/ web interface], mostly: * how the system should train: ** TEFT (''On every new message scanned by the filter''): useful to learn very quickly especially on a new mailbox or when you've got tons of spam on your addresses, but you need to train it regulary (daily is better) or it will learn wrong (very quickly too !) ** TOE (''Only when the filter makes a mistake''): slow learning, but if you don't have time for training very often or go on long holidays without internet access this mode will give you a stable behavior ** TUM (''Only with new data or if the filter makes a mistake''): trade-off between the two previous modes, learn quite fast and not too demanding, adapts better to new SPAMs then TOE * filter sensitivity: you can ask the system to be more or less aggressive * message handling: ** ''Quarantine the message'': mails are not delivered to your mailbox but retained by the system and you can only manage them through the [https://spamfilter.duckcorp.org/ web interface] ; if you retrain a quarantined mail as HAM, it will be freed from quarantine and delivered in your mailbox at once ; in this mode, you need to flush your quarantine once in a while ** ''Tag the Subject header with'': mails are delivered with a modified title (which is a tad ugly) ** ''Deliver the message normally with a X-DSPAM-Result header'': mails are delivered with a special field in your mail headers (not always visible depending on your mail client and its configuration) ; this is quite handy if you prefer SPAMs arranged in a specific folder * ''Disable DSPAM filtering'': you may switch off filtering at your own risk We strongly recommend using TEFT with daily training for a few weeks then switching to TUM. If you need to go away for a long time, switching to TOE is recommended. Using the quarantine feature is also a safe choice, as the web interface is quite easy to use. === Mail Filtering === With your favourite mail client, you can probably filter your mails in proper folders already. Nevertheless, this can be a annoying operation: * blocking you mail client for a long time if you have to process plenty of mails * downloading each mail information, and sometimes content (depending on your filters), is lenghty too, and cost much bandwidth * syncing filters accross your machines (home desktop, laptop, office machine…) is a pain in the ass * processing only when you're online prevents triggering actions in a timely manner (automatic redirect, vacation messages…), and running a machine 24/7 with a mail client polling new mails every 30s is not a solution We provide a much better way to do this using the [[wikipedia:Sieve_(mail_filtering_language)|SIEVE]] filters. Shortly, SIEVE is a language dedicated to expressing mail filters. Our server is able to process your mails according to these filters as soon as they arrive. You then don't have to care about them anymore, and may use light mail clients or webmails when you're not on your machine with your favourite software. To push your filters on the server, a dedicated protocol exists: : MANAGESIEVE (TCP 4190) on sieve.duckcorp.org Several softwares support managing SIEVE rules: * Icedove/Thunderbird using the SIEVE extension (in xul-ext-sieve Debian package) provides a rules editor * Horde (Ingo) provides an easy to use web interface * Squirrelmail with the Avelsieve extension provides an easy to use web interface * Roundcube with an extension provides an easy to use web interface * sieve-connect provides a CLI to upload/download/activate your rules files (tell us if you know more software supporting this feature) You can read more info about SIEVE here: * supported SIEVE features on our server: http://pigeonhole.dovecot.org/ * http://www.fastmail.fm/docs/sieve/ * http://sieve.info/ === Shared/Public Folders === You may need to share mails or messages with friends or people you do stuff with (in a project or association). Depending on your needs, two solutions are possible: * share some of your own private folders, thus called ''shared folders'' * manage a special folder hierarchy, called ''public folders'' (even if they may not be accessible to everyone) Through IMAP, or our webmails internally using IMAP, it is possible to partition the folder hierarchy into ''namespaces''. Traditionally you are using the root namespace for your private folders. Additionnal namespaces can be created and will appear among your own folders or separate, depending on your mail client's choice of representation. To avoid name clashes, we decided to prefix all additionnal namespace names with a '''#'''. Since 2011-05-14, the following extra namespaces are created and reserved: * #Shared, containing all folders other users decided to share with you * #MilkyPond, containing public MP/DC information mailboxes you may subscribe at will Using IMAP, it is possible to setup rights (read only, write allowed…) to your own folders in order to share them with other users, or group of users. Public folders are owned by noone, and must be created by DC administrators ; if you need one, send us a request and we may be able to create it and delegate administration to your care (namespace name is subject to approval). Once created, public folders can be administered like shared folders. Client mail softwares support: * Horde: support namespaces, shared folders configurable via ''Options->Share Folders'' menu but no ACLs for public folders * Icedove/Thunderbird: support namespaces, shared and public folders configurable via folder selection and ''Tools->Imap-ACL'' menu action Most other softwares have namespace support only, so you should be able to use shared/public folders you have rights on but not configure them yourself (tell us if you know more software supporting this feature) == Limitations == === Maximum Mail Size === Mail you send or receive are limited to 10MB. If you need to transmit much bigger data, then a mail transport is not appropriate, you'd better use a file sharing method instead. === Quotas === Even if it would be nice to live without it, we had to establish quotas to force people sort their mails out once in a while and delete useless things instead of leaving an ever-growing mess behind. The default quota is 512MB which is not that big but should match needs of most users. This said, you may ask us for more and there's no reason we would refuse a reasonable demand. aba8f0a1b5864fc101b34236dd3cc20521172733 263 260 2012-01-23T22:43:27Z Duck 2 wikitext text/x-wiki Available services: * multiple email addresses (mailboxes or redirections) based on ''milkypond.org'' (or maybe ''duckcorp.org'') domain(s) or you own domain(s) * roaming accounts to be able to send emails wherever you are == Prerequisite == You need to ask the administrators for an account. == Access == You can retrieve your mails, in case of a real mailbox, using: * IMAP+TLS (TCP 143) / IMAPS (TCP 993) on imap.duckcorp.org * or POP3+TLS (TCP 110) / POP3S (TCP 995) on pop.duckcorp.org * or one of the [https://webmail.duckcorp.org/ provided webmails] The IMAP protocol is recommended over POP3, as it provides many interresting features. If you want to download all your mails absolutely at home, loosing the ability to read your mail from anywhere on the planet, you can do that with IMAP too (look at your mail client settings). You can use our servers to send mails out too via smtp.duckcorp.org using: * SMTP+TLS (TCP 25) / SMTPS (TCP 465) * and SASL authentication == Mailboxes Features == === Antivirus and Antispam === Mails stored on our server are checked upon arrival for viruses and SPAMs. Mail redirected to a third party mailbox are not, not to mess with the strategy of the the final destination (which could arm learning greatly). Mails being viruses are suppressed automatically upon arrival. Once in a week, an extra antivirus check is done on all hosted mailboxes, to remove viruses not detected at the time it arrived (our antivirus database is updated daily), so you may see such mail disappear from your mailbox, don't fear. SPAMs are more difficult to detect, and it is an error-prone process, so we chose to use a learning software intead of using a global database. On the bright side of things, you would never loose mails and the software should be able to learn what is a SPAM from '''your''' point of view (which has proved to differ slightly between our users), but on the grey side you will have to teach him regulary to avoid errors. When your account is created, it acts like an empty headed body letting everything through, but after a few weeks of teaching it is able to recognise most of your habits and block a lot of annoying SPAM. To teach the system, you can: * use the [https://spamfilter.duckcorp.org/ web interface] to retrain from errors in the ''History'' page * resend SPAM to dc-spam@duckcorp.org and HAM (non-SPAM) to dc-ham@duckcorp.org *: {{warning}} PLEASE TAKE CARE to use the ''resend'' function of your mailer and never use ''forward'', which would result in '''yourself''' being considered as spam or ham You can yourself setup a few parameters in the ''Preferences'' page of the [https://spamfilter.duckcorp.org/ web interface], mostly: * how the system should train: ** TEFT (''On every new message scanned by the filter''): useful to learn very quickly especially on a new mailbox or when you've got tons of spam on your addresses, but you need to train it regulary (daily is better) or it will learn wrong (very quickly too !) ** TOE (''Only when the filter makes a mistake''): slow learning, but if you don't have time for training very often or go on long holidays without internet access this mode will give you a stable behavior ** TUM (''Only with new data or if the filter makes a mistake''): trade-off between the two previous modes, learn quite fast and not too demanding, adapts better to new SPAMs then TOE * filter sensitivity: you can ask the system to be more or less aggressive * message handling: ** ''Quarantine the message'': mails are not delivered to your mailbox but retained by the system and you can only manage them through the [https://spamfilter.duckcorp.org/ web interface] ; if you retrain a quarantined mail as HAM, it will be freed from quarantine and delivered in your mailbox at once ; in this mode, you need to flush your quarantine once in a while ** ''Tag the Subject header with'': mails are delivered with a modified title (which is a tad ugly) ** ''Deliver the message normally with a X-DSPAM-Result header'': mails are delivered with a special field in your mail headers (not always visible depending on your mail client and its configuration) ; this is quite handy if you prefer SPAMs arranged in a specific folder * ''Disable DSPAM filtering'': you may switch off filtering at your own risk We strongly recommend using TEFT with daily training for a few weeks then switching to TUM. If you need to go away for a long time, switching to TOE is recommended. Using the quarantine feature is also a safe choice, as the web interface is quite easy to use. === Mail Filtering === With your favourite mail client, you can probably filter your mails in proper folders already. Nevertheless, this can be a annoying operation: * blocking you mail client for a long time if you have to process plenty of mails * downloading each mail information, and sometimes content (depending on your filters), is lenghty too, and cost much bandwidth * syncing filters accross your machines (home desktop, laptop, office machine…) is a pain in the ass * processing only when you're online prevents triggering actions in a timely manner (automatic redirect, vacation messages…), and running a machine 24/7 with a mail client polling new mails every 30s is not a solution We provide a much better way to do this using the [[wikipedia:Sieve_(mail_filtering_language)|SIEVE]] filters. Shortly, SIEVE is a language dedicated to expressing mail filters. Our server is able to process your mails according to these filters as soon as they arrive. You then don't have to care about them anymore, and may use light mail clients or webmails when you're not on your machine with your favourite software. To push your filters on the server, a dedicated protocol exists: : MANAGESIEVE (TCP 4190) on sieve.duckcorp.org Several softwares support managing SIEVE rules: * Icedove/Thunderbird using the SIEVE extension (in xul-ext-sieve Debian package) provides a rules editor * Horde (Ingo) provides an easy to use web interface * Squirrelmail with the Avelsieve extension provides an easy to use web interface * Roundcube with an extension provides an easy to use web interface * sieve-connect provides a CLI to upload/download/activate your rules files (tell us if you know more software supporting this feature) You can read more info about SIEVE here: * supported SIEVE features on our server: http://pigeonhole.dovecot.org/ * http://www.fastmail.fm/docs/sieve/ * http://sieve.info/ === Shared/Public Folders === You may need to share mails or messages with friends or people you do stuff with (in a project or association). Depending on your needs, two solutions are possible: * share some of your own private folders, thus called ''shared folders'' * manage a special folder hierarchy, called ''public folders'' (even if they may not be accessible to everyone) Through IMAP, or our webmails internally using IMAP, it is possible to partition the folder hierarchy into ''namespaces''. Traditionally you are using the root namespace for your private folders. Additionnal namespaces can be created and will appear among your own folders or separate, depending on your mail client's choice of representation. To avoid name clashes, we decided to prefix all additionnal namespace names with a '''#'''. Since 2011-05-14, the following extra namespaces are created and reserved: * #Shared, containing all folders other users decided to share with you * #MilkyPond, containing public MP/DC information mailboxes you may subscribe at will Using IMAP, it is possible to setup rights (read only, write allowed…) to your own folders in order to share them with other users, or group of users. Public folders are owned by noone, and must be created by DC administrators ; if you need one, send us a request and we may be able to create it and delegate administration to your care (namespace name is subject to approval). Once created, public folders can be administered like shared folders. Client mail softwares support: * Horde: support namespaces, shared folders configurable via ''Options->Share Folders'' menu but no ACLs for public folders * Icedove/Thunderbird: support namespaces, shared and public folders configurable via folder selection and ''Tools->Imap-ACL'' menu action Most other softwares have namespace support only, so you should be able to use shared/public folders you have rights on but not configure them yourself (tell us if you know more software supporting this feature) == Limitations == === Maximum Mail Size === Mail you send or receive are limited to 10MB. If you need to transmit much bigger data, then a mail transport is not appropriate, you'd better use a file sharing method instead. === Quotas === Even if it would be nice to live without it, we had to establish quotas to force people sort their mails out once in a while and delete useless things instead of leaving an ever-growing mess behind. The default quota is 512MB which is not that big but should match needs of most users. This said, you may ask us for more and there's no reason we would refuse a reasonable demand. c73d8160adf93224cb8d62b8debe6dc76d71a745 265 263 2012-01-23T22:46:42Z Duck 2 wikitext text/x-wiki Available services: * multiple email addresses (mailboxes or redirections) based on ''milkypond.org'' (or maybe ''duckcorp.org'') domain(s) or you own domain(s) * roaming accounts to be able to send emails wherever you are == Prerequisite == You need to ask an administrator for an account. == Access == You can retrieve your mails, in case of a real mailbox, using: * IMAP+TLS (TCP 143) / IMAPS (TCP 993) on imap.duckcorp.org * or POP3+TLS (TCP 110) / POP3S (TCP 995) on pop.duckcorp.org * or one of the [https://webmail.duckcorp.org/ provided webmails] The IMAP protocol is recommended over POP3, as it provides many interresting features. If you want to download all your mails absolutely at home, loosing the ability to read your mail from anywhere on the planet, you can do that with IMAP too (look at your mail client settings). You can use our servers to send mails out too via smtp.duckcorp.org using: * SMTP+TLS (TCP 25) / SMTPS (TCP 465) * and SASL authentication == Mailboxes Features == === Antivirus and Antispam === Mails stored on our server are checked upon arrival for viruses and SPAMs. Mail redirected to a third party mailbox are not, not to mess with the strategy of the the final destination (which could arm learning greatly). Mails being viruses are suppressed automatically upon arrival. Once in a week, an extra antivirus check is done on all hosted mailboxes, to remove viruses not detected at the time it arrived (our antivirus database is updated daily), so you may see such mail disappear from your mailbox, don't fear. SPAMs are more difficult to detect, and it is an error-prone process, so we chose to use a learning software intead of using a global database. On the bright side of things, you would never loose mails and the software should be able to learn what is a SPAM from '''your''' point of view (which has proved to differ slightly between our users), but on the grey side you will have to teach him regulary to avoid errors. When your account is created, it acts like an empty headed body letting everything through, but after a few weeks of teaching it is able to recognise most of your habits and block a lot of annoying SPAM. To teach the system, you can: * use the [https://spamfilter.duckcorp.org/ web interface] to retrain from errors in the ''History'' page * resend SPAM to dc-spam@duckcorp.org and HAM (non-SPAM) to dc-ham@duckcorp.org *: {{warning}} PLEASE TAKE CARE to use the ''resend'' function of your mailer and never use ''forward'', which would result in '''yourself''' being considered as spam or ham You can yourself setup a few parameters in the ''Preferences'' page of the [https://spamfilter.duckcorp.org/ web interface], mostly: * how the system should train: ** TEFT (''On every new message scanned by the filter''): useful to learn very quickly especially on a new mailbox or when you've got tons of spam on your addresses, but you need to train it regulary (daily is better) or it will learn wrong (very quickly too !) ** TOE (''Only when the filter makes a mistake''): slow learning, but if you don't have time for training very often or go on long holidays without internet access this mode will give you a stable behavior ** TUM (''Only with new data or if the filter makes a mistake''): trade-off between the two previous modes, learn quite fast and not too demanding, adapts better to new SPAMs then TOE * filter sensitivity: you can ask the system to be more or less aggressive * message handling: ** ''Quarantine the message'': mails are not delivered to your mailbox but retained by the system and you can only manage them through the [https://spamfilter.duckcorp.org/ web interface] ; if you retrain a quarantined mail as HAM, it will be freed from quarantine and delivered in your mailbox at once ; in this mode, you need to flush your quarantine once in a while ** ''Tag the Subject header with'': mails are delivered with a modified title (which is a tad ugly) ** ''Deliver the message normally with a X-DSPAM-Result header'': mails are delivered with a special field in your mail headers (not always visible depending on your mail client and its configuration) ; this is quite handy if you prefer SPAMs arranged in a specific folder * ''Disable DSPAM filtering'': you may switch off filtering at your own risk We strongly recommend using TEFT with daily training for a few weeks then switching to TUM. If you need to go away for a long time, switching to TOE is recommended. Using the quarantine feature is also a safe choice, as the web interface is quite easy to use. === Mail Filtering === With your favourite mail client, you can probably filter your mails in proper folders already. Nevertheless, this can be a annoying operation: * blocking you mail client for a long time if you have to process plenty of mails * downloading each mail information, and sometimes content (depending on your filters), is lenghty too, and cost much bandwidth * syncing filters accross your machines (home desktop, laptop, office machine…) is a pain in the ass * processing only when you're online prevents triggering actions in a timely manner (automatic redirect, vacation messages…), and running a machine 24/7 with a mail client polling new mails every 30s is not a solution We provide a much better way to do this using the [[wikipedia:Sieve_(mail_filtering_language)|SIEVE]] filters. Shortly, SIEVE is a language dedicated to expressing mail filters. Our server is able to process your mails according to these filters as soon as they arrive. You then don't have to care about them anymore, and may use light mail clients or webmails when you're not on your machine with your favourite software. To push your filters on the server, a dedicated protocol exists: : MANAGESIEVE (TCP 4190) on sieve.duckcorp.org Several softwares support managing SIEVE rules: * Icedove/Thunderbird using the SIEVE extension (in xul-ext-sieve Debian package) provides a rules editor * Horde (Ingo) provides an easy to use web interface * Squirrelmail with the Avelsieve extension provides an easy to use web interface * Roundcube with an extension provides an easy to use web interface * sieve-connect provides a CLI to upload/download/activate your rules files (tell us if you know more software supporting this feature) You can read more info about SIEVE here: * supported SIEVE features on our server: http://pigeonhole.dovecot.org/ * http://www.fastmail.fm/docs/sieve/ * http://sieve.info/ === Shared/Public Folders === You may need to share mails or messages with friends or people you do stuff with (in a project or association). Depending on your needs, two solutions are possible: * share some of your own private folders, thus called ''shared folders'' * manage a special folder hierarchy, called ''public folders'' (even if they may not be accessible to everyone) Through IMAP, or our webmails internally using IMAP, it is possible to partition the folder hierarchy into ''namespaces''. Traditionally you are using the root namespace for your private folders. Additionnal namespaces can be created and will appear among your own folders or separate, depending on your mail client's choice of representation. To avoid name clashes, we decided to prefix all additionnal namespace names with a '''#'''. Since 2011-05-14, the following extra namespaces are created and reserved: * #Shared, containing all folders other users decided to share with you * #MilkyPond, containing public MP/DC information mailboxes you may subscribe at will Using IMAP, it is possible to setup rights (read only, write allowed…) to your own folders in order to share them with other users, or group of users. Public folders are owned by noone, and must be created by DC administrators ; if you need one, send us a request and we may be able to create it and delegate administration to your care (namespace name is subject to approval). Once created, public folders can be administered like shared folders. Client mail softwares support: * Horde: support namespaces, shared folders configurable via ''Options->Share Folders'' menu but no ACLs for public folders * Icedove/Thunderbird: support namespaces, shared and public folders configurable via folder selection and ''Tools->Imap-ACL'' menu action Most other softwares have namespace support only, so you should be able to use shared/public folders you have rights on but not configure them yourself (tell us if you know more software supporting this feature) == Limitations == === Maximum Mail Size === Mail you send or receive are limited to 10MB. If you need to transmit much bigger data, then a mail transport is not appropriate, you'd better use a file sharing method instead. === Quotas === Even if it would be nice to live without it, we had to establish quotas to force people sort their mails out once in a while and delete useless things instead of leaving an ever-growing mess behind. The default quota is 512MB which is not that big but should match needs of most users. This said, you may ask us for more and there's no reason we would refuse a reasonable demand. d746be15a7201ee6d5de1d9cd0ba30986a4cb4ce 279 265 2012-01-24T22:42:37Z Duck 2 wikitext text/x-wiki Available services: * multiple email addresses (mailboxes or redirections) based on ''milkypond.org'' (or maybe ''duckcorp.org'') domain(s) or you own domain(s) * roaming accounts to be able to send emails wherever you are == Prerequisite == You need to ask an administrator for an account. == Access == === Using a Mail Reader === You can retrieve your mails, in case of a real mailbox, using either: * IMAP+TLS (TCP 143) / IMAPS (TCP 993) on imap.duckcorp.org * or POP3+TLS (TCP 110) / POP3S (TCP 995) on pop.duckcorp.org The IMAP protocol is recommended over POP3, as it provides many interesting features. If you want to download all your mails absolutely at home, loosing the ability to read your mail from anywhere on the planet, you can do that with IMAP too (look at your mail client settings). You can use our servers to send mails out too via smtp.duckcorp.org using: * SMTP+TLS (TCP 25) / SMTPS (TCP 465) * and SASL authentication === Using a Web Interface === Several [https://webmail.duckcorp.org/ webmail interfaces] are available. == Mailboxes Features == === Antivirus and Antispam === Mails stored on our server are checked upon arrival for viruses and SPAMs. Mail redirected to a third party mailbox are not, not to mess with the strategy of the the final destination (which could arm learning greatly). Mails being viruses are suppressed automatically upon arrival. Once in a week, an extra antivirus check is done on all hosted mailboxes, to remove viruses not detected at the time it arrived (our antivirus database is updated daily), so you may see such mail disappear from your mailbox, don't fear. SPAMs are more difficult to detect, and it is an error-prone process, so we chose to use a learning software intead of using a global database. On the bright side of things, you would never loose mails and the software should be able to learn what is a SPAM from '''your''' point of view (which has proved to differ slightly between our users), but on the grey side you will have to teach him regulary to avoid errors. When your account is created, it acts like an empty headed body letting everything through, but after a few weeks of teaching it is able to recognise most of your habits and block a lot of annoying SPAM. To teach the system, you can: * use the [https://spamfilter.duckcorp.org/ web interface] to retrain from errors in the ''History'' page * resend SPAM to dc-spam@duckcorp.org and HAM (non-SPAM) to dc-ham@duckcorp.org *: {{warning}} PLEASE TAKE CARE to use the ''resend'' function of your mailer and never use ''forward'', which would result in '''yourself''' being considered as spam or ham You can yourself setup a few parameters in the ''Preferences'' page of the [https://spamfilter.duckcorp.org/ web interface], mostly: * how the system should train: ** TEFT (''On every new message scanned by the filter''): useful to learn very quickly especially on a new mailbox or when you've got tons of spam on your addresses, but you need to train it regulary (daily is better) or it will learn wrong (very quickly too !) ** TOE (''Only when the filter makes a mistake''): slow learning, but if you don't have time for training very often or go on long holidays without internet access this mode will give you a stable behavior ** TUM (''Only with new data or if the filter makes a mistake''): trade-off between the two previous modes, learn quite fast and not too demanding, adapts better to new SPAMs then TOE * filter sensitivity: you can ask the system to be more or less aggressive * message handling: ** ''Quarantine the message'': mails are not delivered to your mailbox but retained by the system and you can only manage them through the [https://spamfilter.duckcorp.org/ web interface] ; if you retrain a quarantined mail as HAM, it will be freed from quarantine and delivered in your mailbox at once ; in this mode, you need to flush your quarantine once in a while ** ''Tag the Subject header with'': mails are delivered with a modified title (which is a tad ugly) ** ''Deliver the message normally with a X-DSPAM-Result header'': mails are delivered with a special field in your mail headers (not always visible depending on your mail client and its configuration) ; this is quite handy if you prefer SPAMs arranged in a specific folder * ''Disable DSPAM filtering'': you may switch off filtering at your own risk We strongly recommend using TEFT with daily training for a few weeks then switching to TUM. If you need to go away for a long time, switching to TOE is recommended. Using the quarantine feature is also a safe choice, as the web interface is quite easy to use. === Mail Filtering === With your favourite mail client, you can probably filter your mails in proper folders already. Nevertheless, this can be a annoying operation: * blocking you mail client for a long time if you have to process plenty of mails * downloading each mail information, and sometimes content (depending on your filters), is lenghty too, and cost much bandwidth * syncing filters accross your machines (home desktop, laptop, office machine…) is a pain in the ass * processing only when you're online prevents triggering actions in a timely manner (automatic redirect, vacation messages…), and running a machine 24/7 with a mail client polling new mails every 30s is not a solution We provide a much better way to do this using the [[wikipedia:Sieve_(mail_filtering_language)|SIEVE]] filters. Shortly, SIEVE is a language dedicated to expressing mail filters. Our server is able to process your mails according to these filters as soon as they arrive. You then don't have to care about them anymore, and may use light mail clients or webmails when you're not on your machine with your favourite software. To push your filters on the server, a dedicated protocol exists: : MANAGESIEVE (TCP 4190) on sieve.duckcorp.org Several softwares support managing SIEVE rules: * Icedove/Thunderbird using the SIEVE extension (in xul-ext-sieve Debian package) provides a rules editor * Horde (Ingo) provides an easy to use web interface * Squirrelmail with the Avelsieve extension provides an easy to use web interface * Roundcube with an extension provides an easy to use web interface * sieve-connect provides a CLI to upload/download/activate your rules files (tell us if you know more software supporting this feature) You can read more info about SIEVE here: * supported SIEVE features on our server: http://pigeonhole.dovecot.org/ * http://www.fastmail.fm/docs/sieve/ * http://sieve.info/ === Fetching eMails from an External Mailbox === {{todo}} === Shared/Public Folders === You may need to share mails or messages with friends or people you do stuff with (in a project or association). Depending on your needs, two solutions are possible: * share some of your own private folders, thus called ''shared folders'' * manage a special folder hierarchy, called ''public folders'' (even if they may not be accessible to everyone) Through IMAP, or our webmails internally using IMAP, it is possible to partition the folder hierarchy into ''namespaces''. Traditionally you are using the root namespace for your private folders. Additionnal namespaces can be created and will appear among your own folders or separate, depending on your mail client's choice of representation. To avoid name clashes, we decided to prefix all additionnal namespace names with a '''#'''. Since 2011-05-14, the following extra namespaces are created and reserved: * #Shared, containing all folders other users decided to share with you * #MilkyPond, containing public MP/DC information mailboxes you may subscribe at will Using IMAP, it is possible to setup rights (read only, write allowed…) to your own folders in order to share them with other users, or group of users. Public folders are owned by noone, and must be created by DC administrators ; if you need one, send us a request and we may be able to create it and delegate administration to your care (namespace name is subject to approval). Once created, public folders can be administered like shared folders. Client mail softwares support: * Horde: support namespaces, shared folders configurable via ''Options->Share Folders'' menu but no ACLs for public folders * Icedove/Thunderbird: support namespaces, shared and public folders configurable via folder selection and ''Tools->Imap-ACL'' menu action Most other softwares have namespace support only, so you should be able to use shared/public folders you have rights on but not configure them yourself (tell us if you know more software supporting this feature) == Limitations == === Maximum Mail Size === Mail you send or receive are limited to 10MB. If you need to transmit much bigger data, then a mail transport is not appropriate, you'd better use a file sharing method instead. === Quotas === Even if it would be nice to live without it, we had to establish quotas to force people sort their mails out once in a while and delete useless things instead of leaving an ever-growing mess behind. The default quota is 512MB which is not that big but should match needs of most users. This said, you may ask us for more and there's no reason we would refuse a reasonable demand. == Technical Details == This service is made using: * [http://www.postfix.org/ Postfix] * [http://dovecot.org/ Dovecot] * [http://dspam.sourceforge.net DSPAM] * [http://johannes.sipsolutions.net/Projects/dovecot-antispam dovecot-antispam] * [http://www.horde.org/ Horde] * [http://www.squirrelmail.org/ SquirrelMail] * [http://www.roundcube.net/ RoundCube] 7b2c08210b7d08a49897f9a015545490c2523de0 0 52 262 2012-01-23T22:42:35Z Duck 2 Created page with "The Media gallery is a website where you can store, enrich, and share your photo and video files. You can organize them in a hierarchy of folders, and setup permissions if you wa…" wikitext text/x-wiki The Media gallery is a website where you can store, enrich, and share your photo and video files. You can organize them in a hierarchy of folders, and setup permissions if you want to restrict access. == Prerequisite == You need to ask the administrators for an account. == Access == Use this URL in your browser: https://photos.duckcorp.org/ On Android, you can also use [http://f-droid.org/repository/browse/?fdid=net.dahanne.android.regalandroid this application] to access your gallery easily. 9b6851f705e1902ac3258b47e6b942172297c0f0 264 262 2012-01-23T22:46:16Z Duck 2 wikitext text/x-wiki The Media gallery is a website where you can store, enrich, and share your photo and video files. You can organize them in a hierarchy of folders, and setup permissions if you want to restrict access. == Prerequisite == You need to ask an administrator for an account. == Access == Use this URL in your browser: https://photos.duckcorp.org/ On Android, you can also use [http://f-droid.org/repository/browse/?fdid=net.dahanne.android.regalandroid this application] to access your gallery easily. a76a5da5e220c951f7e38afbb8c85f6ee171fc90 272 264 2012-01-23T23:54:12Z Duck 2 wikitext text/x-wiki The Media gallery is a website where you can store, enrich, and share your photo and video files. You can organize them in a hierarchy of folders, and setup permissions if you want to restrict access. == Prerequisite == You need to ask an administrator for an account. == Access == Use this URL in your browser: https://photos.duckcorp.org/ On Android, you can also use [http://f-droid.org/repository/browse/?fdid=net.dahanne.android.regalandroid this application] to access your gallery easily. == Alternate File Upload Method == Besides several methods to transfer files to the gallery, if you have a [[Services/FTP|file repository]] account you may use it to drop your files in the ''photos-perso-dc'' folder. 52a9a253ad6caa5b5efe4df49b54e2c532d4680f 281 272 2012-01-24T22:48:37Z Duck 2 wikitext text/x-wiki The Media gallery is a website where you can store, enrich, and share your photo and video files. You can organize them in a hierarchy of folders, and setup permissions if you want to restrict access. == Prerequisite == You need to ask an administrator for an account. == Access == Use this URL in your browser: https://photos.duckcorp.org/ On Android, you can also use [http://f-droid.org/repository/browse/?fdid=net.dahanne.android.regalandroid this application] to access your gallery easily. == Alternate File Upload Method == Besides several methods to transfer files to the gallery, if you have a [[Services/FTP|file repository]] account you may use it to drop your files in the ''photos-perso-dc'' folder. == Documentation == * ''Gallery 2'' section in the [http://codex.gallery2.org/Main_Page Help Page] == Technical Details == This service is made using: * [http://gallery.menalto.com/ Gallery 2] 2d62dd707b6506e0e06ca2d0926ea91961fafb54 0 53 271 2012-01-23T23:34:10Z Duck 2 Created page with "The file repository is a general-purpose file exchange method. You push files into it and they are kept until you remove them. You may also share them with a other people. == P…" wikitext text/x-wiki The file repository is a general-purpose file exchange method. You push files into it and they are kept until you remove them. You may also share them with a other people. == Prerequisite == You need to ask an administrator for an account if you want to puch your own files, but you don't need anything if you just want to retrieve files from the public folders. You need a FTP client software to access this service, for example: * on GNU/*: filezilla or lftp * on MacOS: CyberDuck * on Windows: filezilla Most browsers should also work for read access. == Access == The publics folders are available for read access using this URL: ftp://ftp.duckcorp.org/ If you want to push files, you need to authenticate with SSL/TLS using this URL: ftps://ftps.duckcorp.org/ You may also access files directly on Toushirou in ''/ftp/ftp.duckcorp.org/'' if you have a [[Services/Shell|shell access]]. == Folders == Summary of important folders for write access: * photos-perso-dc: upload zone for the [[Services/Gallery|gallery]] * private: restricted folders, for users or groups of users; ask an administrator if you need private folders * public: folders which can be read by everybody (accessible directly without authentication on ftp://ftp.duckcorp.org/) * repository: upload folders for the [[Services/Repository|repository]] facility * sendfile: arrival folders for the [[Services/SAFT|shell transfer]] service * sites: folders for hosted websites content 96b6b33b11ffed725ea2a45ccfa080ee25a8c790 273 271 2012-01-23T23:55:24Z Duck 2 /* Folders */ wikitext text/x-wiki The file repository is a general-purpose file exchange method. You push files into it and they are kept until you remove them. You may also share them with a other people. == Prerequisite == You need to ask an administrator for an account if you want to puch your own files, but you don't need anything if you just want to retrieve files from the public folders. You need a FTP client software to access this service, for example: * on GNU/*: filezilla or lftp * on MacOS: CyberDuck * on Windows: filezilla Most browsers should also work for read access. == Access == The publics folders are available for read access using this URL: ftp://ftp.duckcorp.org/ If you want to push files, you need to authenticate with SSL/TLS using this URL: ftps://ftps.duckcorp.org/ You may also access files directly on Toushirou in ''/ftp/ftp.duckcorp.org/'' if you have a [[Services/Shell|shell access]]. == Folders == Summary of important folders for write access: * photos-perso-dc: upload zone for the [[Services/Gallery|gallery]] * private: restricted folders, for users or groups of users; ask an administrator if you need private folders * public: folders which can be read by everybody (accessible directly without authentication on ftp://ftp.duckcorp.org/) * repository: upload folders for the [[Services/SoftwareRepository|software repository]] facility * sendfile: arrival folders for the [[Services/SAFT|shell transfer]] service * sites: folders for hosted websites content d619c6ebb582192b3701e56031999b53fe040738 282 273 2012-01-24T22:51:10Z Duck 2 wikitext text/x-wiki The file repository is a general-purpose file exchange method. You push files into it and they are kept until you remove them. You may also share them with a other people. == Prerequisite == You need to ask an administrator for an account if you want to puch your own files, but you don't need anything if you just want to retrieve files from the public folders. You need a FTP client software to access this service, for example: * on GNU/*: filezilla or lftp * on MacOS: CyberDuck * on Windows: filezilla Most browsers should also work for read access. == Access == The publics folders are available for read access using this URL: ftp://ftp.duckcorp.org/ If you want to push files, you need to authenticate with SSL/TLS using this URL: ftps://ftps.duckcorp.org/ You may also access files directly on Toushirou in ''/ftp/ftp.duckcorp.org/'' if you have a [[Services/Shell|shell access]]. == Folders == Summary of important folders for write access: * photos-perso-dc: upload zone for the [[Services/Gallery|gallery]] * private: restricted folders, for users or groups of users; ask an administrator if you need private folders * public: folders which can be read by everybody (accessible directly without authentication on ftp://ftp.duckcorp.org/) * repository: upload folders for the [[Services/SoftwareRepository|software repository]] facility * sendfile: arrival folders for the [[Services/SAFT|shell transfer]] service * sites: folders for hosted websites content == Documentation == * generic documentation on [[wikipedia:Ftp|FTP]] == Technical Details == This service is made using: * [http://proftpd.org/ ProFTPD] d832035ca3da2bfdf8b270c98f298894bace369d 287 282 2012-01-24T23:47:31Z Duck 2 wikitext text/x-wiki The file repository is a general-purpose file exchange method. You push files into it and they are kept until you remove them. You may also share them with a other people. == Prerequisite == You need to ask an administrator for an account if you want to puch your own files, but you don't need anything if you just want to retrieve files from the public folders. == Access == You need a FTP client software to access this service, for example: * on GNU/*: filezilla or lftp * on MacOS: CyberDuck * on Windows: filezilla Most browsers should also work for read access. The publics folders are available for read access using this URL: ftp://ftp.duckcorp.org/ If you want to push files, you need to authenticate with SSL/TLS using this URL: ftps://ftps.duckcorp.org/ You may also access files directly on Toushirou in ''/ftp/ftp.duckcorp.org/'' if you have a [[Services/Shell|shell access]]. == Folders == Summary of important folders for write access: * photos-perso-dc: upload zone for the [[Services/Gallery|gallery]] * private: restricted folders, for users or groups of users; ask an administrator if you need private folders * public: folders which can be read by everybody (accessible directly without authentication on ftp://ftp.duckcorp.org/) * repository: upload folders for the [[Services/SoftwareRepository|software repository]] facility * sendfile: arrival folders for the [[Services/SAFT|shell transfer]] service * sites: folders for hosted websites content == Documentation == * generic documentation on [[wikipedia:Ftp|FTP]] == Technical Details == This service is made using: * [http://proftpd.org/ ProFTPD] 7c30caae8d84c3e45ab12eed358a11253e99f3a7 0 54 278 2012-01-24T22:28:23Z Duck 2 Created page with "A code review software is a tool to help improve software quality. It is intended for software developers to help them receive feedback on their patches. == Prerequisite == Yo…" wikitext text/x-wiki A code review software is a tool to help improve software quality. It is intended for software developers to help them receive feedback on their patches. == Prerequisite == You need to ask an administrator for an account if you want to create or comment on review, but you don't need anything if you just want to watch existing ones. == Access == Use the following URL and login: https://codereview.duckcorp.org/ == Documentation == * [http://code.google.com/p/rietveld/wiki/CodeReviewHelp Help Page] * generic documentation on [[wikipedia:Code_review|Code Review]] == Technical Details == This service is made using: * [http://code.google.com/p/rietveld/ Rietveld] * [http://www.djangoproject.com/ Django] * [http://www.modwsgi.org/ mod_wsgi] * [http://httpd.apache.org/ Apache HTTPd] e2b8760ecc1b8ae53cf7c43a03517d57bc5ce040 280 278 2012-01-24T22:42:47Z Duck 2 wikitext text/x-wiki A code review software is a tool to help improve software quality. It is intended for software developers to help them receive feedback on their patches. == Prerequisite == You need to ask an administrator for an account if you want to create or comment on review, but you don't need anything if you just want to watch existing ones. == Access == Use the following URL and login: https://codereview.duckcorp.org/ == Documentation == * [http://code.google.com/p/rietveld/wiki/CodeReviewHelp Help Page] * generic documentation on [[wikipedia:Code_review|Code Review]] == Technical Details == This service is made using: * [http://code.google.com/p/rietveld/ Rietveld] * [http://www.djangoproject.com/ Django] f64cc67384dd9bd97822586628eef3301989fce5 0 55 288 2012-01-25T00:11:28Z Duck 2 Created page with "IRC (Internet Relay Chat) is a chat system. We have our own internal network, formerly used to contact administrators and discuss with other users. Even is not advertise widely, …" wikitext text/x-wiki IRC (Internet Relay Chat) is a chat system. We have our own internal network, formerly used to contact administrators and discuss with other users. Even is not advertise widely, external people may join the network, so you can invite your friend. == Prerequisite == None. == Access == === Using an IRC Software === To connect you need and IRC client, like for example: * [http://irssi.org/ Irssi] * [http://www.pidgin.im Pidgin] * [http://weechat.org/ WeeChat] You need to configure these parameters: * host: irc.milkypond.org * port: ** 6680 (if you want a secure connection using SSL/TLS) ** 6667 or 6669 (because 6667 is sometimes filtered) No password is needed to connect. === Using a Web Interface === Use the following URL: https://irconweb.milkypond.org/ == Official Channels == * #MilkyPond: main channel used to meet with other users and friends and ask general questions * #DuckCorp: contact with DuckCorp Administrators and technical discussions * #News: news feeds on IRC (deprecated but still working) == Contacting IRC Administrators == In case of problems on IRC you can find connected administrators using this command (mind the idle time): /QUOTE STATS p Beware IRC Administrators may not be DuckCorp Administrators. == IRC Services == == Documentation == * [http://docs.ratbox.org/svc_userintro.shtml IRC Services Introduction] == Technical Details == This service is made using: * [http://www.ratbox.org/ ircd-ratbox] * [http://services.ratbox.org/ ratbox-services] e7f6ffba0884ef68ac73e96b83178d220ff8daa5 289 288 2012-01-25T00:25:51Z Duck 2 wikitext text/x-wiki IRC (Internet Relay Chat) is a chat system. We have our own internal network, formerly used to contact administrators and discuss with other users. Even is not advertise widely, external people may join the network, so you can invite your friend. == Prerequisite == None. == Access == === Using an IRC Software === To connect you need and IRC client, like for example: * [http://irssi.org/ Irssi] * [http://www.pidgin.im Pidgin] * [http://weechat.org/ WeeChat] You need to configure these parameters: * host: irc.milkypond.org * port: ** 6680 (if you want a secure connection using SSL/TLS) ** 6667 or 6669 (because 6667 is sometimes filtered) No password is needed to connect. === Using a Web Interface === Use the following URL: https://irconweb.milkypond.org/ == Official Channels == * #MilkyPond: main channel used to meet with other users and friends and ask general questions * #DuckCorp: contact with DuckCorp Administrators and technical discussions * #News: news feeds on IRC (deprecated but still working) == Contacting IRC Administrators == In case of problems on IRC you can find connected administrators using this command (mind the idle time): /QUOTE STATS p Beware IRC Administrators may not be DuckCorp Administrators. == Features == === User Modes === You can see available channel modes using this command: /QUOTE HELP UMODE === Channel Modes === You can see available channel modes using this command: /QUOTE HELP CMODE These extra modes are also available: * +r - registered - Users must be registered with services to JOIN * +S - ssl only - Requires SSL/TLS connections to join === IRC Services === == Documentation == * [http://docs.ratbox.org/svc_userintro.shtml IRC Services Introduction] == Technical Details == This service is made using: * [http://www.ratbox.org/ ircd-ratbox] * [http://services.ratbox.org/ ratbox-services] b2500e441fce65429bcf81fd9d40a355b267c948 290 289 2012-01-25T00:32:45Z Duck 2 /* Features */ wikitext text/x-wiki IRC (Internet Relay Chat) is a chat system. We have our own internal network, formerly used to contact administrators and discuss with other users. Even is not advertise widely, external people may join the network, so you can invite your friend. == Prerequisite == None. == Access == === Using an IRC Software === To connect you need and IRC client, like for example: * [http://irssi.org/ Irssi] * [http://www.pidgin.im Pidgin] * [http://weechat.org/ WeeChat] You need to configure these parameters: * host: irc.milkypond.org * port: ** 6680 (if you want a secure connection using SSL/TLS) ** 6667 or 6669 (because 6667 is sometimes filtered) No password is needed to connect. === Using a Web Interface === Use the following URL: https://irconweb.milkypond.org/ == Official Channels == * #MilkyPond: main channel used to meet with other users and friends and ask general questions * #DuckCorp: contact with DuckCorp Administrators and technical discussions * #News: news feeds on IRC (deprecated but still working) == Contacting IRC Administrators == In case of problems on IRC you can find connected administrators using this command (mind the idle time): /QUOTE STATS p Beware IRC Administrators may not be DuckCorp Administrators. == Features == === Commands === You can see available commands using this command: /QUOTE HELP You can get help about a particular command using this command: /QUOTE HELP &lt;command&gt; === User Modes === You can see available channel modes using this command: /QUOTE HELP UMODE === Channel Modes === You can see available channel modes using this command: /QUOTE HELP CMODE These extra modes are also available: * +r - registered - Users must be registered with services to JOIN * +S - ssl only - Requires SSL/TLS connections to join === IRC Services === To help not loose your favorite nick or channel, the IRC Services can register them so you're still in control. It also helps manage channel with a variety of tools. == Documentation == * [http://docs.ratbox.org/svc_userintro.shtml IRC Services Introduction] == Technical Details == This service is made using: * [http://www.ratbox.org/ ircd-ratbox] * [http://services.ratbox.org/ ratbox-services] 50a4415e1aedecf8eb69101353160e2d424491c0 291 290 2012-01-25T00:41:12Z Duck 2 /* User Modes */ wikitext text/x-wiki IRC (Internet Relay Chat) is a chat system. We have our own internal network, formerly used to contact administrators and discuss with other users. Even is not advertise widely, external people may join the network, so you can invite your friend. == Prerequisite == None. == Access == === Using an IRC Software === To connect you need and IRC client, like for example: * [http://irssi.org/ Irssi] * [http://www.pidgin.im Pidgin] * [http://weechat.org/ WeeChat] You need to configure these parameters: * host: irc.milkypond.org * port: ** 6680 (if you want a secure connection using SSL/TLS) ** 6667 or 6669 (because 6667 is sometimes filtered) No password is needed to connect. === Using a Web Interface === Use the following URL: https://irconweb.milkypond.org/ == Official Channels == * #MilkyPond: main channel used to meet with other users and friends and ask general questions * #DuckCorp: contact with DuckCorp Administrators and technical discussions * #News: news feeds on IRC (deprecated but still working) == Contacting IRC Administrators == In case of problems on IRC you can find connected administrators using this command (mind the idle time): /QUOTE STATS p Beware IRC Administrators may not be DuckCorp Administrators. == Features == === Commands === You can see available commands using this command: /QUOTE HELP You can get help about a particular command using this command: /QUOTE HELP &lt;command&gt; === User Modes === You can see available channel modes using this command: /QUOTE HELP UMODE ==== Mode +g ==== (partial note from the ircd-ratbox documentation) When a client is set +g, that user will be in "Caller ID" mode. Any user that messages a +g client will receive a notice saying that they are in +g (server side ignore) mode. The target client (who is set +g) will also receive a notice saying that so and so messaged them, and that they are in +g mode. The target of the message will only receive one notification per minute, from any client, in order to help prevent flooding. The sender will '''not''' have the rate limit, and will receive a notice saying the target is in +g mode every time they send a message. Note that this behavior is similar to the way AWAY messages are done. There are numerous benefits for both opers and regular users, including the ability to stop spambot messages from ever reaching your client, stopping private message and CTCP floods, and being able to sit on IRC in privacy. One question that arises is how to message specific users, while blocking out everyone else. The command ACCEPT is your answer. To add a user to your accept list, issue the raw command: /QUOTE ACCEPT &lt;nick&gt;,&lt;nick&gt;,&lt;nick&gt;,… That user will now be able to send messages to your client until the association is broken. Associations break in one of the following situations: when an accepted user QUIT's (or is on the other side of a split), you QUIT, or the accepted user changes their nick. The reason why a remote user's nick change will remove them from your accept list is so that you cannot track a user after they changed their nick. Viewing the accept list is also very easy. Issue the raw command: /QUOTE ACCEPT * Removing a user from your accept list is also simple. Issue the command: /QUOTE ACCEPT -&lt;nick&gt; === Channel Modes === You can see available channel modes using this command: /QUOTE HELP CMODE These extra modes are also available: * +r - registered - Users must be registered with services to JOIN * +S - ssl only - Requires SSL/TLS connections to join === IRC Services === To help not loose your favorite nick or channel, the IRC Services can register them so you're still in control. It also helps manage channel with a variety of tools. == Documentation == * [http://docs.ratbox.org/svc_userintro.shtml IRC Services Introduction] == Technical Details == This service is made using: * [http://www.ratbox.org/ ircd-ratbox] * [http://services.ratbox.org/ ratbox-services] 01150bf3703a65b24888629cd91629e6f815d583 292 291 2012-01-25T01:12:31Z Duck 2 /* IRC Services */ wikitext text/x-wiki IRC (Internet Relay Chat) is a chat system. We have our own internal network, formerly used to contact administrators and discuss with other users. Even is not advertise widely, external people may join the network, so you can invite your friend. == Prerequisite == None. == Access == === Using an IRC Software === To connect you need and IRC client, like for example: * [http://irssi.org/ Irssi] * [http://www.pidgin.im Pidgin] * [http://weechat.org/ WeeChat] You need to configure these parameters: * host: irc.milkypond.org * port: ** 6680 (if you want a secure connection using SSL/TLS) ** 6667 or 6669 (because 6667 is sometimes filtered) No password is needed to connect. === Using a Web Interface === Use the following URL: https://irconweb.milkypond.org/ == Official Channels == * #MilkyPond: main channel used to meet with other users and friends and ask general questions * #DuckCorp: contact with DuckCorp Administrators and technical discussions * #News: news feeds on IRC (deprecated but still working) == Contacting IRC Administrators == In case of problems on IRC you can find connected administrators using this command (mind the idle time): /QUOTE STATS p Beware IRC Administrators may not be DuckCorp Administrators. == Features == === Commands === You can see available commands using this command: /QUOTE HELP You can get help about a particular command using this command: /QUOTE HELP &lt;command&gt; === User Modes === You can see available channel modes using this command: /QUOTE HELP UMODE ==== Mode +g ==== (partial note from the ircd-ratbox documentation) When a client is set +g, that user will be in "Caller ID" mode. Any user that messages a +g client will receive a notice saying that they are in +g (server side ignore) mode. The target client (who is set +g) will also receive a notice saying that so and so messaged them, and that they are in +g mode. The target of the message will only receive one notification per minute, from any client, in order to help prevent flooding. The sender will '''not''' have the rate limit, and will receive a notice saying the target is in +g mode every time they send a message. Note that this behavior is similar to the way AWAY messages are done. There are numerous benefits for both opers and regular users, including the ability to stop spambot messages from ever reaching your client, stopping private message and CTCP floods, and being able to sit on IRC in privacy. One question that arises is how to message specific users, while blocking out everyone else. The command ACCEPT is your answer. To add a user to your accept list, issue the raw command: /QUOTE ACCEPT &lt;nick&gt;,&lt;nick&gt;,&lt;nick&gt;,… That user will now be able to send messages to your client until the association is broken. Associations break in one of the following situations: when an accepted user QUIT's (or is on the other side of a split), you QUIT, or the accepted user changes their nick. The reason why a remote user's nick change will remove them from your accept list is so that you cannot track a user after they changed their nick. Viewing the accept list is also very easy. Issue the raw command: /QUOTE ACCEPT * Removing a user from your accept list is also simple. Issue the command: /QUOTE ACCEPT -&lt;nick&gt; === Channel Modes === You can see available channel modes using this command: /QUOTE HELP CMODE These extra modes are also available: * +r - registered - Users must be registered with services to JOIN * +S - ssl only - Requires SSL/TLS connections to join === IRC Services === To help not loose your favorite nick or channel, the IRC Services can register them so you're still in control. It also helps manage channel with a variety of tools. Look at the user introduction manual in the documentation below. List of Services: * ALIS: search available channels * USERSERV: register an account List of Services available with an account (see USERSERV): * NICKSERV: register nicknames * CHANSERV: register and manage channels * MEMOSERV: send and receive memos from other registered users ==== Additional Services for IRC Administrators ==== (exact privileges depends on trust and delegation) * OPERSERV: superadmin commands * JUPESERV: manage "jupes" (fake connections to prevent unwanted links) * GLOBAL: messaging all users * BANSERV: managing global bans * OPERBOT: manage the OperBot * WATCHSERV: spy on service commands (only available via DCC) You also may be able to access services via DCC CHAT, which is handy when a flood occurs, using: /DCC CHAT operserv == Documentation == * [http://docs.ratbox.org/svc_userintro.shtml IRC Services Introduction] == Technical Details == This service is made using: * [http://www.ratbox.org/ ircd-ratbox] * [http://services.ratbox.org/ ratbox-services] ba3f5ad5c32cbd48669d5e1739916e2b0ccc5621 293 292 2012-01-25T01:13:16Z Duck 2 /* Commands */ wikitext text/x-wiki IRC (Internet Relay Chat) is a chat system. We have our own internal network, formerly used to contact administrators and discuss with other users. Even is not advertise widely, external people may join the network, so you can invite your friend. == Prerequisite == None. == Access == === Using an IRC Software === To connect you need and IRC client, like for example: * [http://irssi.org/ Irssi] * [http://www.pidgin.im Pidgin] * [http://weechat.org/ WeeChat] You need to configure these parameters: * host: irc.milkypond.org * port: ** 6680 (if you want a secure connection using SSL/TLS) ** 6667 or 6669 (because 6667 is sometimes filtered) No password is needed to connect. === Using a Web Interface === Use the following URL: https://irconweb.milkypond.org/ == Official Channels == * #MilkyPond: main channel used to meet with other users and friends and ask general questions * #DuckCorp: contact with DuckCorp Administrators and technical discussions * #News: news feeds on IRC (deprecated but still working) == Contacting IRC Administrators == In case of problems on IRC you can find connected administrators using this command (mind the idle time): /QUOTE STATS p Beware IRC Administrators may not be DuckCorp Administrators. == Features == === Commands === You can see available commands using this command: /QUOTE HELP You can get help about a particular command using this command: /QUOTE HELP &lt;command&gt; ==== Additional Commands for IRC Administrators ==== All special commands are listed in the Oper MOTD. === User Modes === You can see available channel modes using this command: /QUOTE HELP UMODE ==== Mode +g ==== (partial note from the ircd-ratbox documentation) When a client is set +g, that user will be in "Caller ID" mode. Any user that messages a +g client will receive a notice saying that they are in +g (server side ignore) mode. The target client (who is set +g) will also receive a notice saying that so and so messaged them, and that they are in +g mode. The target of the message will only receive one notification per minute, from any client, in order to help prevent flooding. The sender will '''not''' have the rate limit, and will receive a notice saying the target is in +g mode every time they send a message. Note that this behavior is similar to the way AWAY messages are done. There are numerous benefits for both opers and regular users, including the ability to stop spambot messages from ever reaching your client, stopping private message and CTCP floods, and being able to sit on IRC in privacy. One question that arises is how to message specific users, while blocking out everyone else. The command ACCEPT is your answer. To add a user to your accept list, issue the raw command: /QUOTE ACCEPT &lt;nick&gt;,&lt;nick&gt;,&lt;nick&gt;,… That user will now be able to send messages to your client until the association is broken. Associations break in one of the following situations: when an accepted user QUIT's (or is on the other side of a split), you QUIT, or the accepted user changes their nick. The reason why a remote user's nick change will remove them from your accept list is so that you cannot track a user after they changed their nick. Viewing the accept list is also very easy. Issue the raw command: /QUOTE ACCEPT * Removing a user from your accept list is also simple. Issue the command: /QUOTE ACCEPT -&lt;nick&gt; === Channel Modes === You can see available channel modes using this command: /QUOTE HELP CMODE These extra modes are also available: * +r - registered - Users must be registered with services to JOIN * +S - ssl only - Requires SSL/TLS connections to join === IRC Services === To help not loose your favorite nick or channel, the IRC Services can register them so you're still in control. It also helps manage channel with a variety of tools. Look at the user introduction manual in the documentation below. List of Services: * ALIS: search available channels * USERSERV: register an account List of Services available with an account (see USERSERV): * NICKSERV: register nicknames * CHANSERV: register and manage channels * MEMOSERV: send and receive memos from other registered users ==== Additional Services for IRC Administrators ==== (exact privileges depends on trust and delegation) * OPERSERV: superadmin commands * JUPESERV: manage "jupes" (fake connections to prevent unwanted links) * GLOBAL: messaging all users * BANSERV: managing global bans * OPERBOT: manage the OperBot * WATCHSERV: spy on service commands (only available via DCC) You also may be able to access services via DCC CHAT, which is handy when a flood occurs, using: /DCC CHAT operserv == Documentation == * [http://docs.ratbox.org/svc_userintro.shtml IRC Services Introduction] == Technical Details == This service is made using: * [http://www.ratbox.org/ ircd-ratbox] * [http://services.ratbox.org/ ratbox-services] fb5bb1dd7f87083420480423f223a65da0a45c69 294 293 2012-01-25T01:16:46Z Duck 2 /* IRC Services */ wikitext text/x-wiki IRC (Internet Relay Chat) is a chat system. We have our own internal network, formerly used to contact administrators and discuss with other users. Even is not advertise widely, external people may join the network, so you can invite your friend. == Prerequisite == None. == Access == === Using an IRC Software === To connect you need and IRC client, like for example: * [http://irssi.org/ Irssi] * [http://www.pidgin.im Pidgin] * [http://weechat.org/ WeeChat] You need to configure these parameters: * host: irc.milkypond.org * port: ** 6680 (if you want a secure connection using SSL/TLS) ** 6667 or 6669 (because 6667 is sometimes filtered) No password is needed to connect. === Using a Web Interface === Use the following URL: https://irconweb.milkypond.org/ == Official Channels == * #MilkyPond: main channel used to meet with other users and friends and ask general questions * #DuckCorp: contact with DuckCorp Administrators and technical discussions * #News: news feeds on IRC (deprecated but still working) == Contacting IRC Administrators == In case of problems on IRC you can find connected administrators using this command (mind the idle time): /QUOTE STATS p Beware IRC Administrators may not be DuckCorp Administrators. == Features == === Commands === You can see available commands using this command: /QUOTE HELP You can get help about a particular command using this command: /QUOTE HELP &lt;command&gt; ==== Additional Commands for IRC Administrators ==== All special commands are listed in the Oper MOTD. === User Modes === You can see available channel modes using this command: /QUOTE HELP UMODE ==== Mode +g ==== (partial note from the ircd-ratbox documentation) When a client is set +g, that user will be in "Caller ID" mode. Any user that messages a +g client will receive a notice saying that they are in +g (server side ignore) mode. The target client (who is set +g) will also receive a notice saying that so and so messaged them, and that they are in +g mode. The target of the message will only receive one notification per minute, from any client, in order to help prevent flooding. The sender will '''not''' have the rate limit, and will receive a notice saying the target is in +g mode every time they send a message. Note that this behavior is similar to the way AWAY messages are done. There are numerous benefits for both opers and regular users, including the ability to stop spambot messages from ever reaching your client, stopping private message and CTCP floods, and being able to sit on IRC in privacy. One question that arises is how to message specific users, while blocking out everyone else. The command ACCEPT is your answer. To add a user to your accept list, issue the raw command: /QUOTE ACCEPT &lt;nick&gt;,&lt;nick&gt;,&lt;nick&gt;,… That user will now be able to send messages to your client until the association is broken. Associations break in one of the following situations: when an accepted user QUIT's (or is on the other side of a split), you QUIT, or the accepted user changes their nick. The reason why a remote user's nick change will remove them from your accept list is so that you cannot track a user after they changed their nick. Viewing the accept list is also very easy. Issue the raw command: /QUOTE ACCEPT * Removing a user from your accept list is also simple. Issue the command: /QUOTE ACCEPT -&lt;nick&gt; === Channel Modes === You can see available channel modes using this command: /QUOTE HELP CMODE These extra modes are also available: * +r - registered - Users must be registered with services to JOIN * +S - ssl only - Requires SSL/TLS connections to join === IRC Services === To help not loose your favorite nick or channel, the IRC Services can register them so you're still in control. It also helps manage channel with a variety of tools. Look at the user introduction manual in the documentation below. List of Services: * ALIS: search available channels * USERSERV: register an account List of Services available with an account (see USERSERV): * NICKSERV: register nicknames * CHANSERV: register and manage channels * MEMOSERV: send and receive memos from other registered users To get help on each service commands, use the following command: /QUOTE &lt;service&gt; HELP ==== Additional Services for IRC Administrators ==== (exact privileges depends on trust and delegation) * OPERSERV: superadmin commands * JUPESERV: manage "jupes" (fake connections to prevent unwanted links) * GLOBAL: messaging all users * BANSERV: managing global bans * OPERBOT: manage the OperBot * WATCHSERV: spy on service commands (only available via DCC) You also may be able to access services via DCC CHAT, which is handy when a flood occurs, using: /DCC CHAT operserv == Documentation == * [http://docs.ratbox.org/svc_userintro.shtml IRC Services Introduction] == Technical Details == This service is made using: * [http://www.ratbox.org/ ircd-ratbox] * [http://services.ratbox.org/ ratbox-services] c44f542745b5ad4ac7659b6c47f387f6f3a54f45 295 294 2012-01-25T01:28:21Z Duck 2 wikitext text/x-wiki [[wikipedia:Irc|IRC]] (Internet Relay Chat) is a chat system. We have our own internal network, formerly used to contact administrators and discuss with other users. Even is not advertise widely, external people may join the network, so you can invite your friend. == Prerequisite == None. == Access == === Using an IRC Software === To connect you need and IRC client, like for example: * [http://irssi.org/ Irssi] * [http://www.pidgin.im Pidgin] * [http://weechat.org/ WeeChat] You need to configure these parameters: * host: irc.milkypond.org * port: ** 6680 (if you want a secure connection using SSL/TLS) ** 6667 or 6669 (because 6667 is sometimes filtered) No password is needed to connect. === Using a Web Interface === Use the following URL: https://irconweb.milkypond.org/ == Official Channels == * #MilkyPond: main channel used to meet with other users and friends and ask general questions * #DuckCorp: contact with DuckCorp Administrators and technical discussions * #News: news feeds on IRC (deprecated but still working) == Contacting IRC Administrators == In case of problems on IRC you can find connected administrators using this command (mind the idle time): /QUOTE STATS p Beware IRC Administrators may not be DuckCorp Administrators. == Features == === Commands === You can see available commands using this command: /QUOTE HELP You can get help about a particular command using this command: /QUOTE HELP &lt;command&gt; ==== Additional Commands for IRC Administrators ==== All special commands are listed in the Oper MOTD. === User Modes === You can see available channel modes using this command: /QUOTE HELP UMODE ==== Mode +g ==== (partial note from the ircd-ratbox documentation) When a client is set +g, that user will be in "Caller ID" mode. Any user that messages a +g client will receive a notice saying that they are in +g (server side ignore) mode. The target client (who is set +g) will also receive a notice saying that so and so messaged them, and that they are in +g mode. The target of the message will only receive one notification per minute, from any client, in order to help prevent flooding. The sender will '''not''' have the rate limit, and will receive a notice saying the target is in +g mode every time they send a message. Note that this behavior is similar to the way AWAY messages are done. There are numerous benefits for both opers and regular users, including the ability to stop spambot messages from ever reaching your client, stopping private message and CTCP floods, and being able to sit on IRC in privacy. One question that arises is how to message specific users, while blocking out everyone else. The command ACCEPT is your answer. To add a user to your accept list, issue the raw command: /QUOTE ACCEPT &lt;nick&gt;,&lt;nick&gt;,&lt;nick&gt;,… That user will now be able to send messages to your client until the association is broken. Associations break in one of the following situations: when an accepted user QUIT's (or is on the other side of a split), you QUIT, or the accepted user changes their nick. The reason why a remote user's nick change will remove them from your accept list is so that you cannot track a user after they changed their nick. Viewing the accept list is also very easy. Issue the raw command: /QUOTE ACCEPT * Removing a user from your accept list is also simple. Issue the command: /QUOTE ACCEPT -&lt;nick&gt; === Channel Modes === You can see available channel modes using this command: /QUOTE HELP CMODE These extra modes are also available: * +r - registered - Users must be registered with services to JOIN * +S - ssl only - Requires SSL/TLS connections to join === IRC Services === To help not loose your favorite nick or channel, the IRC Services can register them so you're still in control. It also helps manage channel with a variety of tools. Look at the user introduction manual in the documentation below. List of Services: * ALIS: search available channels * USERSERV: register an account List of Services available with an account (see USERSERV): * NICKSERV: register nicknames * CHANSERV: register and manage channels * MEMOSERV: send and receive memos from other registered users To get help on each service commands, use the following command: /QUOTE &lt;service&gt; HELP ==== Additional Services for IRC Administrators ==== (exact privileges depends on trust and delegation) * OPERSERV: superadmin commands * JUPESERV: manage "jupes" (fake connections to prevent unwanted links) * GLOBAL: messaging all users * BANSERV: managing global bans * OPERBOT: manage the OperBot * WATCHSERV: spy on service commands (only available via DCC) You also may be able to access services via DCC CHAT, which is handy when a flood occurs, using: /DCC CHAT operserv == Documentation == * [http://docs.ratbox.org/svc_userintro.shtml IRC Services Introduction] == Technical Details == This service is made using: * [http://www.ratbox.org/ ircd-ratbox] * [http://services.ratbox.org/ ratbox-services] 0466ef5cd32e063ee86c9433f80cb2d6baed93c2 0 56 296 2012-01-25T02:02:42Z Duck 2 Created page with "An [[wikipedia:IRC_bouncer#IRC|IRC Bouncer]] is a proxy, relaying connection to one or multiple IRC servers. When you disconnect from the bouncer, the bouncer keep your connectio…" wikitext text/x-wiki An [[wikipedia:IRC_bouncer#IRC|IRC Bouncer]] is a proxy, relaying connection to one or multiple IRC servers. When you disconnect from the bouncer, the bouncer keep your connections alive and store messages sent to you or in channels you joined. When you are back connected to the bouncer, all your channels and private chats are automatically reopened, and you can access messages you missed. == Prerequisite == You need to ask an administrator for an account. You need to provide the following information: * default nick / user / realname * an encrypted password generated using the ''bipmkpw'' command (available on Thorfinn, or in the ''Bip'' software) * list of networks you wish to connect to * list of channel you want to autojoin (for each network) * an other specific settings you wish == Access == To connect you need and IRC client, as the bouncer acts like an IRC server. See the [[IRC#Using_an_IRC_Software|here]] for examples of usable softwares. The bouncer is able to connect to multiple networks, but so as not to mix connections (which may have users and channels of the same name, creating a conflict), you need to connect to the bouncer multiple times, one for each network. You need to configure these parameters for each connection: * host: irc-bouncer.duckcorp.org * port: 7778 * password: &lt;user&gt;:&lt;user-password&gt;:&lt;connection&gt; &lt;user&gt; is your username, &lt;user-password&gt; your password, and &lt;connection&gt; the name of the network you want to connect to (see the list of available networks below). == Available Networks == These are the available networks you may access, depending on your configuration: * milkypond * minbif * debianjp * freenode * oftc * ircnet * epiknet * gimpnet * rezosup * iie * n7mm == Technical Details == This service is made using: * [http://bip.milkypond.org/ Bip] a14bbb7dc7d718e4e8dc761c03584e726e81dfff 10 57 299 2012-01-25T22:35:42Z Duck 2 Created page with "|" wikitext text/x-wiki | 3eb416223e9e69e6bb8ee19793911ad1ad2027d8 10 58 300 2012-01-25T22:40:50Z Duck 2 Created page with "{| class="wikitable" |+ Service '{{BASEPAGENAME}}' ! Description || {{{description}}} |- ! Prerequisite || {{{prerequisite}}} |- ! Account || {{#if {{{account}}} | {{#ifeq: {{{ac…" wikitext text/x-wiki {| class="wikitable" |+ Service '{{BASEPAGENAME}}' ! Description || {{{description}}} |- ! Prerequisite || {{{prerequisite}}} |- ! Account || {{#if {{{account}}} | {{#ifeq: {{{account}}} | global | style="color: green;" {{!}} [[GlobalAccount|Global]] | style="color: red;" {{!}} No }} | none }} }} 25b5e8ef1998288fc05c09fa9225fb31cd43e3bc 301 300 2012-01-25T22:41:58Z Duck 2 wikitext text/x-wiki {| class="wikitable" |+ Service '{{BASEPAGENAME}}' ! Description || {{{description}}} |- ! Prerequisite || {{{prerequisite}}} |- ! Account || {{#if {{{account}}} | {{#ifeq: {{{account}}} | global | style="color: green;" {{!}} [[GlobalAccount|Global]] | style="color: red;" {{!}} No }} | none }} |} bc4d280d3f94e32ac10e976396c0045d768a7e4c 302 301 2012-01-25T23:04:34Z Duck 2 wikitext text/x-wiki {| class="wikitable" |+ Service '{{BASEPAGENAME}}' ! Description || {{{description|}}} |- ! Prerequisite || {{{prerequisite|}}} |- ! Account || {{#if {{{account|}}} | {{#ifeq: {{{account}}} | global | style="color: green;" {{!}} [[GlobalAccount{{!}}Global]] | style="color: red;" {{!}} Local }} | none }} |} d1ccecb5c28140c388afeca589f5c6147ac709b8 303 302 2012-01-25T23:08:16Z Duck 2 wikitext text/x-wiki {| class="wikitable" |+ Service '{{BASEPAGENAME}}' ! Description | {{{description|}}} |- ! Prerequisite | {{{prerequisite|}}} |- ! Account | {{#if {{{account|}}} | {{#ifeq: {{{account|}}} | global | style="color: green;" {{!}} [[GlobalAccount{{!}}Global]] | style="color: red;" {{!}} Local }} | none }} |} 70aafada7802a4ba2644ab980f3f91564cff8297 304 303 2012-01-25T23:13:37Z Duck 2 wikitext text/x-wiki {| class="wikitable" |+ Service '{{BASEPAGENAME}}' ! Description | {{{description|}}} |- ! Prerequisite | {{{prerequisite|}}} |- ! Account | {{#if: {{{account|}}} | {{#ifeq: {{{account|}}} | global | style="color: green;" {{!}} [[GlobalAccount{{!}}Global]] | style="color: red;" {{!}} Local }} | none }} |} e2e1014296fd3158162bd8a623c28538f5595482 305 304 2012-01-25T23:19:32Z Duck 2 wikitext text/x-wiki {| class="wikitable" |+ Service '{{BASEPAGENAME}}' ! Description | {{{description|}}} |- ! Prerequisite | {{{prerequisite|}}} |- ! [[AccountType|Account ]] | {{#if: {{{account|}}} | {{#ifeq: {{{account|}}} | global | style="color: blue;" {{!}} Global | style="color: orange;" {{!}} Local }} | none }} |} 967106a25e5f5e56c6e95b466cb8c09be497b6a6 10 59 306 2012-01-25T23:31:04Z Duck 2 Created page with "{{#titleparts:{{PAGENAME}}|1|-1|}}" wikitext text/x-wiki {{#titleparts:{{PAGENAME}}|1|-1|}} 9b182a096e3946226096cfc0d89b43ab78ee4781 309 306 2012-01-25T23:31:52Z Duck 2 Protected "[[Template:TITLEPAGE]]" ([edit=sysop] (indefinite) [move=sysop] (indefinite)) wikitext text/x-wiki {{#titleparts:{{PAGENAME}}|1|-1|}} 9b182a096e3946226096cfc0d89b43ab78ee4781 10 58 307 305 2012-01-25T23:31:19Z Duck 2 wikitext text/x-wiki {| class="wikitable" |+ Service '{{TITLEPAGE}}' ! Description | {{{description|}}} |- ! Prerequisite | {{{prerequisite|}}} |- ! [[AccountType|Account ]] | {{#if: {{{account|}}} | {{#ifeq: {{{account|}}} | global | style="color: blue;" {{!}} Global | style="color: orange;" {{!}} Local }} | none }} |} 67ff4b877adb8acd3902608da025b32b962c678b 308 307 2012-01-25T23:31:39Z Duck 2 Protected "[[Template:Service]]" ([edit=sysop] (indefinite) [move=sysop] (indefinite)) wikitext text/x-wiki {| class="wikitable" |+ Service '{{TITLEPAGE}}' ! Description | {{{description|}}} |- ! Prerequisite | {{{prerequisite|}}} |- ! [[AccountType|Account ]] | {{#if: {{{account|}}} | {{#ifeq: {{{account|}}} | global | style="color: blue;" {{!}} Global | style="color: orange;" {{!}} Local }} | none }} |} 67ff4b877adb8acd3902608da025b32b962c678b 314 308 2012-01-26T00:22:11Z Duck 2 wikitext text/x-wiki {| class="wikitable" |+ Service '{{TITLEPAGE}}' ! Description | colspan="3" | {{{description|}}} |- ! Prerequisite | colspan="3" | {{{prerequisite|}}} |- ! [[AccountType|Account]] | {{#if: {{{account|}}} | {{#ifeq: {{{account|}}} | global | style="color: blue;" {{!}} Global | style="color: orange;" {{!}} Local }} | none }} ! IPv6 Ready | {{#if: {{{ipv6_ready|}}} | {{#ifeq: {{{ipv6_ready|}}} | true | style="color: blue;" {{!}} Yes | style="color: orange;" {{!}} No }} | N/A }} |- ! [[SecurityLevel|Security Level]] | {{#if: {{{security_level|}}} | {{#ifeq: {{{security_level|}}} | high | style="color: green;" {{!}} High | {{#ifeq: {{{security_level|}}} | medium | style="color: blue;" {{!}} Medium | style="color: orange;" {{!}} Low }} | N/A }} |} fda0d1755d871a6a89d36832ef86d8a6bcb7288f 315 314 2012-01-26T00:27:20Z Duck 2 wikitext text/x-wiki {| class="wikitable" |+ Service '{{TITLEPAGE}}' ! Description | colspan="4" | {{{description|}}} |- ! Prerequisite | colspan="4" | {{{prerequisite|}}} |- ! [[AccountType|Account]] | {{#if: {{{account|}}} | {{#ifeq: {{{account|}}} | global | style="color: blue;" {{!}} Global | style="color: orange;" {{!}} Local }} | none }} ! IPv6 Ready | {{#if: {{{ipv6_ready|}}} | {{#ifeq: {{{ipv6_ready|}}} | true | style="color: blue;" {{!}} Yes | style="color: orange;" {{!}} No }} | N/A }} | rowspan="2" | |- ! [[SecurityLevel|Security Level]] | {{#if: {{{security_level|}}} | {{#ifeq: {{{security_level|}}} | high | style="color: green;" {{!}} High | {{#ifeq: {{{security_level|}}} | medium | style="color: blue;" {{!}} Medium | style="color: orange;" {{!}} Low }} }} | N/A }} | |} 96b74f52dd8e0880df5cac951c3cdb49d5ac4ed6 316 315 2012-01-26T00:28:20Z Duck 2 wikitext text/x-wiki {| class="wikitable" |+ Service '{{TITLEPAGE}}' ! Description | colspan="4" | {{{description|}}} |- ! Prerequisite | colspan="4" | {{{prerequisite|}}} |- ! [[AccountType|Account]] | {{#if: {{{account|}}} | {{#ifeq: {{{account|}}} | global | style="color: blue;" {{!}} Global | style="color: orange;" {{!}} Local }} | none }} ! IPv6 Ready | {{#if: {{{ipv6_ready|}}} | {{#ifeq: {{{ipv6_ready|}}} | true | style="color: blue;" {{!}} Yes | style="color: orange;" {{!}} No }} | N/A }} | rowspan="2" style="width: 85%;" | |- ! [[SecurityLevel|Security Level]] | {{#if: {{{security_level|}}} | {{#ifeq: {{{security_level|}}} | high | style="color: green;" {{!}} High | {{#ifeq: {{{security_level|}}} | medium | style="color: blue;" {{!}} Medium | style="color: orange;" {{!}} Low }} }} | N/A }} | |} 9cb1bd5c17959ed47da797815d8a1595f4181e7f 317 316 2012-01-26T00:48:38Z Duck 2 wikitext text/x-wiki {| class="wikitable" |+ Service '{{TITLEPAGE}}' ! Description | colspan="4" | {{{description|}}} zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz fffffffffffffffffffffffffffffffffffffffffffffff |- ! Prerequisite | colspan="4" | {{#if: {{{prerequisite|}}} | {{{prerequisite|}}} | none }} |- ! style="width: 12%;" | [[AccountType|Account]] | style="width: 12%;" | {{#if: {{{account|}}} | {{#ifeq: {{{account|}}} | global | style="color: blue;" {{!}} Global | style="color: orange;" {{!}} Local }} | none }} ! style="width: 12%;" | [[wikipedia:Ipv6|IPv6 Ready]] | style="width: 12%;" | {{#if: {{{ipv6_ready|}}} | {{#ifeq: {{{ipv6_ready|}}} | true | style="color: blue;" {{!}} Yes | style="color: orange;" {{!}} No }} | N/A }} | rowspan="2" | |- ! [[SecurityLevel|Security Level]] | {{#if: {{{security_level|}}} | {{#ifeq: {{{security_level|}}} | high | style="color: green;" {{!}} High | {{#ifeq: {{{security_level|}}} | medium | style="color: blue;" {{!}} Medium | style="color: orange;" {{!}} Low }} }} | N/A }} | |} 59f4674592f81c6225b8c3df10c666afe9c39b86 318 317 2012-01-26T00:50:48Z Duck 2 wikitext text/x-wiki {| class="wikitable" |+ Service '{{TITLEPAGE}}' ! Description | colspan="4" | {{{description|}}} zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz fffffffffffffffffffffffffffffffffffffffffffffff |- ! Prerequisite | colspan="4" | {{#if: {{{prerequisite|}}} | {{{prerequisite|}}} | none }} |- ! style="width: 12%;" | [[AccountType|Account]] | style="width: 12%;" {{#if: {{{account|}}} | {{#ifeq: {{{account|}}} | global | style="color: blue;" {{!}} Global | style="color: orange;" {{!}} Local }} | {{!}} none }} ! style="width: 12%;" | [[wikipedia:Ipv6|IPv6 Ready]] | style="width: 12%;" {{#if: {{{ipv6_ready|}}} | {{#ifeq: {{{ipv6_ready|}}} | true | style="color: blue;" {{!}} Yes | style="color: orange;" {{!}} No }} | {{!}} N/A }} | rowspan="2" | |- ! [[SecurityLevel|Security Level]] | {{#if: {{{security_level|}}} | {{#ifeq: {{{security_level|}}} | high | style="color: green;" {{!}} High | {{#ifeq: {{{security_level|}}} | medium | style="color: blue;" {{!}} Medium | style="color: orange;" {{!}} Low }} }} | N/A }} | |} 4bc9b7537ee091af6f7f29cd39bf063fa5e592d1 319 318 2012-01-26T00:54:24Z Duck 2 wikitext text/x-wiki {| class="wikitable" |+ Service '{{TITLEPAGE}}' ! Description | colspan="4" | {{{description|}}} |- ! Prerequisite | colspan="4" | {{#if: {{{prerequisite|}}} | {{{prerequisite|}}} | none }} |- ! style="width: 12%;" | [[AccountType|Account]] | style="width: 12%;" | {{#if: {{{account|}}} | {{#ifeq: {{{account|}}} | global | <span style="color: blue;">Global</span> | <span style="color: orange;">Local</span> }} | none }} ! style="width: 12%;" | [[wikipedia:Ipv6|IPv6 Ready]] | style="width: 12%;" | {{#if: {{{ipv6_ready|}}} | {{#ifeq: {{{ipv6_ready|}}} | true | <span style="color: blue;">Yes</span> | <span style="color: orange;">No</span> }} | N/A }} | rowspan="2" | |- ! [[SecurityLevel|Security Level]] | {{#if: {{{security_level|}}} | {{#ifeq: {{{security_level|}}} | high | style="color: green;" {{!}} High | {{#ifeq: {{{security_level|}}} | medium | style="color: blue;" {{!}} Medium | style="color: orange;" {{!}} Low }} }} | N/A }} | |} 9384b781dd2decaa8152a4d9fc87b6fed0976461 321 319 2012-01-26T19:09:25Z Duck 2 wikitext text/x-wiki {| class="wikitable" |+ Service '{{TITLEPAGE}}' ! Description | colspan="4" | {{{description|}}} |- ! Prerequisite | colspan="4" | {{#if: {{{prerequisite|}}} | {{{prerequisite|}}} | none }} |- ! style="width: 17%;" | [[AccountType|Account]] | style="width: 12%;" | {{#if: {{{account|}}} | {{#ifeq: {{{account|}}} | global | <span style="color: blue;">Global</span> | <span style="color: orange;">Local</span> }} | none }} ! style="width: 17%;" | [[wikipedia:Ipv6|IPv6 Ready]] | style="width: 12%;" | {{#if: {{{ipv6|}}} | {{#ifeq: {{{ipv6|}}} | true | <span style="color: blue;">Yes</span> | <span style="color: orange;">No</span> }} | N/A }} | |- ! Security Notes | colspan="4" | {{{security_notes|}}} |} 68a63290c9025681ba8882c3926b5887d62f0d67 323 321 2012-01-26T20:48:10Z Duck 2 wikitext text/x-wiki {| class="wikitable" |+ Service '{{TITLEPAGE}}' ! Description | colspan="4" | {{{description|}}} |- ! Prerequisite | colspan="4" | {{#if: {{{prerequisite|}}} | {{{prerequisite|}}} | none }} |- ! style="width: 17%;" | [[AccountType|Account]] | style="width: 12%;" | {{#if: {{{account|}}} | {{#ifeq: {{{account|}}} | global | <span style="color: green;">Global</span> | {{#ifeq: {{{account|}}} | global-reg | <span style="color: blue;">Global (registration required)</span> | <span style="color: orange;">Local (registration required)</span> }} }} | none }} ! style="width: 17%;" | [[wikipedia:Ipv6|IPv6 Ready]] | style="width: 12%;" | {{#if: {{{ipv6|}}} | {{#ifeq: {{{ipv6|}}} | true | <span style="color: blue;">Yes</span> | <span style="color: orange;">No</span> }} | N/A }} | |- ! Security Notes | colspan="4" | {{{security_notes|}}} |} 2dd251bdb1f82e21d4af36cca67a579edf8e09ec 324 323 2012-01-26T21:02:50Z Duck 2 wikitext text/x-wiki {| class="wikitable" |+ Service '{{TITLEPAGE}}' ! Description | colspan="4" | {{{description|}}} |- ! Prerequisite | colspan="4" | {{#if: {{{prerequisite|}}} | {{{prerequisite|}}} | none }} |- ! style="width: 17%;" | [[AccountType|Account]] | style="width: 15%;" | {{#if: {{{account|}}} | {{#ifeq: {{{account|}}} | global | <span style="color: green;">Global</span> | {{#ifeq: {{{account|}}} | global-reg | <span style="color: blue;">Global (registration required)</span> | <span style="color: orange;">Local (registration required)</span> }} }} | none }} ! style="width: 17%;" | [[wikipedia:Ipv6|IPv6 Ready]] | style="width: 8%;" | {{#if: {{{ipv6|}}} | {{#ifeq: {{{ipv6|}}} | true | <span style="color: blue;">Yes</span> | <span style="color: orange;">No</span> }} | N/A }} | |- ! Security Notes | colspan="4" | {{{security_notes|}}} |} 33d4fb126318f7b18b9423523092e4f6cb0e7ee1 325 324 2012-01-26T21:03:56Z Duck 2 wikitext text/x-wiki {| class="wikitable" |+ Service '{{TITLEPAGE}}' ! Description | colspan="4" | {{{description|}}} |- ! Prerequisite | colspan="4" | {{#if: {{{prerequisite|}}} | {{{prerequisite|}}} | none }} |- ! style="width: 15%;" | [[AccountType|Account]] | style="width: 15%;" | {{#if: {{{account|}}} | {{#ifeq: {{{account|}}} | global | <span style="color: green;">Global</span> | {{#ifeq: {{{account|}}} | global-reg | <span style="color: blue;">Global (registration required)</span> | <span style="color: orange;">Local (registration required)</span> }} }} | none }} ! style="width: 17%;" | [[wikipedia:Ipv6|IPv6 Ready]] | style="width: 8%;" | {{#if: {{{ipv6|}}} | {{#ifeq: {{{ipv6|}}} | true | <span style="color: blue;">Yes</span> | <span style="color: orange;">No</span> }} | N/A }} | |- ! Security Notes | colspan="4" | {{{security_notes|}}} |} 63c27a482a0d27d550a5ee2f76fe87d7c0b67212 326 325 2012-01-26T21:04:41Z Duck 2 wikitext text/x-wiki {| class="wikitable" |+ Service '{{TITLEPAGE}}' ! Description | colspan="4" | {{{description|}}} |- ! Prerequisite | colspan="4" | {{#if: {{{prerequisite|}}} | {{{prerequisite|}}} | none }} |- ! style="width: 15%;" | [[AccountType|Account]] | style="width: 15%;" | {{#if: {{{account|}}} | {{#ifeq: {{{account|}}} | global | <span style="color: green;">Global</span> | {{#ifeq: {{{account|}}} | global-reg | <span style="color: blue;">Global (registration required)</span> | <span style="color: orange;">Local (registration required)</span> }} }} | none }} ! style="width: 15%;" | [[wikipedia:Ipv6|IPv6 Ready]] | style="width: 8%;" | {{#if: {{{ipv6|}}} | {{#ifeq: {{{ipv6|}}} | true | <span style="color: blue;">Yes</span> | <span style="color: orange;">No</span> }} | N/A }} | |- ! Security Notes | colspan="4" | {{{security_notes|}}} |} e689f89c128bce7169fdb32ea53d1c65fe6147ad 340 326 2012-01-26T23:07:11Z Duck 2 wikitext text/x-wiki {| class="wikitable" |+ Service '{{TITLEPAGE}}' ! Description | colspan="4" | {{{description|}}} |- ! Prerequisite | colspan="4" | {{#if: {{{prerequisite|}}} | {{{prerequisite|}}} | none }} |- ! style="width: 15%;" | [[AccountType|Account]] | style="width: 15%;" | {{#if: {{{account|}}} | {{#ifeq: {{{account|}}} | global | <span style="color: green;">Global</span> | {{#ifeq: {{{account|}}} | global-reg | <span style="color: green;">Global (registration required)</span> | <span style="color: orange;">Local (registration required)</span> }} }} | none }} ! style="width: 15%;" | [[wikipedia:Ipv6|IPv6 Ready]] | style="width: 8%;" | {{#if: {{{ipv6|}}} | {{#ifeq: {{{ipv6|}}} | true | <span style="color: blue;">Yes</span> | <span style="color: orange;">No</span> }} | N/A }} | |- ! Security Notes | colspan="4" | {{{security_notes|}}} |} 961863439d22687ecc58c36054021d6807574bbf 341 340 2012-01-26T23:07:34Z Duck 2 wikitext text/x-wiki {| class="wikitable" |+ Service '{{TITLEPAGE}}' ! Description | colspan="4" | {{{description|}}} |- ! Prerequisite | colspan="4" | {{#if: {{{prerequisite|}}} | {{{prerequisite|}}} | none }} |- ! style="width: 15%;" | [[AccountType|Account]] | style="width: 15%;" | {{#if: {{{account|}}} | {{#ifeq: {{{account|}}} | global | <span style="color: green;">Global</span> | {{#ifeq: {{{account|}}} | global-reg | <span style="color: blue;">Global (registration required)</span> | <span style="color: orange;">Local (registration required)</span> }} }} | none }} ! style="width: 15%;" | [[wikipedia:Ipv6|IPv6 Ready]] | style="width: 8%;" | {{#if: {{{ipv6|}}} | {{#ifeq: {{{ipv6|}}} | true | <span style="color: green;">Yes</span> | <span style="color: orange;">No</span> }} | N/A }} | |- ! Security Notes | colspan="4" | {{{security_notes|}}} |} 690c1cc313b006c5eb482882edaa34598dd3c9ac 10 57 310 299 2012-01-25T23:32:27Z Duck 2 Protected "[[Template:!]]" ([edit=sysop] (indefinite) [move=sysop] (indefinite)) wikitext text/x-wiki | 3eb416223e9e69e6bb8ee19793911ad1ad2027d8 0 49 311 279 2012-01-25T23:33:00Z Duck 2 wikitext text/x-wiki {{Template:Service | description = Available services: * multiple email addresses (mailboxes or redirections) based on ''milkypond.org'' (or maybe ''duckcorp.org'') domain(s) or you own domain(s) * roaming accounts to be able to send emails wherever you are | prerequisite = You need to ask an administrator for an account. | account = global }} == Access == === Using a Mail Reader === You can retrieve your mails, in case of a real mailbox, using either: * IMAP+TLS (TCP 143) / IMAPS (TCP 993) on imap.duckcorp.org * or POP3+TLS (TCP 110) / POP3S (TCP 995) on pop.duckcorp.org The IMAP protocol is recommended over POP3, as it provides many interesting features. If you want to download all your mails absolutely at home, loosing the ability to read your mail from anywhere on the planet, you can do that with IMAP too (look at your mail client settings). You can use our servers to send mails out too via smtp.duckcorp.org using: * SMTP+TLS (TCP 25) / SMTPS (TCP 465) * and SASL authentication === Using a Web Interface === Several [https://webmail.duckcorp.org/ webmail interfaces] are available. == Mailboxes Features == === Antivirus and Antispam === Mails stored on our server are checked upon arrival for viruses and SPAMs. Mail redirected to a third party mailbox are not, not to mess with the strategy of the the final destination (which could arm learning greatly). Mails being viruses are suppressed automatically upon arrival. Once in a week, an extra antivirus check is done on all hosted mailboxes, to remove viruses not detected at the time it arrived (our antivirus database is updated daily), so you may see such mail disappear from your mailbox, don't fear. SPAMs are more difficult to detect, and it is an error-prone process, so we chose to use a learning software intead of using a global database. On the bright side of things, you would never loose mails and the software should be able to learn what is a SPAM from '''your''' point of view (which has proved to differ slightly between our users), but on the grey side you will have to teach him regulary to avoid errors. When your account is created, it acts like an empty headed body letting everything through, but after a few weeks of teaching it is able to recognise most of your habits and block a lot of annoying SPAM. To teach the system, you can: * use the [https://spamfilter.duckcorp.org/ web interface] to retrain from errors in the ''History'' page * resend SPAM to dc-spam@duckcorp.org and HAM (non-SPAM) to dc-ham@duckcorp.org *: {{warning}} PLEASE TAKE CARE to use the ''resend'' function of your mailer and never use ''forward'', which would result in '''yourself''' being considered as spam or ham You can yourself setup a few parameters in the ''Preferences'' page of the [https://spamfilter.duckcorp.org/ web interface], mostly: * how the system should train: ** TEFT (''On every new message scanned by the filter''): useful to learn very quickly especially on a new mailbox or when you've got tons of spam on your addresses, but you need to train it regulary (daily is better) or it will learn wrong (very quickly too !) ** TOE (''Only when the filter makes a mistake''): slow learning, but if you don't have time for training very often or go on long holidays without internet access this mode will give you a stable behavior ** TUM (''Only with new data or if the filter makes a mistake''): trade-off between the two previous modes, learn quite fast and not too demanding, adapts better to new SPAMs then TOE * filter sensitivity: you can ask the system to be more or less aggressive * message handling: ** ''Quarantine the message'': mails are not delivered to your mailbox but retained by the system and you can only manage them through the [https://spamfilter.duckcorp.org/ web interface] ; if you retrain a quarantined mail as HAM, it will be freed from quarantine and delivered in your mailbox at once ; in this mode, you need to flush your quarantine once in a while ** ''Tag the Subject header with'': mails are delivered with a modified title (which is a tad ugly) ** ''Deliver the message normally with a X-DSPAM-Result header'': mails are delivered with a special field in your mail headers (not always visible depending on your mail client and its configuration) ; this is quite handy if you prefer SPAMs arranged in a specific folder * ''Disable DSPAM filtering'': you may switch off filtering at your own risk We strongly recommend using TEFT with daily training for a few weeks then switching to TUM. If you need to go away for a long time, switching to TOE is recommended. Using the quarantine feature is also a safe choice, as the web interface is quite easy to use. === Mail Filtering === With your favourite mail client, you can probably filter your mails in proper folders already. Nevertheless, this can be a annoying operation: * blocking you mail client for a long time if you have to process plenty of mails * downloading each mail information, and sometimes content (depending on your filters), is lenghty too, and cost much bandwidth * syncing filters accross your machines (home desktop, laptop, office machine…) is a pain in the ass * processing only when you're online prevents triggering actions in a timely manner (automatic redirect, vacation messages…), and running a machine 24/7 with a mail client polling new mails every 30s is not a solution We provide a much better way to do this using the [[wikipedia:Sieve_(mail_filtering_language)|SIEVE]] filters. Shortly, SIEVE is a language dedicated to expressing mail filters. Our server is able to process your mails according to these filters as soon as they arrive. You then don't have to care about them anymore, and may use light mail clients or webmails when you're not on your machine with your favourite software. To push your filters on the server, a dedicated protocol exists: : MANAGESIEVE (TCP 4190) on sieve.duckcorp.org Several softwares support managing SIEVE rules: * Icedove/Thunderbird using the SIEVE extension (in xul-ext-sieve Debian package) provides a rules editor * Horde (Ingo) provides an easy to use web interface * Squirrelmail with the Avelsieve extension provides an easy to use web interface * Roundcube with an extension provides an easy to use web interface * sieve-connect provides a CLI to upload/download/activate your rules files (tell us if you know more software supporting this feature) You can read more info about SIEVE here: * supported SIEVE features on our server: http://pigeonhole.dovecot.org/ * http://www.fastmail.fm/docs/sieve/ * http://sieve.info/ === Fetching eMails from an External Mailbox === {{todo}} === Shared/Public Folders === You may need to share mails or messages with friends or people you do stuff with (in a project or association). Depending on your needs, two solutions are possible: * share some of your own private folders, thus called ''shared folders'' * manage a special folder hierarchy, called ''public folders'' (even if they may not be accessible to everyone) Through IMAP, or our webmails internally using IMAP, it is possible to partition the folder hierarchy into ''namespaces''. Traditionally you are using the root namespace for your private folders. Additionnal namespaces can be created and will appear among your own folders or separate, depending on your mail client's choice of representation. To avoid name clashes, we decided to prefix all additionnal namespace names with a '''#'''. Since 2011-05-14, the following extra namespaces are created and reserved: * #Shared, containing all folders other users decided to share with you * #MilkyPond, containing public MP/DC information mailboxes you may subscribe at will Using IMAP, it is possible to setup rights (read only, write allowed…) to your own folders in order to share them with other users, or group of users. Public folders are owned by noone, and must be created by DC administrators ; if you need one, send us a request and we may be able to create it and delegate administration to your care (namespace name is subject to approval). Once created, public folders can be administered like shared folders. Client mail softwares support: * Horde: support namespaces, shared folders configurable via ''Options->Share Folders'' menu but no ACLs for public folders * Icedove/Thunderbird: support namespaces, shared and public folders configurable via folder selection and ''Tools->Imap-ACL'' menu action Most other softwares have namespace support only, so you should be able to use shared/public folders you have rights on but not configure them yourself (tell us if you know more software supporting this feature) == Limitations == === Maximum Mail Size === Mail you send or receive are limited to 10MB. If you need to transmit much bigger data, then a mail transport is not appropriate, you'd better use a file sharing method instead. === Quotas === Even if it would be nice to live without it, we had to establish quotas to force people sort their mails out once in a while and delete useless things instead of leaving an ever-growing mess behind. The default quota is 512MB which is not that big but should match needs of most users. This said, you may ask us for more and there's no reason we would refuse a reasonable demand. == Technical Details == This service is made using: * [http://www.postfix.org/ Postfix] * [http://dovecot.org/ Dovecot] * [http://dspam.sourceforge.net DSPAM] * [http://johannes.sipsolutions.net/Projects/dovecot-antispam dovecot-antispam] * [http://www.horde.org/ Horde] * [http://www.squirrelmail.org/ SquirrelMail] * [http://www.roundcube.net/ RoundCube] 1c5dada8736516b4ffce57cba10d2c877f132d48 320 311 2012-01-26T00:59:05Z Duck 2 wikitext text/x-wiki {{Template:Service | description = Available services: * multiple email addresses (mailboxes or redirections) based on ''milkypond.org'' (or maybe ''duckcorp.org'') domain(s) or you own domain(s) * roaming accounts to be able to send emails wherever you are | prerequisite = You need to ask an administrator for an account. | account = global | ipv6_ready = true | security_level = medium }} == Access == === Using a Mail Reader === You can retrieve your mails, in case of a real mailbox, using either: * IMAP+TLS (TCP 143) / IMAPS (TCP 993) on imap.duckcorp.org * or POP3+TLS (TCP 110) / POP3S (TCP 995) on pop.duckcorp.org The IMAP protocol is recommended over POP3, as it provides many interesting features. If you want to download all your mails absolutely at home, loosing the ability to read your mail from anywhere on the planet, you can do that with IMAP too (look at your mail client settings). You can use our servers to send mails out too via smtp.duckcorp.org using: * SMTP+TLS (TCP 25) / SMTPS (TCP 465) * and SASL authentication === Using a Web Interface === Several [https://webmail.duckcorp.org/ webmail interfaces] are available. == Mailboxes Features == === Antivirus and Antispam === Mails stored on our server are checked upon arrival for viruses and SPAMs. Mail redirected to a third party mailbox are not, not to mess with the strategy of the the final destination (which could arm learning greatly). Mails being viruses are suppressed automatically upon arrival. Once in a week, an extra antivirus check is done on all hosted mailboxes, to remove viruses not detected at the time it arrived (our antivirus database is updated daily), so you may see such mail disappear from your mailbox, don't fear. SPAMs are more difficult to detect, and it is an error-prone process, so we chose to use a learning software intead of using a global database. On the bright side of things, you would never loose mails and the software should be able to learn what is a SPAM from '''your''' point of view (which has proved to differ slightly between our users), but on the grey side you will have to teach him regulary to avoid errors. When your account is created, it acts like an empty headed body letting everything through, but after a few weeks of teaching it is able to recognise most of your habits and block a lot of annoying SPAM. To teach the system, you can: * use the [https://spamfilter.duckcorp.org/ web interface] to retrain from errors in the ''History'' page * resend SPAM to dc-spam@duckcorp.org and HAM (non-SPAM) to dc-ham@duckcorp.org *: {{warning}} PLEASE TAKE CARE to use the ''resend'' function of your mailer and never use ''forward'', which would result in '''yourself''' being considered as spam or ham You can yourself setup a few parameters in the ''Preferences'' page of the [https://spamfilter.duckcorp.org/ web interface], mostly: * how the system should train: ** TEFT (''On every new message scanned by the filter''): useful to learn very quickly especially on a new mailbox or when you've got tons of spam on your addresses, but you need to train it regulary (daily is better) or it will learn wrong (very quickly too !) ** TOE (''Only when the filter makes a mistake''): slow learning, but if you don't have time for training very often or go on long holidays without internet access this mode will give you a stable behavior ** TUM (''Only with new data or if the filter makes a mistake''): trade-off between the two previous modes, learn quite fast and not too demanding, adapts better to new SPAMs then TOE * filter sensitivity: you can ask the system to be more or less aggressive * message handling: ** ''Quarantine the message'': mails are not delivered to your mailbox but retained by the system and you can only manage them through the [https://spamfilter.duckcorp.org/ web interface] ; if you retrain a quarantined mail as HAM, it will be freed from quarantine and delivered in your mailbox at once ; in this mode, you need to flush your quarantine once in a while ** ''Tag the Subject header with'': mails are delivered with a modified title (which is a tad ugly) ** ''Deliver the message normally with a X-DSPAM-Result header'': mails are delivered with a special field in your mail headers (not always visible depending on your mail client and its configuration) ; this is quite handy if you prefer SPAMs arranged in a specific folder * ''Disable DSPAM filtering'': you may switch off filtering at your own risk We strongly recommend using TEFT with daily training for a few weeks then switching to TUM. If you need to go away for a long time, switching to TOE is recommended. Using the quarantine feature is also a safe choice, as the web interface is quite easy to use. === Mail Filtering === With your favourite mail client, you can probably filter your mails in proper folders already. Nevertheless, this can be a annoying operation: * blocking you mail client for a long time if you have to process plenty of mails * downloading each mail information, and sometimes content (depending on your filters), is lenghty too, and cost much bandwidth * syncing filters accross your machines (home desktop, laptop, office machine…) is a pain in the ass * processing only when you're online prevents triggering actions in a timely manner (automatic redirect, vacation messages…), and running a machine 24/7 with a mail client polling new mails every 30s is not a solution We provide a much better way to do this using the [[wikipedia:Sieve_(mail_filtering_language)|SIEVE]] filters. Shortly, SIEVE is a language dedicated to expressing mail filters. Our server is able to process your mails according to these filters as soon as they arrive. You then don't have to care about them anymore, and may use light mail clients or webmails when you're not on your machine with your favourite software. To push your filters on the server, a dedicated protocol exists: : MANAGESIEVE (TCP 4190) on sieve.duckcorp.org Several softwares support managing SIEVE rules: * Icedove/Thunderbird using the SIEVE extension (in xul-ext-sieve Debian package) provides a rules editor * Horde (Ingo) provides an easy to use web interface * Squirrelmail with the Avelsieve extension provides an easy to use web interface * Roundcube with an extension provides an easy to use web interface * sieve-connect provides a CLI to upload/download/activate your rules files (tell us if you know more software supporting this feature) You can read more info about SIEVE here: * supported SIEVE features on our server: http://pigeonhole.dovecot.org/ * http://www.fastmail.fm/docs/sieve/ * http://sieve.info/ === Fetching eMails from an External Mailbox === {{todo}} === Shared/Public Folders === You may need to share mails or messages with friends or people you do stuff with (in a project or association). Depending on your needs, two solutions are possible: * share some of your own private folders, thus called ''shared folders'' * manage a special folder hierarchy, called ''public folders'' (even if they may not be accessible to everyone) Through IMAP, or our webmails internally using IMAP, it is possible to partition the folder hierarchy into ''namespaces''. Traditionally you are using the root namespace for your private folders. Additionnal namespaces can be created and will appear among your own folders or separate, depending on your mail client's choice of representation. To avoid name clashes, we decided to prefix all additionnal namespace names with a '''#'''. Since 2011-05-14, the following extra namespaces are created and reserved: * #Shared, containing all folders other users decided to share with you * #MilkyPond, containing public MP/DC information mailboxes you may subscribe at will Using IMAP, it is possible to setup rights (read only, write allowed…) to your own folders in order to share them with other users, or group of users. Public folders are owned by noone, and must be created by DC administrators ; if you need one, send us a request and we may be able to create it and delegate administration to your care (namespace name is subject to approval). Once created, public folders can be administered like shared folders. Client mail softwares support: * Horde: support namespaces, shared folders configurable via ''Options->Share Folders'' menu but no ACLs for public folders * Icedove/Thunderbird: support namespaces, shared and public folders configurable via folder selection and ''Tools->Imap-ACL'' menu action Most other softwares have namespace support only, so you should be able to use shared/public folders you have rights on but not configure them yourself (tell us if you know more software supporting this feature) == Limitations == === Maximum Mail Size === Mail you send or receive are limited to 10MB. If you need to transmit much bigger data, then a mail transport is not appropriate, you'd better use a file sharing method instead. === Quotas === Even if it would be nice to live without it, we had to establish quotas to force people sort their mails out once in a while and delete useless things instead of leaving an ever-growing mess behind. The default quota is 512MB which is not that big but should match needs of most users. This said, you may ask us for more and there's no reason we would refuse a reasonable demand. == Technical Details == This service is made using: * [http://www.postfix.org/ Postfix] * [http://dovecot.org/ Dovecot] * [http://dspam.sourceforge.net DSPAM] * [http://johannes.sipsolutions.net/Projects/dovecot-antispam dovecot-antispam] * [http://www.horde.org/ Horde] * [http://www.squirrelmail.org/ SquirrelMail] * [http://www.roundcube.net/ RoundCube] 35a1dc74db341abd305111b6b9c170489b83a996 322 320 2012-01-26T19:09:30Z Duck 2 wikitext text/x-wiki {{Template:Service | description = Available services: * multiple email addresses (mailboxes or redirections) based on ''milkypond.org'' (or maybe ''duckcorp.org'') domain(s) or you own domain(s) * roaming accounts to be able to send emails wherever you are | prerequisite = You need to ask an administrator for an account. | account = global | ipv6 = true | security_notes = }} == Access == === Using a Mail Reader === You can retrieve your mails, in case of a real mailbox, using either: * IMAP+TLS (TCP 143) / IMAPS (TCP 993) on imap.duckcorp.org * or POP3+TLS (TCP 110) / POP3S (TCP 995) on pop.duckcorp.org The IMAP protocol is recommended over POP3, as it provides many interesting features. If you want to download all your mails absolutely at home, loosing the ability to read your mail from anywhere on the planet, you can do that with IMAP too (look at your mail client settings). You can use our servers to send mails out too via smtp.duckcorp.org using: * SMTP+TLS (TCP 25) / SMTPS (TCP 465) * and SASL authentication === Using a Web Interface === Several [https://webmail.duckcorp.org/ webmail interfaces] are available. == Mailboxes Features == === Antivirus and Antispam === Mails stored on our server are checked upon arrival for viruses and SPAMs. Mail redirected to a third party mailbox are not, not to mess with the strategy of the the final destination (which could arm learning greatly). Mails being viruses are suppressed automatically upon arrival. Once in a week, an extra antivirus check is done on all hosted mailboxes, to remove viruses not detected at the time it arrived (our antivirus database is updated daily), so you may see such mail disappear from your mailbox, don't fear. SPAMs are more difficult to detect, and it is an error-prone process, so we chose to use a learning software intead of using a global database. On the bright side of things, you would never loose mails and the software should be able to learn what is a SPAM from '''your''' point of view (which has proved to differ slightly between our users), but on the grey side you will have to teach him regulary to avoid errors. When your account is created, it acts like an empty headed body letting everything through, but after a few weeks of teaching it is able to recognise most of your habits and block a lot of annoying SPAM. To teach the system, you can: * use the [https://spamfilter.duckcorp.org/ web interface] to retrain from errors in the ''History'' page * resend SPAM to dc-spam@duckcorp.org and HAM (non-SPAM) to dc-ham@duckcorp.org *: {{warning}} PLEASE TAKE CARE to use the ''resend'' function of your mailer and never use ''forward'', which would result in '''yourself''' being considered as spam or ham You can yourself setup a few parameters in the ''Preferences'' page of the [https://spamfilter.duckcorp.org/ web interface], mostly: * how the system should train: ** TEFT (''On every new message scanned by the filter''): useful to learn very quickly especially on a new mailbox or when you've got tons of spam on your addresses, but you need to train it regulary (daily is better) or it will learn wrong (very quickly too !) ** TOE (''Only when the filter makes a mistake''): slow learning, but if you don't have time for training very often or go on long holidays without internet access this mode will give you a stable behavior ** TUM (''Only with new data or if the filter makes a mistake''): trade-off between the two previous modes, learn quite fast and not too demanding, adapts better to new SPAMs then TOE * filter sensitivity: you can ask the system to be more or less aggressive * message handling: ** ''Quarantine the message'': mails are not delivered to your mailbox but retained by the system and you can only manage them through the [https://spamfilter.duckcorp.org/ web interface] ; if you retrain a quarantined mail as HAM, it will be freed from quarantine and delivered in your mailbox at once ; in this mode, you need to flush your quarantine once in a while ** ''Tag the Subject header with'': mails are delivered with a modified title (which is a tad ugly) ** ''Deliver the message normally with a X-DSPAM-Result header'': mails are delivered with a special field in your mail headers (not always visible depending on your mail client and its configuration) ; this is quite handy if you prefer SPAMs arranged in a specific folder * ''Disable DSPAM filtering'': you may switch off filtering at your own risk We strongly recommend using TEFT with daily training for a few weeks then switching to TUM. If you need to go away for a long time, switching to TOE is recommended. Using the quarantine feature is also a safe choice, as the web interface is quite easy to use. === Mail Filtering === With your favourite mail client, you can probably filter your mails in proper folders already. Nevertheless, this can be a annoying operation: * blocking you mail client for a long time if you have to process plenty of mails * downloading each mail information, and sometimes content (depending on your filters), is lenghty too, and cost much bandwidth * syncing filters accross your machines (home desktop, laptop, office machine…) is a pain in the ass * processing only when you're online prevents triggering actions in a timely manner (automatic redirect, vacation messages…), and running a machine 24/7 with a mail client polling new mails every 30s is not a solution We provide a much better way to do this using the [[wikipedia:Sieve_(mail_filtering_language)|SIEVE]] filters. Shortly, SIEVE is a language dedicated to expressing mail filters. Our server is able to process your mails according to these filters as soon as they arrive. You then don't have to care about them anymore, and may use light mail clients or webmails when you're not on your machine with your favourite software. To push your filters on the server, a dedicated protocol exists: : MANAGESIEVE (TCP 4190) on sieve.duckcorp.org Several softwares support managing SIEVE rules: * Icedove/Thunderbird using the SIEVE extension (in xul-ext-sieve Debian package) provides a rules editor * Horde (Ingo) provides an easy to use web interface * Squirrelmail with the Avelsieve extension provides an easy to use web interface * Roundcube with an extension provides an easy to use web interface * sieve-connect provides a CLI to upload/download/activate your rules files (tell us if you know more software supporting this feature) You can read more info about SIEVE here: * supported SIEVE features on our server: http://pigeonhole.dovecot.org/ * http://www.fastmail.fm/docs/sieve/ * http://sieve.info/ === Fetching eMails from an External Mailbox === {{todo}} === Shared/Public Folders === You may need to share mails or messages with friends or people you do stuff with (in a project or association). Depending on your needs, two solutions are possible: * share some of your own private folders, thus called ''shared folders'' * manage a special folder hierarchy, called ''public folders'' (even if they may not be accessible to everyone) Through IMAP, or our webmails internally using IMAP, it is possible to partition the folder hierarchy into ''namespaces''. Traditionally you are using the root namespace for your private folders. Additionnal namespaces can be created and will appear among your own folders or separate, depending on your mail client's choice of representation. To avoid name clashes, we decided to prefix all additionnal namespace names with a '''#'''. Since 2011-05-14, the following extra namespaces are created and reserved: * #Shared, containing all folders other users decided to share with you * #MilkyPond, containing public MP/DC information mailboxes you may subscribe at will Using IMAP, it is possible to setup rights (read only, write allowed…) to your own folders in order to share them with other users, or group of users. Public folders are owned by noone, and must be created by DC administrators ; if you need one, send us a request and we may be able to create it and delegate administration to your care (namespace name is subject to approval). Once created, public folders can be administered like shared folders. Client mail softwares support: * Horde: support namespaces, shared folders configurable via ''Options->Share Folders'' menu but no ACLs for public folders * Icedove/Thunderbird: support namespaces, shared and public folders configurable via folder selection and ''Tools->Imap-ACL'' menu action Most other softwares have namespace support only, so you should be able to use shared/public folders you have rights on but not configure them yourself (tell us if you know more software supporting this feature) == Limitations == === Maximum Mail Size === Mail you send or receive are limited to 10MB. If you need to transmit much bigger data, then a mail transport is not appropriate, you'd better use a file sharing method instead. === Quotas === Even if it would be nice to live without it, we had to establish quotas to force people sort their mails out once in a while and delete useless things instead of leaving an ever-growing mess behind. The default quota is 512MB which is not that big but should match needs of most users. This said, you may ask us for more and there's no reason we would refuse a reasonable demand. == Technical Details == This service is made using: * [http://www.postfix.org/ Postfix] * [http://dovecot.org/ Dovecot] * [http://dspam.sourceforge.net DSPAM] * [http://johannes.sipsolutions.net/Projects/dovecot-antispam dovecot-antispam] * [http://www.horde.org/ Horde] * [http://www.squirrelmail.org/ SquirrelMail] * [http://www.roundcube.net/ RoundCube] 7094c996bef96e8e69031e51bc393b806bcc2d79 327 322 2012-01-26T21:09:51Z Duck 2 wikitext text/x-wiki {{Template:Service | description = Available services: * multiple email addresses (mailboxes+aliases or redirections) based on the ''milkypond.org'' (or maybe ''duckcorp.org'') domain * roaming accounts to be able to send emails wherever you are If you want email addresses using you own domain(s), see the [[Services/MailHosting|mail hosting service]]. | prerequisite = | account = global-reg | ipv6 = true | security_notes = Access to the mail services are fully secured, and to your data, nevertheless most mail exchange on the Internet are not. Complete security can be achieved using signed and encrypted mail (see [[wikipedia:Pretty_Good_Privacy|OpenPGP]] and [[wikipedia:S/MIME|S/MIME]]) }} == Access == === Using a Mail Reader === You can retrieve your mails, in case of a real mailbox, using either: * IMAP+TLS (TCP 143) / IMAPS (TCP 993) on imap.duckcorp.org * or POP3+TLS (TCP 110) / POP3S (TCP 995) on pop.duckcorp.org The IMAP protocol is recommended over POP3, as it provides many interesting features. If you want to download all your mails absolutely at home, loosing the ability to read your mail from anywhere on the planet, you can do that with IMAP too (look at your mail client settings). You can use our servers to send mails out too via smtp.duckcorp.org using: * SMTP+TLS (TCP 25) / SMTPS (TCP 465) * and SASL authentication === Using a Web Interface === Several [https://webmail.duckcorp.org/ webmail interfaces] are available. == Mailboxes Features == === Antivirus and Antispam === Mails stored on our server are checked upon arrival for viruses and SPAMs. Mail redirected to a third party mailbox are not, not to mess with the strategy of the the final destination (which could arm learning greatly). Mails being viruses are suppressed automatically upon arrival. Once in a week, an extra antivirus check is done on all hosted mailboxes, to remove viruses not detected at the time it arrived (our antivirus database is updated daily), so you may see such mail disappear from your mailbox, don't fear. SPAMs are more difficult to detect, and it is an error-prone process, so we chose to use a learning software intead of using a global database. On the bright side of things, you would never loose mails and the software should be able to learn what is a SPAM from '''your''' point of view (which has proved to differ slightly between our users), but on the grey side you will have to teach him regulary to avoid errors. When your account is created, it acts like an empty headed body letting everything through, but after a few weeks of teaching it is able to recognise most of your habits and block a lot of annoying SPAM. To teach the system, you can: * use the [https://spamfilter.duckcorp.org/ web interface] to retrain from errors in the ''History'' page * resend SPAM to dc-spam@duckcorp.org and HAM (non-SPAM) to dc-ham@duckcorp.org *: {{warning}} PLEASE TAKE CARE to use the ''resend'' function of your mailer and never use ''forward'', which would result in '''yourself''' being considered as spam or ham You can yourself setup a few parameters in the ''Preferences'' page of the [https://spamfilter.duckcorp.org/ web interface], mostly: * how the system should train: ** TEFT (''On every new message scanned by the filter''): useful to learn very quickly especially on a new mailbox or when you've got tons of spam on your addresses, but you need to train it regulary (daily is better) or it will learn wrong (very quickly too !) ** TOE (''Only when the filter makes a mistake''): slow learning, but if you don't have time for training very often or go on long holidays without internet access this mode will give you a stable behavior ** TUM (''Only with new data or if the filter makes a mistake''): trade-off between the two previous modes, learn quite fast and not too demanding, adapts better to new SPAMs then TOE * filter sensitivity: you can ask the system to be more or less aggressive * message handling: ** ''Quarantine the message'': mails are not delivered to your mailbox but retained by the system and you can only manage them through the [https://spamfilter.duckcorp.org/ web interface] ; if you retrain a quarantined mail as HAM, it will be freed from quarantine and delivered in your mailbox at once ; in this mode, you need to flush your quarantine once in a while ** ''Tag the Subject header with'': mails are delivered with a modified title (which is a tad ugly) ** ''Deliver the message normally with a X-DSPAM-Result header'': mails are delivered with a special field in your mail headers (not always visible depending on your mail client and its configuration) ; this is quite handy if you prefer SPAMs arranged in a specific folder * ''Disable DSPAM filtering'': you may switch off filtering at your own risk We strongly recommend using TEFT with daily training for a few weeks then switching to TUM. If you need to go away for a long time, switching to TOE is recommended. Using the quarantine feature is also a safe choice, as the web interface is quite easy to use. === Mail Filtering === With your favourite mail client, you can probably filter your mails in proper folders already. Nevertheless, this can be a annoying operation: * blocking you mail client for a long time if you have to process plenty of mails * downloading each mail information, and sometimes content (depending on your filters), is lenghty too, and cost much bandwidth * syncing filters accross your machines (home desktop, laptop, office machine…) is a pain in the ass * processing only when you're online prevents triggering actions in a timely manner (automatic redirect, vacation messages…), and running a machine 24/7 with a mail client polling new mails every 30s is not a solution We provide a much better way to do this using the [[wikipedia:Sieve_(mail_filtering_language)|SIEVE]] filters. Shortly, SIEVE is a language dedicated to expressing mail filters. Our server is able to process your mails according to these filters as soon as they arrive. You then don't have to care about them anymore, and may use light mail clients or webmails when you're not on your machine with your favourite software. To push your filters on the server, a dedicated protocol exists: : MANAGESIEVE (TCP 4190) on sieve.duckcorp.org Several softwares support managing SIEVE rules: * Icedove/Thunderbird using the SIEVE extension (in xul-ext-sieve Debian package) provides a rules editor * Horde (Ingo) provides an easy to use web interface * Squirrelmail with the Avelsieve extension provides an easy to use web interface * Roundcube with an extension provides an easy to use web interface * sieve-connect provides a CLI to upload/download/activate your rules files (tell us if you know more software supporting this feature) You can read more info about SIEVE here: * supported SIEVE features on our server: http://pigeonhole.dovecot.org/ * http://www.fastmail.fm/docs/sieve/ * http://sieve.info/ === Fetching eMails from an External Mailbox === {{todo}} === Shared/Public Folders === You may need to share mails or messages with friends or people you do stuff with (in a project or association). Depending on your needs, two solutions are possible: * share some of your own private folders, thus called ''shared folders'' * manage a special folder hierarchy, called ''public folders'' (even if they may not be accessible to everyone) Through IMAP, or our webmails internally using IMAP, it is possible to partition the folder hierarchy into ''namespaces''. Traditionally you are using the root namespace for your private folders. Additionnal namespaces can be created and will appear among your own folders or separate, depending on your mail client's choice of representation. To avoid name clashes, we decided to prefix all additionnal namespace names with a '''#'''. Since 2011-05-14, the following extra namespaces are created and reserved: * #Shared, containing all folders other users decided to share with you * #MilkyPond, containing public MP/DC information mailboxes you may subscribe at will Using IMAP, it is possible to setup rights (read only, write allowed…) to your own folders in order to share them with other users, or group of users. Public folders are owned by noone, and must be created by DC administrators ; if you need one, send us a request and we may be able to create it and delegate administration to your care (namespace name is subject to approval). Once created, public folders can be administered like shared folders. Client mail softwares support: * Horde: support namespaces, shared folders configurable via ''Options->Share Folders'' menu but no ACLs for public folders * Icedove/Thunderbird: support namespaces, shared and public folders configurable via folder selection and ''Tools->Imap-ACL'' menu action Most other softwares have namespace support only, so you should be able to use shared/public folders you have rights on but not configure them yourself (tell us if you know more software supporting this feature) == Limitations == === Maximum Mail Size === Mail you send or receive are limited to 10MB. If you need to transmit much bigger data, then a mail transport is not appropriate, you'd better use a file sharing method instead. === Quotas === Even if it would be nice to live without it, we had to establish quotas to force people sort their mails out once in a while and delete useless things instead of leaving an ever-growing mess behind. The default quota is 512MB which is not that big but should match needs of most users. This said, you may ask us for more and there's no reason we would refuse a reasonable demand. == Technical Details == This service is made using: * [http://www.postfix.org/ Postfix] * [http://dovecot.org/ Dovecot] * [http://dspam.sourceforge.net DSPAM] * [http://johannes.sipsolutions.net/Projects/dovecot-antispam dovecot-antispam] * [http://www.horde.org/ Horde] * [http://www.squirrelmail.org/ SquirrelMail] * [http://www.roundcube.net/ RoundCube] c523874d08e6b36bc13e95a470695705259e4051 352 327 2012-01-30T18:18:15Z Duck 2 /* Technical Details */ wikitext text/x-wiki {{Template:Service | description = Available services: * multiple email addresses (mailboxes+aliases or redirections) based on the ''milkypond.org'' (or maybe ''duckcorp.org'') domain * roaming accounts to be able to send emails wherever you are If you want email addresses using you own domain(s), see the [[Services/MailHosting|mail hosting service]]. | prerequisite = | account = global-reg | ipv6 = true | security_notes = Access to the mail services are fully secured, and to your data, nevertheless most mail exchange on the Internet are not. Complete security can be achieved using signed and encrypted mail (see [[wikipedia:Pretty_Good_Privacy|OpenPGP]] and [[wikipedia:S/MIME|S/MIME]]) }} == Access == === Using a Mail Reader === You can retrieve your mails, in case of a real mailbox, using either: * IMAP+TLS (TCP 143) / IMAPS (TCP 993) on imap.duckcorp.org * or POP3+TLS (TCP 110) / POP3S (TCP 995) on pop.duckcorp.org The IMAP protocol is recommended over POP3, as it provides many interesting features. If you want to download all your mails absolutely at home, loosing the ability to read your mail from anywhere on the planet, you can do that with IMAP too (look at your mail client settings). You can use our servers to send mails out too via smtp.duckcorp.org using: * SMTP+TLS (TCP 25) / SMTPS (TCP 465) * and SASL authentication === Using a Web Interface === Several [https://webmail.duckcorp.org/ webmail interfaces] are available. == Mailboxes Features == === Antivirus and Antispam === Mails stored on our server are checked upon arrival for viruses and SPAMs. Mail redirected to a third party mailbox are not, not to mess with the strategy of the the final destination (which could arm learning greatly). Mails being viruses are suppressed automatically upon arrival. Once in a week, an extra antivirus check is done on all hosted mailboxes, to remove viruses not detected at the time it arrived (our antivirus database is updated daily), so you may see such mail disappear from your mailbox, don't fear. SPAMs are more difficult to detect, and it is an error-prone process, so we chose to use a learning software intead of using a global database. On the bright side of things, you would never loose mails and the software should be able to learn what is a SPAM from '''your''' point of view (which has proved to differ slightly between our users), but on the grey side you will have to teach him regulary to avoid errors. When your account is created, it acts like an empty headed body letting everything through, but after a few weeks of teaching it is able to recognise most of your habits and block a lot of annoying SPAM. To teach the system, you can: * use the [https://spamfilter.duckcorp.org/ web interface] to retrain from errors in the ''History'' page * resend SPAM to dc-spam@duckcorp.org and HAM (non-SPAM) to dc-ham@duckcorp.org *: {{warning}} PLEASE TAKE CARE to use the ''resend'' function of your mailer and never use ''forward'', which would result in '''yourself''' being considered as spam or ham You can yourself setup a few parameters in the ''Preferences'' page of the [https://spamfilter.duckcorp.org/ web interface], mostly: * how the system should train: ** TEFT (''On every new message scanned by the filter''): useful to learn very quickly especially on a new mailbox or when you've got tons of spam on your addresses, but you need to train it regulary (daily is better) or it will learn wrong (very quickly too !) ** TOE (''Only when the filter makes a mistake''): slow learning, but if you don't have time for training very often or go on long holidays without internet access this mode will give you a stable behavior ** TUM (''Only with new data or if the filter makes a mistake''): trade-off between the two previous modes, learn quite fast and not too demanding, adapts better to new SPAMs then TOE * filter sensitivity: you can ask the system to be more or less aggressive * message handling: ** ''Quarantine the message'': mails are not delivered to your mailbox but retained by the system and you can only manage them through the [https://spamfilter.duckcorp.org/ web interface] ; if you retrain a quarantined mail as HAM, it will be freed from quarantine and delivered in your mailbox at once ; in this mode, you need to flush your quarantine once in a while ** ''Tag the Subject header with'': mails are delivered with a modified title (which is a tad ugly) ** ''Deliver the message normally with a X-DSPAM-Result header'': mails are delivered with a special field in your mail headers (not always visible depending on your mail client and its configuration) ; this is quite handy if you prefer SPAMs arranged in a specific folder * ''Disable DSPAM filtering'': you may switch off filtering at your own risk We strongly recommend using TEFT with daily training for a few weeks then switching to TUM. If you need to go away for a long time, switching to TOE is recommended. Using the quarantine feature is also a safe choice, as the web interface is quite easy to use. === Mail Filtering === With your favourite mail client, you can probably filter your mails in proper folders already. Nevertheless, this can be a annoying operation: * blocking you mail client for a long time if you have to process plenty of mails * downloading each mail information, and sometimes content (depending on your filters), is lenghty too, and cost much bandwidth * syncing filters accross your machines (home desktop, laptop, office machine…) is a pain in the ass * processing only when you're online prevents triggering actions in a timely manner (automatic redirect, vacation messages…), and running a machine 24/7 with a mail client polling new mails every 30s is not a solution We provide a much better way to do this using the [[wikipedia:Sieve_(mail_filtering_language)|SIEVE]] filters. Shortly, SIEVE is a language dedicated to expressing mail filters. Our server is able to process your mails according to these filters as soon as they arrive. You then don't have to care about them anymore, and may use light mail clients or webmails when you're not on your machine with your favourite software. To push your filters on the server, a dedicated protocol exists: : MANAGESIEVE (TCP 4190) on sieve.duckcorp.org Several softwares support managing SIEVE rules: * Icedove/Thunderbird using the SIEVE extension (in xul-ext-sieve Debian package) provides a rules editor * Horde (Ingo) provides an easy to use web interface * Squirrelmail with the Avelsieve extension provides an easy to use web interface * Roundcube with an extension provides an easy to use web interface * sieve-connect provides a CLI to upload/download/activate your rules files (tell us if you know more software supporting this feature) You can read more info about SIEVE here: * supported SIEVE features on our server: http://pigeonhole.dovecot.org/ * http://www.fastmail.fm/docs/sieve/ * http://sieve.info/ === Fetching eMails from an External Mailbox === {{todo}} === Shared/Public Folders === You may need to share mails or messages with friends or people you do stuff with (in a project or association). Depending on your needs, two solutions are possible: * share some of your own private folders, thus called ''shared folders'' * manage a special folder hierarchy, called ''public folders'' (even if they may not be accessible to everyone) Through IMAP, or our webmails internally using IMAP, it is possible to partition the folder hierarchy into ''namespaces''. Traditionally you are using the root namespace for your private folders. Additionnal namespaces can be created and will appear among your own folders or separate, depending on your mail client's choice of representation. To avoid name clashes, we decided to prefix all additionnal namespace names with a '''#'''. Since 2011-05-14, the following extra namespaces are created and reserved: * #Shared, containing all folders other users decided to share with you * #MilkyPond, containing public MP/DC information mailboxes you may subscribe at will Using IMAP, it is possible to setup rights (read only, write allowed…) to your own folders in order to share them with other users, or group of users. Public folders are owned by noone, and must be created by DC administrators ; if you need one, send us a request and we may be able to create it and delegate administration to your care (namespace name is subject to approval). Once created, public folders can be administered like shared folders. Client mail softwares support: * Horde: support namespaces, shared folders configurable via ''Options->Share Folders'' menu but no ACLs for public folders * Icedove/Thunderbird: support namespaces, shared and public folders configurable via folder selection and ''Tools->Imap-ACL'' menu action Most other softwares have namespace support only, so you should be able to use shared/public folders you have rights on but not configure them yourself (tell us if you know more software supporting this feature) == Limitations == === Maximum Mail Size === Mail you send or receive are limited to 10MB. If you need to transmit much bigger data, then a mail transport is not appropriate, you'd better use a file sharing method instead. === Quotas === Even if it would be nice to live without it, we had to establish quotas to force people sort their mails out once in a while and delete useless things instead of leaving an ever-growing mess behind. The default quota is 512MB which is not that big but should match needs of most users. This said, you may ask us for more and there's no reason we would refuse a reasonable demand. == Technical Details == This service is made using: * [http://www.postfix.org/ Postfix] * [http://dovecot.org/ Dovecot] * [http://dspam.sourceforge.net DSPAM] * [http://johannes.sipsolutions.net/Projects/dovecot-antispam dovecot-antispam] * [https://projects.duckcorp.org/projects/spoolinger Spoolinger] * [http://www.horde.org/ Horde] * [http://www.squirrelmail.org/ SquirrelMail] * [http://www.roundcube.net/ RoundCube] 36d3f91bed78e6d424c5522e70dbcd76f68cd061 353 352 2012-01-30T18:18:41Z Duck 2 /* Maximum Mail Size */ wikitext text/x-wiki {{Template:Service | description = Available services: * multiple email addresses (mailboxes+aliases or redirections) based on the ''milkypond.org'' (or maybe ''duckcorp.org'') domain * roaming accounts to be able to send emails wherever you are If you want email addresses using you own domain(s), see the [[Services/MailHosting|mail hosting service]]. | prerequisite = | account = global-reg | ipv6 = true | security_notes = Access to the mail services are fully secured, and to your data, nevertheless most mail exchange on the Internet are not. Complete security can be achieved using signed and encrypted mail (see [[wikipedia:Pretty_Good_Privacy|OpenPGP]] and [[wikipedia:S/MIME|S/MIME]]) }} == Access == === Using a Mail Reader === You can retrieve your mails, in case of a real mailbox, using either: * IMAP+TLS (TCP 143) / IMAPS (TCP 993) on imap.duckcorp.org * or POP3+TLS (TCP 110) / POP3S (TCP 995) on pop.duckcorp.org The IMAP protocol is recommended over POP3, as it provides many interesting features. If you want to download all your mails absolutely at home, loosing the ability to read your mail from anywhere on the planet, you can do that with IMAP too (look at your mail client settings). You can use our servers to send mails out too via smtp.duckcorp.org using: * SMTP+TLS (TCP 25) / SMTPS (TCP 465) * and SASL authentication === Using a Web Interface === Several [https://webmail.duckcorp.org/ webmail interfaces] are available. == Mailboxes Features == === Antivirus and Antispam === Mails stored on our server are checked upon arrival for viruses and SPAMs. Mail redirected to a third party mailbox are not, not to mess with the strategy of the the final destination (which could arm learning greatly). Mails being viruses are suppressed automatically upon arrival. Once in a week, an extra antivirus check is done on all hosted mailboxes, to remove viruses not detected at the time it arrived (our antivirus database is updated daily), so you may see such mail disappear from your mailbox, don't fear. SPAMs are more difficult to detect, and it is an error-prone process, so we chose to use a learning software intead of using a global database. On the bright side of things, you would never loose mails and the software should be able to learn what is a SPAM from '''your''' point of view (which has proved to differ slightly between our users), but on the grey side you will have to teach him regulary to avoid errors. When your account is created, it acts like an empty headed body letting everything through, but after a few weeks of teaching it is able to recognise most of your habits and block a lot of annoying SPAM. To teach the system, you can: * use the [https://spamfilter.duckcorp.org/ web interface] to retrain from errors in the ''History'' page * resend SPAM to dc-spam@duckcorp.org and HAM (non-SPAM) to dc-ham@duckcorp.org *: {{warning}} PLEASE TAKE CARE to use the ''resend'' function of your mailer and never use ''forward'', which would result in '''yourself''' being considered as spam or ham You can yourself setup a few parameters in the ''Preferences'' page of the [https://spamfilter.duckcorp.org/ web interface], mostly: * how the system should train: ** TEFT (''On every new message scanned by the filter''): useful to learn very quickly especially on a new mailbox or when you've got tons of spam on your addresses, but you need to train it regulary (daily is better) or it will learn wrong (very quickly too !) ** TOE (''Only when the filter makes a mistake''): slow learning, but if you don't have time for training very often or go on long holidays without internet access this mode will give you a stable behavior ** TUM (''Only with new data or if the filter makes a mistake''): trade-off between the two previous modes, learn quite fast and not too demanding, adapts better to new SPAMs then TOE * filter sensitivity: you can ask the system to be more or less aggressive * message handling: ** ''Quarantine the message'': mails are not delivered to your mailbox but retained by the system and you can only manage them through the [https://spamfilter.duckcorp.org/ web interface] ; if you retrain a quarantined mail as HAM, it will be freed from quarantine and delivered in your mailbox at once ; in this mode, you need to flush your quarantine once in a while ** ''Tag the Subject header with'': mails are delivered with a modified title (which is a tad ugly) ** ''Deliver the message normally with a X-DSPAM-Result header'': mails are delivered with a special field in your mail headers (not always visible depending on your mail client and its configuration) ; this is quite handy if you prefer SPAMs arranged in a specific folder * ''Disable DSPAM filtering'': you may switch off filtering at your own risk We strongly recommend using TEFT with daily training for a few weeks then switching to TUM. If you need to go away for a long time, switching to TOE is recommended. Using the quarantine feature is also a safe choice, as the web interface is quite easy to use. === Mail Filtering === With your favourite mail client, you can probably filter your mails in proper folders already. Nevertheless, this can be a annoying operation: * blocking you mail client for a long time if you have to process plenty of mails * downloading each mail information, and sometimes content (depending on your filters), is lenghty too, and cost much bandwidth * syncing filters accross your machines (home desktop, laptop, office machine…) is a pain in the ass * processing only when you're online prevents triggering actions in a timely manner (automatic redirect, vacation messages…), and running a machine 24/7 with a mail client polling new mails every 30s is not a solution We provide a much better way to do this using the [[wikipedia:Sieve_(mail_filtering_language)|SIEVE]] filters. Shortly, SIEVE is a language dedicated to expressing mail filters. Our server is able to process your mails according to these filters as soon as they arrive. You then don't have to care about them anymore, and may use light mail clients or webmails when you're not on your machine with your favourite software. To push your filters on the server, a dedicated protocol exists: : MANAGESIEVE (TCP 4190) on sieve.duckcorp.org Several softwares support managing SIEVE rules: * Icedove/Thunderbird using the SIEVE extension (in xul-ext-sieve Debian package) provides a rules editor * Horde (Ingo) provides an easy to use web interface * Squirrelmail with the Avelsieve extension provides an easy to use web interface * Roundcube with an extension provides an easy to use web interface * sieve-connect provides a CLI to upload/download/activate your rules files (tell us if you know more software supporting this feature) You can read more info about SIEVE here: * supported SIEVE features on our server: http://pigeonhole.dovecot.org/ * http://www.fastmail.fm/docs/sieve/ * http://sieve.info/ === Fetching eMails from an External Mailbox === {{todo}} === Shared/Public Folders === You may need to share mails or messages with friends or people you do stuff with (in a project or association). Depending on your needs, two solutions are possible: * share some of your own private folders, thus called ''shared folders'' * manage a special folder hierarchy, called ''public folders'' (even if they may not be accessible to everyone) Through IMAP, or our webmails internally using IMAP, it is possible to partition the folder hierarchy into ''namespaces''. Traditionally you are using the root namespace for your private folders. Additionnal namespaces can be created and will appear among your own folders or separate, depending on your mail client's choice of representation. To avoid name clashes, we decided to prefix all additionnal namespace names with a '''#'''. Since 2011-05-14, the following extra namespaces are created and reserved: * #Shared, containing all folders other users decided to share with you * #MilkyPond, containing public MP/DC information mailboxes you may subscribe at will Using IMAP, it is possible to setup rights (read only, write allowed…) to your own folders in order to share them with other users, or group of users. Public folders are owned by noone, and must be created by DC administrators ; if you need one, send us a request and we may be able to create it and delegate administration to your care (namespace name is subject to approval). Once created, public folders can be administered like shared folders. Client mail softwares support: * Horde: support namespaces, shared folders configurable via ''Options->Share Folders'' menu but no ACLs for public folders * Icedove/Thunderbird: support namespaces, shared and public folders configurable via folder selection and ''Tools->Imap-ACL'' menu action Most other softwares have namespace support only, so you should be able to use shared/public folders you have rights on but not configure them yourself (tell us if you know more software supporting this feature) == Limitations == === Maximum Mail Size === Mail you send or receive are limited to '''10MB'''. If you need to transmit much bigger data, then a mail transport is not appropriate, you'd better use a file sharing method instead. === Quotas === Even if it would be nice to live without it, we had to establish quotas to force people sort their mails out once in a while and delete useless things instead of leaving an ever-growing mess behind. The default quota is 512MB which is not that big but should match needs of most users. This said, you may ask us for more and there's no reason we would refuse a reasonable demand. == Technical Details == This service is made using: * [http://www.postfix.org/ Postfix] * [http://dovecot.org/ Dovecot] * [http://dspam.sourceforge.net DSPAM] * [http://johannes.sipsolutions.net/Projects/dovecot-antispam dovecot-antispam] * [https://projects.duckcorp.org/projects/spoolinger Spoolinger] * [http://www.horde.org/ Horde] * [http://www.squirrelmail.org/ SquirrelMail] * [http://www.roundcube.net/ RoundCube] bc04e818a5bbe7bea7bf2b2fe223ff41f86cee49 354 353 2012-01-30T18:18:58Z Duck 2 /* Quotas */ wikitext text/x-wiki {{Template:Service | description = Available services: * multiple email addresses (mailboxes+aliases or redirections) based on the ''milkypond.org'' (or maybe ''duckcorp.org'') domain * roaming accounts to be able to send emails wherever you are If you want email addresses using you own domain(s), see the [[Services/MailHosting|mail hosting service]]. | prerequisite = | account = global-reg | ipv6 = true | security_notes = Access to the mail services are fully secured, and to your data, nevertheless most mail exchange on the Internet are not. Complete security can be achieved using signed and encrypted mail (see [[wikipedia:Pretty_Good_Privacy|OpenPGP]] and [[wikipedia:S/MIME|S/MIME]]) }} == Access == === Using a Mail Reader === You can retrieve your mails, in case of a real mailbox, using either: * IMAP+TLS (TCP 143) / IMAPS (TCP 993) on imap.duckcorp.org * or POP3+TLS (TCP 110) / POP3S (TCP 995) on pop.duckcorp.org The IMAP protocol is recommended over POP3, as it provides many interesting features. If you want to download all your mails absolutely at home, loosing the ability to read your mail from anywhere on the planet, you can do that with IMAP too (look at your mail client settings). You can use our servers to send mails out too via smtp.duckcorp.org using: * SMTP+TLS (TCP 25) / SMTPS (TCP 465) * and SASL authentication === Using a Web Interface === Several [https://webmail.duckcorp.org/ webmail interfaces] are available. == Mailboxes Features == === Antivirus and Antispam === Mails stored on our server are checked upon arrival for viruses and SPAMs. Mail redirected to a third party mailbox are not, not to mess with the strategy of the the final destination (which could arm learning greatly). Mails being viruses are suppressed automatically upon arrival. Once in a week, an extra antivirus check is done on all hosted mailboxes, to remove viruses not detected at the time it arrived (our antivirus database is updated daily), so you may see such mail disappear from your mailbox, don't fear. SPAMs are more difficult to detect, and it is an error-prone process, so we chose to use a learning software intead of using a global database. On the bright side of things, you would never loose mails and the software should be able to learn what is a SPAM from '''your''' point of view (which has proved to differ slightly between our users), but on the grey side you will have to teach him regulary to avoid errors. When your account is created, it acts like an empty headed body letting everything through, but after a few weeks of teaching it is able to recognise most of your habits and block a lot of annoying SPAM. To teach the system, you can: * use the [https://spamfilter.duckcorp.org/ web interface] to retrain from errors in the ''History'' page * resend SPAM to dc-spam@duckcorp.org and HAM (non-SPAM) to dc-ham@duckcorp.org *: {{warning}} PLEASE TAKE CARE to use the ''resend'' function of your mailer and never use ''forward'', which would result in '''yourself''' being considered as spam or ham You can yourself setup a few parameters in the ''Preferences'' page of the [https://spamfilter.duckcorp.org/ web interface], mostly: * how the system should train: ** TEFT (''On every new message scanned by the filter''): useful to learn very quickly especially on a new mailbox or when you've got tons of spam on your addresses, but you need to train it regulary (daily is better) or it will learn wrong (very quickly too !) ** TOE (''Only when the filter makes a mistake''): slow learning, but if you don't have time for training very often or go on long holidays without internet access this mode will give you a stable behavior ** TUM (''Only with new data or if the filter makes a mistake''): trade-off between the two previous modes, learn quite fast and not too demanding, adapts better to new SPAMs then TOE * filter sensitivity: you can ask the system to be more or less aggressive * message handling: ** ''Quarantine the message'': mails are not delivered to your mailbox but retained by the system and you can only manage them through the [https://spamfilter.duckcorp.org/ web interface] ; if you retrain a quarantined mail as HAM, it will be freed from quarantine and delivered in your mailbox at once ; in this mode, you need to flush your quarantine once in a while ** ''Tag the Subject header with'': mails are delivered with a modified title (which is a tad ugly) ** ''Deliver the message normally with a X-DSPAM-Result header'': mails are delivered with a special field in your mail headers (not always visible depending on your mail client and its configuration) ; this is quite handy if you prefer SPAMs arranged in a specific folder * ''Disable DSPAM filtering'': you may switch off filtering at your own risk We strongly recommend using TEFT with daily training for a few weeks then switching to TUM. If you need to go away for a long time, switching to TOE is recommended. Using the quarantine feature is also a safe choice, as the web interface is quite easy to use. === Mail Filtering === With your favourite mail client, you can probably filter your mails in proper folders already. Nevertheless, this can be a annoying operation: * blocking you mail client for a long time if you have to process plenty of mails * downloading each mail information, and sometimes content (depending on your filters), is lenghty too, and cost much bandwidth * syncing filters accross your machines (home desktop, laptop, office machine…) is a pain in the ass * processing only when you're online prevents triggering actions in a timely manner (automatic redirect, vacation messages…), and running a machine 24/7 with a mail client polling new mails every 30s is not a solution We provide a much better way to do this using the [[wikipedia:Sieve_(mail_filtering_language)|SIEVE]] filters. Shortly, SIEVE is a language dedicated to expressing mail filters. Our server is able to process your mails according to these filters as soon as they arrive. You then don't have to care about them anymore, and may use light mail clients or webmails when you're not on your machine with your favourite software. To push your filters on the server, a dedicated protocol exists: : MANAGESIEVE (TCP 4190) on sieve.duckcorp.org Several softwares support managing SIEVE rules: * Icedove/Thunderbird using the SIEVE extension (in xul-ext-sieve Debian package) provides a rules editor * Horde (Ingo) provides an easy to use web interface * Squirrelmail with the Avelsieve extension provides an easy to use web interface * Roundcube with an extension provides an easy to use web interface * sieve-connect provides a CLI to upload/download/activate your rules files (tell us if you know more software supporting this feature) You can read more info about SIEVE here: * supported SIEVE features on our server: http://pigeonhole.dovecot.org/ * http://www.fastmail.fm/docs/sieve/ * http://sieve.info/ === Fetching eMails from an External Mailbox === {{todo}} === Shared/Public Folders === You may need to share mails or messages with friends or people you do stuff with (in a project or association). Depending on your needs, two solutions are possible: * share some of your own private folders, thus called ''shared folders'' * manage a special folder hierarchy, called ''public folders'' (even if they may not be accessible to everyone) Through IMAP, or our webmails internally using IMAP, it is possible to partition the folder hierarchy into ''namespaces''. Traditionally you are using the root namespace for your private folders. Additionnal namespaces can be created and will appear among your own folders or separate, depending on your mail client's choice of representation. To avoid name clashes, we decided to prefix all additionnal namespace names with a '''#'''. Since 2011-05-14, the following extra namespaces are created and reserved: * #Shared, containing all folders other users decided to share with you * #MilkyPond, containing public MP/DC information mailboxes you may subscribe at will Using IMAP, it is possible to setup rights (read only, write allowed…) to your own folders in order to share them with other users, or group of users. Public folders are owned by noone, and must be created by DC administrators ; if you need one, send us a request and we may be able to create it and delegate administration to your care (namespace name is subject to approval). Once created, public folders can be administered like shared folders. Client mail softwares support: * Horde: support namespaces, shared folders configurable via ''Options->Share Folders'' menu but no ACLs for public folders * Icedove/Thunderbird: support namespaces, shared and public folders configurable via folder selection and ''Tools->Imap-ACL'' menu action Most other softwares have namespace support only, so you should be able to use shared/public folders you have rights on but not configure them yourself (tell us if you know more software supporting this feature) == Limitations == === Maximum Mail Size === Mail you send or receive are limited to '''10MB'''. If you need to transmit much bigger data, then a mail transport is not appropriate, you'd better use a file sharing method instead. === Quotas === Even if it would be nice to live without it, we had to establish quotas to force people sort their mails out once in a while and delete useless things instead of leaving an ever-growing mess behind. The default quota is '''512MB''' which is not that big but should match needs of most users. This said, you may ask us for more and there's no reason we would refuse a reasonable demand. == Technical Details == This service is made using: * [http://www.postfix.org/ Postfix] * [http://dovecot.org/ Dovecot] * [http://dspam.sourceforge.net DSPAM] * [http://johannes.sipsolutions.net/Projects/dovecot-antispam dovecot-antispam] * [https://projects.duckcorp.org/projects/spoolinger Spoolinger] * [http://www.horde.org/ Horde] * [http://www.squirrelmail.org/ SquirrelMail] * [http://www.roundcube.net/ RoundCube] 2c1d28aaf859d5b796be6292eeb7894b625a7da1 355 354 2012-01-30T18:43:51Z Duck 2 /* Antivirus and Antispam */ wikitext text/x-wiki {{Template:Service | description = Available services: * multiple email addresses (mailboxes+aliases or redirections) based on the ''milkypond.org'' (or maybe ''duckcorp.org'') domain * roaming accounts to be able to send emails wherever you are If you want email addresses using you own domain(s), see the [[Services/MailHosting|mail hosting service]]. | prerequisite = | account = global-reg | ipv6 = true | security_notes = Access to the mail services are fully secured, and to your data, nevertheless most mail exchange on the Internet are not. Complete security can be achieved using signed and encrypted mail (see [[wikipedia:Pretty_Good_Privacy|OpenPGP]] and [[wikipedia:S/MIME|S/MIME]]) }} == Access == === Using a Mail Reader === You can retrieve your mails, in case of a real mailbox, using either: * IMAP+TLS (TCP 143) / IMAPS (TCP 993) on imap.duckcorp.org * or POP3+TLS (TCP 110) / POP3S (TCP 995) on pop.duckcorp.org The IMAP protocol is recommended over POP3, as it provides many interesting features. If you want to download all your mails absolutely at home, loosing the ability to read your mail from anywhere on the planet, you can do that with IMAP too (look at your mail client settings). You can use our servers to send mails out too via smtp.duckcorp.org using: * SMTP+TLS (TCP 25) / SMTPS (TCP 465) * and SASL authentication === Using a Web Interface === Several [https://webmail.duckcorp.org/ webmail interfaces] are available. == Mailboxes Features == === Antivirus and Antispam === Mails stored on our server are checked upon arrival for viruses and SPAMs. Mail redirected to a third party mailbox are not, not to mess with the strategy of the the final destination (which could arm learning greatly). Mails being viruses are suppressed automatically upon arrival. Once in a week, an extra antivirus check is done on all hosted mailboxes, to remove viruses not detected at the time it arrived (our antivirus database is updated daily), so you may see such mail disappear from your mailbox, don't fear. SPAMs are more difficult to detect, and it is an error-prone process, so we chose to use a learning software instead of using a global database. On the bright side of things, you would never loose mails and the software should be able to learn what is a SPAM from '''your''' point of view (which has proved to differ slightly between our users), but on the grey side you will have to teach him regularly to avoid errors. When your account is created, it acts like an empty headed body letting everything through, but after a few weeks of teaching it is able to recognize most of your habits and block a lot of annoying SPAM. Teaching the system is called ''retraining''. ==== Retraining using the Special ''Junk'' Folder ==== ==== Retraining via Web Interface ==== Use the [https://spamfilter.duckcorp.org/ web interface] to retrain from errors in the ''History'' page. ==== Retraining via Mail ==== Resend SPAMs to ''dc-spam@duckcorp.org'' and HAM (non-SPAM) to ''dc-ham@duckcorp.org''. {{warning}} PLEASE TAKE CARE to use the ''resend'' function of your mailer and never use ''forward'', which would result in '''yourself''' being considered as SPAN or HAM. ==== User Settings ==== You can yourself setup a few parameters in the ''Preferences'' page of the [https://spamfilter.duckcorp.org/ web interface], mostly: * how the system should train: ** TEFT (''On every new message scanned by the filter''): useful to learn very quickly especially on a new mailbox or when you've got tons of spam on your addresses, but you need to train it regulary (daily is better) or it will learn wrong (very quickly too !) ** TOE (''Only when the filter makes a mistake''): slow learning, but if you don't have time for training very often or go on long holidays without internet access this mode will give you a stable behavior ** TUM (''Only with new data or if the filter makes a mistake''): trade-off between the two previous modes, learn quite fast and not too demanding, adapts better to new SPAMs then TOE * filter sensitivity: you can ask the system to be more or less aggressive * message handling: ** ''Quarantine the message'': mails are not delivered to your mailbox but retained by the system and you can only manage them through the [https://spamfilter.duckcorp.org/ web interface] ; if you retrain a quarantined mail as HAM, it will be freed from quarantine and delivered in your mailbox at once ; in this mode, you need to flush your quarantine once in a while ** ''Tag the Subject header with'': mails are delivered with a modified title (which is a tad ugly) ** ''Deliver the message normally with a X-DSPAM-Result header'': mails are delivered with a special field in your mail headers (not always visible depending on your mail client and its configuration) ; this is quite handy if you prefer SPAMs arranged in a specific folder * ''Disable DSPAM filtering'': you may switch off filtering at your own risk We strongly recommend using TEFT with daily training for a few weeks then switching to TUM. If you need to go away for a long time, switching to TOE is recommended. Using the quarantine feature is also a safe choice, as the web interface is quite easy to use. === Mail Filtering === With your favourite mail client, you can probably filter your mails in proper folders already. Nevertheless, this can be a annoying operation: * blocking you mail client for a long time if you have to process plenty of mails * downloading each mail information, and sometimes content (depending on your filters), is lenghty too, and cost much bandwidth * syncing filters accross your machines (home desktop, laptop, office machine…) is a pain in the ass * processing only when you're online prevents triggering actions in a timely manner (automatic redirect, vacation messages…), and running a machine 24/7 with a mail client polling new mails every 30s is not a solution We provide a much better way to do this using the [[wikipedia:Sieve_(mail_filtering_language)|SIEVE]] filters. Shortly, SIEVE is a language dedicated to expressing mail filters. Our server is able to process your mails according to these filters as soon as they arrive. You then don't have to care about them anymore, and may use light mail clients or webmails when you're not on your machine with your favourite software. To push your filters on the server, a dedicated protocol exists: : MANAGESIEVE (TCP 4190) on sieve.duckcorp.org Several softwares support managing SIEVE rules: * Icedove/Thunderbird using the SIEVE extension (in xul-ext-sieve Debian package) provides a rules editor * Horde (Ingo) provides an easy to use web interface * Squirrelmail with the Avelsieve extension provides an easy to use web interface * Roundcube with an extension provides an easy to use web interface * sieve-connect provides a CLI to upload/download/activate your rules files (tell us if you know more software supporting this feature) You can read more info about SIEVE here: * supported SIEVE features on our server: http://pigeonhole.dovecot.org/ * http://www.fastmail.fm/docs/sieve/ * http://sieve.info/ === Fetching eMails from an External Mailbox === {{todo}} === Shared/Public Folders === You may need to share mails or messages with friends or people you do stuff with (in a project or association). Depending on your needs, two solutions are possible: * share some of your own private folders, thus called ''shared folders'' * manage a special folder hierarchy, called ''public folders'' (even if they may not be accessible to everyone) Through IMAP, or our webmails internally using IMAP, it is possible to partition the folder hierarchy into ''namespaces''. Traditionally you are using the root namespace for your private folders. Additionnal namespaces can be created and will appear among your own folders or separate, depending on your mail client's choice of representation. To avoid name clashes, we decided to prefix all additionnal namespace names with a '''#'''. Since 2011-05-14, the following extra namespaces are created and reserved: * #Shared, containing all folders other users decided to share with you * #MilkyPond, containing public MP/DC information mailboxes you may subscribe at will Using IMAP, it is possible to setup rights (read only, write allowed…) to your own folders in order to share them with other users, or group of users. Public folders are owned by noone, and must be created by DC administrators ; if you need one, send us a request and we may be able to create it and delegate administration to your care (namespace name is subject to approval). Once created, public folders can be administered like shared folders. Client mail softwares support: * Horde: support namespaces, shared folders configurable via ''Options->Share Folders'' menu but no ACLs for public folders * Icedove/Thunderbird: support namespaces, shared and public folders configurable via folder selection and ''Tools->Imap-ACL'' menu action Most other softwares have namespace support only, so you should be able to use shared/public folders you have rights on but not configure them yourself (tell us if you know more software supporting this feature) == Limitations == === Maximum Mail Size === Mail you send or receive are limited to '''10MB'''. If you need to transmit much bigger data, then a mail transport is not appropriate, you'd better use a file sharing method instead. === Quotas === Even if it would be nice to live without it, we had to establish quotas to force people sort their mails out once in a while and delete useless things instead of leaving an ever-growing mess behind. The default quota is '''512MB''' which is not that big but should match needs of most users. This said, you may ask us for more and there's no reason we would refuse a reasonable demand. == Technical Details == This service is made using: * [http://www.postfix.org/ Postfix] * [http://dovecot.org/ Dovecot] * [http://dspam.sourceforge.net DSPAM] * [http://johannes.sipsolutions.net/Projects/dovecot-antispam dovecot-antispam] * [https://projects.duckcorp.org/projects/spoolinger Spoolinger] * [http://www.horde.org/ Horde] * [http://www.squirrelmail.org/ SquirrelMail] * [http://www.roundcube.net/ RoundCube] 152070507db725009d1680caf89e6f491ea3061d 356 355 2012-01-30T18:56:07Z Duck 2 wikitext text/x-wiki {{Template:Service | description = Available services: * multiple email addresses (mailboxes+aliases or redirections) based on the ''milkypond.org'' (or maybe ''duckcorp.org'') domain * roaming accounts to be able to send emails wherever you are If you want email addresses using you own domain(s), see the [[Services/MailHosting|mail hosting service]]. | prerequisite = | account = global-reg | ipv6 = true | security_notes = Access to the mail services are fully secured, and to your data, nevertheless most mail exchange on the Internet are not. Complete security can be achieved using signed and encrypted mail (see [[wikipedia:Pretty_Good_Privacy|OpenPGP]] and [[wikipedia:S/MIME|S/MIME]]) }} == Access == === Using a Mail Reader === You can retrieve your mails, in case of a real mailbox, using either: * IMAP+TLS (TCP 143) / IMAPS (TCP 993) on imap.duckcorp.org * or POP3+TLS (TCP 110) / POP3S (TCP 995) on pop.duckcorp.org The IMAP protocol is recommended over POP3, as it provides many interesting features. If you want to download all your mails absolutely at home, loosing the ability to read your mail from anywhere on the planet, you can do that with IMAP too (look at your mail client settings). You can use our servers to send mails out too via smtp.duckcorp.org using: * SMTP+TLS (TCP 25) / SMTPS (TCP 465) * and SASL authentication === Using a Web Interface === Several [https://webmail.duckcorp.org/ webmail interfaces] are available. == Antivirus and Antispam == Mails stored on our server are checked upon arrival for viruses and SPAMs. Mail redirected to a third party mailbox are not, not to mess with the strategy of the the final destination (which could arm learning greatly). Mails being viruses are suppressed automatically upon arrival. Once in a week, an extra antivirus check is done on all hosted mailboxes, to remove viruses not detected at the time it arrived (our antivirus database is updated daily), so you may see such mail disappear from your mailbox, don't fear. SPAMs are more difficult to detect, and it is an error-prone process, so we chose to use a learning software instead of using a global database. On the bright side of things, you would never loose mails and the software should be able to learn what is a SPAM from '''your''' point of view (which has proved to differ slightly between our users), but on the grey side you will have to teach him regularly to avoid errors. When your account is created, it acts like an empty headed body letting everything through, but after a few weeks of teaching it is able to recognize most of your habits and block a lot of annoying SPAM. Teaching the system is called ''retraining''. ==== Retraining using the Special ''Junk'' Folder ==== ==== Retraining via Web Interface ==== Use the [https://spamfilter.duckcorp.org/ web interface] to retrain from errors in the ''History'' page. ==== Retraining via Mail ==== Resend SPAMs to ''dc-spam@duckcorp.org'' and HAM (non-SPAM) to ''dc-ham@duckcorp.org''. {{warning}} PLEASE TAKE CARE to use the ''resend'' function of your mailer and never use ''forward'', which would result in '''yourself''' being considered as SPAN or HAM. ==== User Settings ==== You can yourself setup a few parameters in the ''Preferences'' page of the [https://spamfilter.duckcorp.org/ web interface], mostly: * how the system should train: ** TEFT (''On every new message scanned by the filter''): useful to learn very quickly especially on a new mailbox or when you've got tons of spam on your addresses, but you need to train it regulary (daily is better) or it will learn wrong (very quickly too !) ** TOE (''Only when the filter makes a mistake''): slow learning, but if you don't have time for training very often or go on long holidays without internet access this mode will give you a stable behavior ** TUM (''Only with new data or if the filter makes a mistake''): trade-off between the two previous modes, learn quite fast and not too demanding, adapts better to new SPAMs then TOE * filter sensitivity: you can ask the system to be more or less aggressive * message handling: ** ''Quarantine the message'': mails are not delivered to your mailbox but retained by the system and you can only manage them through the [https://spamfilter.duckcorp.org/ web interface] ; if you retrain a quarantined mail as HAM, it will be freed from quarantine and delivered in your mailbox at once ; in this mode, you need to flush your quarantine once in a while ** ''Tag the Subject header with'': mails are delivered with a modified title (which is a tad ugly) ** ''Deliver the message normally with a X-DSPAM-Result header'': mails are delivered with a special field in your mail headers (not always visible depending on your mail client and its configuration) ; this is quite handy if you prefer SPAMs arranged in a specific folder * ''Disable DSPAM filtering'': you may switch off filtering at your own risk We strongly recommend using TEFT with daily training for a few weeks then switching to TUM. If you need to go away for a long time, switching to TOE is recommended. Using the quarantine feature is also a safe choice, as the web interface is quite easy to use. == Mail Filtering == With your favourite mail client, you can probably filter your mails in proper folders already. Nevertheless, this can be a annoying operation: * blocking you mail client for a long time if you have to process plenty of mails * downloading each mail information, and sometimes content (depending on your filters), is lenghty too, and cost much bandwidth * syncing filters accross your machines (home desktop, laptop, office machine…) is a pain in the ass * processing only when you're online prevents triggering actions in a timely manner (automatic redirect, vacation messages…), and running a machine 24/7 with a mail client polling new mails every 30s is not a solution We provide a much better way to do this using the [[wikipedia:Sieve_(mail_filtering_language)|SIEVE]] filters. Shortly, SIEVE is a language dedicated to expressing mail filters. Our server is able to process your mails according to these filters as soon as they arrive. You then don't have to care about them anymore, and may use light mail clients or webmails when you're not on your machine with your favourite software. To push your filters on the server, a dedicated protocol exists: : MANAGESIEVE (TCP 4190) on sieve.duckcorp.org Several softwares support managing SIEVE rules: * Icedove/Thunderbird using the SIEVE extension (in xul-ext-sieve Debian package) provides a rules editor * Horde (Ingo) provides an easy to use web interface * Squirrelmail with the Avelsieve extension provides an easy to use web interface * Roundcube with an extension provides an easy to use web interface * sieve-connect provides a CLI to upload/download/activate your rules files (tell us if you know more software supporting this feature) You can read more info about SIEVE here: * supported SIEVE features on our server: http://pigeonhole.dovecot.org/ * http://www.fastmail.fm/docs/sieve/ * http://sieve.info/ == Fetching eMails from an External Mailbox == {{todo}} == Shared/Public Folders == You may need to share mails or messages with friends or people you do stuff with (in a project or association). Depending on your needs, two solutions are possible: * share some of your own private folders, thus called ''shared folders'' * manage a special folder hierarchy, called ''public folders'' (even if they may not be accessible to everyone) Through IMAP, or our webmails internally using IMAP, it is possible to partition the folder hierarchy into ''namespaces''. Traditionally you are using the root namespace for your private folders. Additionnal namespaces can be created and will appear among your own folders or separate, depending on your mail client's choice of representation. To avoid name clashes, we decided to prefix all additionnal namespace names with a '''#'''. Since 2011-05-14, the following extra namespaces are created and reserved: * #Shared, containing all folders other users decided to share with you * #MilkyPond, containing public MP/DC information mailboxes you may subscribe at will Using IMAP, it is possible to setup rights (read only, write allowed…) to your own folders in order to share them with other users, or group of users. Public folders are owned by noone, and must be created by DC administrators ; if you need one, send us a request and we may be able to create it and delegate administration to your care (namespace name is subject to approval). Once created, public folders can be administered like shared folders. Client mail softwares support: * Horde: support namespaces, shared folders configurable via ''Options->Share Folders'' menu but no ACLs for public folders * Icedove/Thunderbird: support namespaces, shared and public folders configurable via folder selection and ''Tools->Imap-ACL'' menu action Most other softwares have namespace support only, so you should be able to use shared/public folders you have rights on but not configure them yourself (tell us if you know more software supporting this feature) == Limitations == === Maximum Mail Size === Mail you send or receive are limited to '''10MB'''. If you need to transmit much bigger data, then a mail transport is not appropriate, you'd better use a file sharing method instead. === Quotas === Even if it would be nice to live without it, we had to establish quotas to force people sort their mails out once in a while and delete useless things instead of leaving an ever-growing mess behind. The default quota is '''512MB''' which is not that big but should match needs of most users. This said, you may ask us for more and there's no reason we would refuse a reasonable demand. == Technical Details == This service is made using: * [http://www.postfix.org/ Postfix] * [http://dovecot.org/ Dovecot] * [http://dspam.sourceforge.net DSPAM] * [http://johannes.sipsolutions.net/Projects/dovecot-antispam dovecot-antispam] * [https://projects.duckcorp.org/projects/spoolinger Spoolinger] * [http://www.horde.org/ Horde] * [http://www.squirrelmail.org/ SquirrelMail] * [http://www.roundcube.net/ RoundCube] 3807967fa1210f4e5bac000c2e6a1779f5de9c50 357 356 2012-01-30T19:14:05Z Duck 2 /* Antivirus and Antispam */ wikitext text/x-wiki {{Template:Service | description = Available services: * multiple email addresses (mailboxes+aliases or redirections) based on the ''milkypond.org'' (or maybe ''duckcorp.org'') domain * roaming accounts to be able to send emails wherever you are If you want email addresses using you own domain(s), see the [[Services/MailHosting|mail hosting service]]. | prerequisite = | account = global-reg | ipv6 = true | security_notes = Access to the mail services are fully secured, and to your data, nevertheless most mail exchange on the Internet are not. Complete security can be achieved using signed and encrypted mail (see [[wikipedia:Pretty_Good_Privacy|OpenPGP]] and [[wikipedia:S/MIME|S/MIME]]) }} == Access == === Using a Mail Reader === You can retrieve your mails, in case of a real mailbox, using either: * IMAP+TLS (TCP 143) / IMAPS (TCP 993) on imap.duckcorp.org * or POP3+TLS (TCP 110) / POP3S (TCP 995) on pop.duckcorp.org The IMAP protocol is recommended over POP3, as it provides many interesting features. If you want to download all your mails absolutely at home, loosing the ability to read your mail from anywhere on the planet, you can do that with IMAP too (look at your mail client settings). You can use our servers to send mails out too via smtp.duckcorp.org using: * SMTP+TLS (TCP 25) / SMTPS (TCP 465) * and SASL authentication === Using a Web Interface === Several [https://webmail.duckcorp.org/ webmail interfaces] are available. == Antivirus and Antispam == Mails stored on our server are checked upon arrival for viruses and SPAMs. Mail redirected to a third party mailbox are not, not to mess with the strategy of the the final destination (which could arm learning greatly). Mails being viruses are suppressed automatically upon arrival. Once in a week, an extra antivirus check is done on all hosted mailboxes, to remove viruses not detected at the time it arrived (our antivirus database is updated daily), so you may see such mail disappear from your mailbox, don't fear. SPAMs are more difficult to detect, and it is an error-prone process, so we chose to use a learning software instead of using a global database. On the bright side of things, you would never loose mails and the software should be able to learn what is a SPAM from '''your''' point of view (which has proved to differ slightly between our users), but on the grey side you will have to teach him regularly to avoid errors. When your account is created, it acts like an empty headed body letting everything through, but after a few weeks of teaching it is able to recognize most of your habits and block a lot of annoying SPAM. === Web Interface === The web interface is an easy way to view your mail history, changes your settings, and more. The web interface is available using this URL: https://spamfilter.duckcorp.org/ ==== User Settings ==== You can yourself setup a few parameters in the ''Preferences'' page of the [https://spamfilter.duckcorp.org/ web interface], mostly: * how the system should train: ** TEFT (''On every new message scanned by the filter''): useful to learn very quickly especially on a new mailbox or when you've got tons of spam on your addresses, but you need to train it regulary (daily is better) or it will learn wrong (very quickly too !) ** TOE (''Only when the filter makes a mistake''): slow learning, but if you don't have time for training very often or go on long holidays without internet access this mode will give you a stable behavior ** TUM (''Only with new data or if the filter makes a mistake''): trade-off between the two previous modes, learn quite fast and not too demanding, adapts better to new SPAMs then TOE * filter sensitivity: you can ask the system to be more or less aggressive * message handling: ** ''Quarantine the message'': mails are not delivered to your mailbox but kept by the system and you can only manage them through the [https://spamfilter.duckcorp.org/ web interface] ; if you retrain a quarantined mail as HAM, it will be freed from quarantine and delivered in your mailbox at once ; in this mode, you need to flush your quarantine once in a while ** ''Tag the Subject header with'': mails are delivered with a modified title (which is a tad ugly) ** ''Deliver the message normally with a X-DSPAM-Result header'': mails are delivered with a special field in your mail headers (not always visible depending on your mail client and its configuration) ; this is quite handy if you prefer SPAMs arranged in a specific folder * ''Disable DSPAM filtering'': you may switch off filtering at your own risk We strongly recommend using TEFT with daily training for a few weeks then switching to TUM. If you need to go away for a long time, switching to TOE is recommended. Using the quarantine feature is also a safe choice, as the web interface is quite easy to use. ==== Quarantine ==== If you are using the ''quarantine'' (see the ''message handling'' setting in your preferences, as explained above), then your SPAMs will not go into your mailbox but stay in this stagging area. Through the web interface, you can see these mails in the ''Quarantine'' page and: * free legitimate mails wrongly considered as SPAM by the system * delete real SPAMs if the system was right about them (freeing useful space) === Retraining === Teaching the system what is SPAM and HAM (non-SPAM) is called ''retraining''. ==== Retraining using the Special ''Junk'' Folder (preferred method) ==== {{warning}} This feature is to be available soon! ==== Retraining via Web Interface ==== If you are using the ''quarantine'', then freed mails will automatically be retrained as HAM. Use the [https://spamfilter.duckcorp.org/ web interface] to retrain from errors in the ''History'' page. ==== Retraining via Mail ==== Resend SPAMs to ''dc-spam@duckcorp.org'' and HAM (non-SPAM) to ''dc-ham@duckcorp.org''. {{warning}} PLEASE TAKE CARE to use the ''resend'' function of your mailer and never use ''forward'', which would result in '''yourself''' being considered as SPAN or HAM. == Mail Filtering == With your favourite mail client, you can probably filter your mails in proper folders already. Nevertheless, this can be a annoying operation: * blocking you mail client for a long time if you have to process plenty of mails * downloading each mail information, and sometimes content (depending on your filters), is lenghty too, and cost much bandwidth * syncing filters accross your machines (home desktop, laptop, office machine…) is a pain in the ass * processing only when you're online prevents triggering actions in a timely manner (automatic redirect, vacation messages…), and running a machine 24/7 with a mail client polling new mails every 30s is not a solution We provide a much better way to do this using the [[wikipedia:Sieve_(mail_filtering_language)|SIEVE]] filters. Shortly, SIEVE is a language dedicated to expressing mail filters. Our server is able to process your mails according to these filters as soon as they arrive. You then don't have to care about them anymore, and may use light mail clients or webmails when you're not on your machine with your favourite software. To push your filters on the server, a dedicated protocol exists: : MANAGESIEVE (TCP 4190) on sieve.duckcorp.org Several softwares support managing SIEVE rules: * Icedove/Thunderbird using the SIEVE extension (in xul-ext-sieve Debian package) provides a rules editor * Horde (Ingo) provides an easy to use web interface * Squirrelmail with the Avelsieve extension provides an easy to use web interface * Roundcube with an extension provides an easy to use web interface * sieve-connect provides a CLI to upload/download/activate your rules files (tell us if you know more software supporting this feature) You can read more info about SIEVE here: * supported SIEVE features on our server: http://pigeonhole.dovecot.org/ * http://www.fastmail.fm/docs/sieve/ * http://sieve.info/ == Fetching eMails from an External Mailbox == {{todo}} == Shared/Public Folders == You may need to share mails or messages with friends or people you do stuff with (in a project or association). Depending on your needs, two solutions are possible: * share some of your own private folders, thus called ''shared folders'' * manage a special folder hierarchy, called ''public folders'' (even if they may not be accessible to everyone) Through IMAP, or our webmails internally using IMAP, it is possible to partition the folder hierarchy into ''namespaces''. Traditionally you are using the root namespace for your private folders. Additionnal namespaces can be created and will appear among your own folders or separate, depending on your mail client's choice of representation. To avoid name clashes, we decided to prefix all additionnal namespace names with a '''#'''. Since 2011-05-14, the following extra namespaces are created and reserved: * #Shared, containing all folders other users decided to share with you * #MilkyPond, containing public MP/DC information mailboxes you may subscribe at will Using IMAP, it is possible to setup rights (read only, write allowed…) to your own folders in order to share them with other users, or group of users. Public folders are owned by noone, and must be created by DC administrators ; if you need one, send us a request and we may be able to create it and delegate administration to your care (namespace name is subject to approval). Once created, public folders can be administered like shared folders. Client mail softwares support: * Horde: support namespaces, shared folders configurable via ''Options->Share Folders'' menu but no ACLs for public folders * Icedove/Thunderbird: support namespaces, shared and public folders configurable via folder selection and ''Tools->Imap-ACL'' menu action Most other softwares have namespace support only, so you should be able to use shared/public folders you have rights on but not configure them yourself (tell us if you know more software supporting this feature) == Limitations == === Maximum Mail Size === Mail you send or receive are limited to '''10MB'''. If you need to transmit much bigger data, then a mail transport is not appropriate, you'd better use a file sharing method instead. === Quotas === Even if it would be nice to live without it, we had to establish quotas to force people sort their mails out once in a while and delete useless things instead of leaving an ever-growing mess behind. The default quota is '''512MB''' which is not that big but should match needs of most users. This said, you may ask us for more and there's no reason we would refuse a reasonable demand. == Technical Details == This service is made using: * [http://www.postfix.org/ Postfix] * [http://dovecot.org/ Dovecot] * [http://dspam.sourceforge.net DSPAM] * [http://johannes.sipsolutions.net/Projects/dovecot-antispam dovecot-antispam] * [https://projects.duckcorp.org/projects/spoolinger Spoolinger] * [http://www.horde.org/ Horde] * [http://www.squirrelmail.org/ SquirrelMail] * [http://www.roundcube.net/ RoundCube] e3399df7d88df876af6f995a28687521d34f2c9b 358 357 2012-01-30T19:15:27Z Duck 2 /* User Settings */ wikitext text/x-wiki {{Template:Service | description = Available services: * multiple email addresses (mailboxes+aliases or redirections) based on the ''milkypond.org'' (or maybe ''duckcorp.org'') domain * roaming accounts to be able to send emails wherever you are If you want email addresses using you own domain(s), see the [[Services/MailHosting|mail hosting service]]. | prerequisite = | account = global-reg | ipv6 = true | security_notes = Access to the mail services are fully secured, and to your data, nevertheless most mail exchange on the Internet are not. Complete security can be achieved using signed and encrypted mail (see [[wikipedia:Pretty_Good_Privacy|OpenPGP]] and [[wikipedia:S/MIME|S/MIME]]) }} == Access == === Using a Mail Reader === You can retrieve your mails, in case of a real mailbox, using either: * IMAP+TLS (TCP 143) / IMAPS (TCP 993) on imap.duckcorp.org * or POP3+TLS (TCP 110) / POP3S (TCP 995) on pop.duckcorp.org The IMAP protocol is recommended over POP3, as it provides many interesting features. If you want to download all your mails absolutely at home, loosing the ability to read your mail from anywhere on the planet, you can do that with IMAP too (look at your mail client settings). You can use our servers to send mails out too via smtp.duckcorp.org using: * SMTP+TLS (TCP 25) / SMTPS (TCP 465) * and SASL authentication === Using a Web Interface === Several [https://webmail.duckcorp.org/ webmail interfaces] are available. == Antivirus and Antispam == Mails stored on our server are checked upon arrival for viruses and SPAMs. Mail redirected to a third party mailbox are not, not to mess with the strategy of the the final destination (which could arm learning greatly). Mails being viruses are suppressed automatically upon arrival. Once in a week, an extra antivirus check is done on all hosted mailboxes, to remove viruses not detected at the time it arrived (our antivirus database is updated daily), so you may see such mail disappear from your mailbox, don't fear. SPAMs are more difficult to detect, and it is an error-prone process, so we chose to use a learning software instead of using a global database. On the bright side of things, you would never loose mails and the software should be able to learn what is a SPAM from '''your''' point of view (which has proved to differ slightly between our users), but on the grey side you will have to teach him regularly to avoid errors. When your account is created, it acts like an empty headed body letting everything through, but after a few weeks of teaching it is able to recognize most of your habits and block a lot of annoying SPAM. === Web Interface === The web interface is an easy way to view your mail history, changes your settings, and more. The web interface is available using this URL: https://spamfilter.duckcorp.org/ ==== User Settings ==== You can yourself setup a few parameters in the ''Preferences'' page of the [https://spamfilter.duckcorp.org/ web interface], mostly: * how the system should train: ** TEFT (''On every new message scanned by the filter''): useful to learn very quickly especially on a new mailbox or when you've got tons of spam on your addresses, but you need to train it regulary (daily is better) or it will learn wrong (very quickly too !) ** TOE (''Only when the filter makes a mistake''): slow learning, but if you don't have time for training very often or go on long holidays without internet access this mode will give you a stable behavior ** TUM (''Only with new data or if the filter makes a mistake''): trade-off between the two previous modes, learn quite fast and not too demanding, adapts better to new SPAMs then TOE * filter sensitivity: you can ask the system to be more or less aggressive * message handling: ** ''Quarantine the message'': mails are not delivered to your mailbox but kept by the system and you can only manage them through the [https://spamfilter.duckcorp.org/ web interface] (see below) ; in this mode, you need to flush your quarantine once in a while ** ''Tag the Subject header with'': mails are delivered with a modified title (which is a tad ugly) ** ''Deliver the message normally with a X-DSPAM-Result header'': mails are delivered with a special field in your mail headers (not always visible depending on your mail client and its configuration) ; this is quite handy if you prefer SPAMs arranged in a specific folder * ''Disable DSPAM filtering'': you may switch off filtering at your own risk We strongly recommend using TEFT with daily training for a few weeks then switching to TUM. If you need to go away for a long time, switching to TOE is recommended. Using the quarantine feature is also a safe choice, as the web interface is quite easy to use. ==== Quarantine ==== If you are using the ''quarantine'' (see the ''message handling'' setting in your preferences, as explained above), then your SPAMs will not go into your mailbox but stay in this stagging area. Through the web interface, you can see these mails in the ''Quarantine'' page and: * free legitimate mails wrongly considered as SPAM by the system * delete real SPAMs if the system was right about them (freeing useful space) === Retraining === Teaching the system what is SPAM and HAM (non-SPAM) is called ''retraining''. ==== Retraining using the Special ''Junk'' Folder (preferred method) ==== {{warning}} This feature is to be available soon! ==== Retraining via Web Interface ==== If you are using the ''quarantine'', then freed mails will automatically be retrained as HAM. Use the [https://spamfilter.duckcorp.org/ web interface] to retrain from errors in the ''History'' page. ==== Retraining via Mail ==== Resend SPAMs to ''dc-spam@duckcorp.org'' and HAM (non-SPAM) to ''dc-ham@duckcorp.org''. {{warning}} PLEASE TAKE CARE to use the ''resend'' function of your mailer and never use ''forward'', which would result in '''yourself''' being considered as SPAN or HAM. == Mail Filtering == With your favourite mail client, you can probably filter your mails in proper folders already. Nevertheless, this can be a annoying operation: * blocking you mail client for a long time if you have to process plenty of mails * downloading each mail information, and sometimes content (depending on your filters), is lenghty too, and cost much bandwidth * syncing filters accross your machines (home desktop, laptop, office machine…) is a pain in the ass * processing only when you're online prevents triggering actions in a timely manner (automatic redirect, vacation messages…), and running a machine 24/7 with a mail client polling new mails every 30s is not a solution We provide a much better way to do this using the [[wikipedia:Sieve_(mail_filtering_language)|SIEVE]] filters. Shortly, SIEVE is a language dedicated to expressing mail filters. Our server is able to process your mails according to these filters as soon as they arrive. You then don't have to care about them anymore, and may use light mail clients or webmails when you're not on your machine with your favourite software. To push your filters on the server, a dedicated protocol exists: : MANAGESIEVE (TCP 4190) on sieve.duckcorp.org Several softwares support managing SIEVE rules: * Icedove/Thunderbird using the SIEVE extension (in xul-ext-sieve Debian package) provides a rules editor * Horde (Ingo) provides an easy to use web interface * Squirrelmail with the Avelsieve extension provides an easy to use web interface * Roundcube with an extension provides an easy to use web interface * sieve-connect provides a CLI to upload/download/activate your rules files (tell us if you know more software supporting this feature) You can read more info about SIEVE here: * supported SIEVE features on our server: http://pigeonhole.dovecot.org/ * http://www.fastmail.fm/docs/sieve/ * http://sieve.info/ == Fetching eMails from an External Mailbox == {{todo}} == Shared/Public Folders == You may need to share mails or messages with friends or people you do stuff with (in a project or association). Depending on your needs, two solutions are possible: * share some of your own private folders, thus called ''shared folders'' * manage a special folder hierarchy, called ''public folders'' (even if they may not be accessible to everyone) Through IMAP, or our webmails internally using IMAP, it is possible to partition the folder hierarchy into ''namespaces''. Traditionally you are using the root namespace for your private folders. Additionnal namespaces can be created and will appear among your own folders or separate, depending on your mail client's choice of representation. To avoid name clashes, we decided to prefix all additionnal namespace names with a '''#'''. Since 2011-05-14, the following extra namespaces are created and reserved: * #Shared, containing all folders other users decided to share with you * #MilkyPond, containing public MP/DC information mailboxes you may subscribe at will Using IMAP, it is possible to setup rights (read only, write allowed…) to your own folders in order to share them with other users, or group of users. Public folders are owned by noone, and must be created by DC administrators ; if you need one, send us a request and we may be able to create it and delegate administration to your care (namespace name is subject to approval). Once created, public folders can be administered like shared folders. Client mail softwares support: * Horde: support namespaces, shared folders configurable via ''Options->Share Folders'' menu but no ACLs for public folders * Icedove/Thunderbird: support namespaces, shared and public folders configurable via folder selection and ''Tools->Imap-ACL'' menu action Most other softwares have namespace support only, so you should be able to use shared/public folders you have rights on but not configure them yourself (tell us if you know more software supporting this feature) == Limitations == === Maximum Mail Size === Mail you send or receive are limited to '''10MB'''. If you need to transmit much bigger data, then a mail transport is not appropriate, you'd better use a file sharing method instead. === Quotas === Even if it would be nice to live without it, we had to establish quotas to force people sort their mails out once in a while and delete useless things instead of leaving an ever-growing mess behind. The default quota is '''512MB''' which is not that big but should match needs of most users. This said, you may ask us for more and there's no reason we would refuse a reasonable demand. == Technical Details == This service is made using: * [http://www.postfix.org/ Postfix] * [http://dovecot.org/ Dovecot] * [http://dspam.sourceforge.net DSPAM] * [http://johannes.sipsolutions.net/Projects/dovecot-antispam dovecot-antispam] * [https://projects.duckcorp.org/projects/spoolinger Spoolinger] * [http://www.horde.org/ Horde] * [http://www.squirrelmail.org/ SquirrelMail] * [http://www.roundcube.net/ RoundCube] 6161b4900644e9138466eaed121b8b29d5079a7d 0 60 312 2012-01-26T00:06:08Z Duck 2 Created page with "Services containing personal user data, or consuming a lot of resources, are limited to registered users. In order to do this, each user has one or more accounts associated with …" wikitext text/x-wiki Services containing personal user data, or consuming a lot of resources, are limited to registered users. In order to do this, each user has one or more accounts associated with services. To user certain services a user needs to authenticate using their credentials : a login (username) and password (secret phrase). Accounts may also contain general user information and specific configuration parameters. Each user begins with at least one account in the central user database, the ''master account'', containing credentials to access most services. This account is only deleted when the user leaves. On each service description an ''Account'' field may have the following values: * ''none'': no account is needed to access this service * ''Global'': this service uses the central user database, which means you don't have to remember lots of credentials but only those associated with your master account * ''Local'': this service is either considered not secure enough or is not able to use the central database, and specific credentials are needed; when you update your master account password, the local password remains unchanged and needs to be updated separately As the central database is a LDAP database, the master account is often called a ''LDAP Account''. 92bc508974a85a9eeeeb455d58b6bfdf0ef3e41a 335 312 2012-01-26T22:11:59Z Duck 2 wikitext text/x-wiki == Introduction == Services containing personal user data, or consuming a lot of resources, are limited to registered users. In order to do this, each user has one or more accounts associated with services. To user certain services a user needs to authenticate using their credentials : a login (username) and password (secret phrase). Accounts may also contain general user information and specific configuration parameters. Each user begins with at least one account in the central user database, the ''master account'', containing credentials to access most services. This account is only deleted when the user leaves. As the central database is a LDAP database, the master account is often called a ''LDAP Account''. == Account Requirement for Services == On each service description an ''Account'' field may have the following values: * ''none'': no account is needed to access this service * ''Global'': this service uses the central user database, which means you don't have to remember lots of credentials but only those associated with your master account * ''Local'': this service is either considered not secure enough or is not able to use the central database, and specific credentials are needed; when you update your master account password, the local password remains unchanged and needs to be updated separately == Alternate Authentication == Security sensitive services won't use basic credentials but either: * an RSA/DSA key (like for SSH) * or a GPG key (like for signed mails) This will be advertised in the service description. e1364de23ddbc27e4ff3bb968cd597644fa523b9 0 50 313 285 2012-01-26T00:11:58Z Duck 2 /* Prerequisite */ wikitext text/x-wiki == Prerequisite == You need to ask an administrator for an account, but we need to know you well-enough to ensure you are trustable. This is '''not''' a VIP requirement, but such access can be very dangerous and we don't know any other way to avoid a disaster, sorry. You also need to provide a RSA/DSA public key (see ''ssh-keygen''). == Access == Via SSH with a RSA/DSA key on the fillowing hosts: * thorfinn.duckcorp.org (prefered for lengthy sessions, like screens) * toushirou.duckcorp.org (mostly useful to manage Web/FTP data) == Available Resources == The following resources are available and will remain until we advertise a scheduled removal. If you miss something you can send us a request. === Locales === * en_GB.UTF-8 * en_US.UTF-8 * fr_FR.UTF-8 * ja_JP.EUC-JP * ja_JP.UTF-8 === Shells === * dash * bash * zsh * ksh * tcsh === Programs === * aspell * dict * emacs * irssi (with plugins) * latex (full TeXlive) * screen * sieve-connect * vim * w3m * weechat (with plugins) Additional tools: * [[Services/VCS|VCS tools]] == Technical Details == This service is made using: * [http://www.openssh.org/ OpenSSH] 50849d8e574650ca3d5020afe0500f80ac2e058a 338 313 2012-01-26T22:23:58Z Duck 2 wikitext text/x-wiki {{Template:Service | description = Remote [[wikipedia:Shell_(computing)|shell]] to a DuckCorp machine. | prerequisite = You need to ask an administrator for an account, but we need to know you well-enough to ensure you are trustable. This is '''not''' a VIP requirement, but such an access can be very dangerous and we don't know any other way to avoid a disaster, sorry. You also need to provide a RSA/DSA public key (see ''ssh-keygen''). | account = global-reg | ipv6 = true | security_notes = This service is secure. }} == Access == Via SSH with a RSA/DSA key on the fillowing hosts: * thorfinn.duckcorp.org (prefered for lengthy sessions, like screens) * toushirou.duckcorp.org (mostly useful to manage Web/FTP data) == Available Resources == The following resources are available and will remain until we advertise a scheduled removal. If you miss something you can send us a request. === Locales === * en_GB.UTF-8 * en_US.UTF-8 * fr_FR.UTF-8 * ja_JP.EUC-JP * ja_JP.UTF-8 === Shells === * dash * bash * zsh * ksh * tcsh === Programs === * aspell * dict * emacs * irssi (with plugins) * latex (full TeXlive) * screen * sieve-connect * vim * w3m * weechat (with plugins) Additional tools: * [[Services/VCS|VCS tools]] == Technical Details == This service is made using: * [http://www.openssh.org/ OpenSSH] 45eb0597df0af1abcb29d211562a990a91344e1e 10 61 328 2012-01-26T21:21:38Z Duck 2 Created page with "[https://projects.duckcorp.org/issues/{{{1}}} DC-Projects#{{{1}}}]" wikitext text/x-wiki [https://projects.duckcorp.org/issues/{{{1}}} DC-Projects#{{{1}}}] fe0b4f963a4440238d2f0e41e5d3d8a3351e05ea 0 55 329 295 2012-01-26T21:26:37Z Duck 2 wikitext text/x-wiki {{Template:Service | description = [[wikipedia:Irc|IRC]] (Internet Relay Chat) is a chat system. We have our own internal network, formerly used to contact administrators and discuss with other users. Even is not advertise widely, external people may join the network, so you can invite your friend. | prerequisite = | account = | ipv6 = true | security_notes = Your messages are secured if you connect using the secure port(s), but you need to ensure the recipient uses a secure connection too ; this can be achieved using chanmode +S (see below). {{warning}} Unfortunately, due to a bug in the software (see {{dc-projects|233}}), the link between our server is not yet fully secured, but you can work around this problem if you talk only to people connected to the same server as yourself. }} == Access == === Using an IRC Software === To connect you need and IRC client, like for example: * [http://irssi.org/ Irssi] * [http://www.pidgin.im Pidgin] * [http://weechat.org/ WeeChat] You need to configure these parameters: * host: irc.milkypond.org * port: ** 6680 (if you want a secure connection using SSL/TLS) ** 6667 or 6669 (because 6667 is sometimes filtered) No password is needed to connect. === Using a Web Interface === Use the following URL: https://irconweb.milkypond.org/ == Official Channels == * #MilkyPond: main channel used to meet with other users and friends and ask general questions * #DuckCorp: contact with DuckCorp Administrators and technical discussions * #News: news feeds on IRC (deprecated but still working) == Contacting IRC Administrators == In case of problems on IRC you can find connected administrators using this command (mind the idle time): /QUOTE STATS p Beware IRC Administrators may not be DuckCorp Administrators. == Features == === Commands === You can see available commands using this command: /QUOTE HELP You can get help about a particular command using this command: /QUOTE HELP &lt;command&gt; ==== Additional Commands for IRC Administrators ==== All special commands are listed in the Oper MOTD. === User Modes === You can see available channel modes using this command: /QUOTE HELP UMODE ==== Mode +g ==== (partial note from the ircd-ratbox documentation) When a client is set +g, that user will be in "Caller ID" mode. Any user that messages a +g client will receive a notice saying that they are in +g (server side ignore) mode. The target client (who is set +g) will also receive a notice saying that so and so messaged them, and that they are in +g mode. The target of the message will only receive one notification per minute, from any client, in order to help prevent flooding. The sender will '''not''' have the rate limit, and will receive a notice saying the target is in +g mode every time they send a message. Note that this behavior is similar to the way AWAY messages are done. There are numerous benefits for both opers and regular users, including the ability to stop spambot messages from ever reaching your client, stopping private message and CTCP floods, and being able to sit on IRC in privacy. One question that arises is how to message specific users, while blocking out everyone else. The command ACCEPT is your answer. To add a user to your accept list, issue the raw command: /QUOTE ACCEPT &lt;nick&gt;,&lt;nick&gt;,&lt;nick&gt;,… That user will now be able to send messages to your client until the association is broken. Associations break in one of the following situations: when an accepted user QUIT's (or is on the other side of a split), you QUIT, or the accepted user changes their nick. The reason why a remote user's nick change will remove them from your accept list is so that you cannot track a user after they changed their nick. Viewing the accept list is also very easy. Issue the raw command: /QUOTE ACCEPT * Removing a user from your accept list is also simple. Issue the command: /QUOTE ACCEPT -&lt;nick&gt; === Channel Modes === You can see available channel modes using this command: /QUOTE HELP CMODE These extra modes are also available: * +r - registered - Users must be registered with services to JOIN * +S - ssl only - Requires SSL/TLS connections to join === IRC Services === To help not loose your favorite nick or channel, the IRC Services can register them so you're still in control. It also helps manage channel with a variety of tools. Look at the user introduction manual in the documentation below. List of Services: * ALIS: search available channels * USERSERV: register an account List of Services available with an account (see USERSERV): * NICKSERV: register nicknames * CHANSERV: register and manage channels * MEMOSERV: send and receive memos from other registered users To get help on each service commands, use the following command: /QUOTE &lt;service&gt; HELP ==== Additional Services for IRC Administrators ==== (exact privileges depends on trust and delegation) * OPERSERV: superadmin commands * JUPESERV: manage "jupes" (fake connections to prevent unwanted links) * GLOBAL: messaging all users * BANSERV: managing global bans * OPERBOT: manage the OperBot * WATCHSERV: spy on service commands (only available via DCC) You also may be able to access services via DCC CHAT, which is handy when a flood occurs, using: /DCC CHAT operserv == Documentation == * [http://docs.ratbox.org/svc_userintro.shtml IRC Services Introduction] == Technical Details == This service is made using: * [http://www.ratbox.org/ ircd-ratbox] * [http://services.ratbox.org/ ratbox-services] 2124a9530b43295910c59dc06c4b16eeacdda54e 0 56 330 296 2012-01-26T21:47:08Z Duck 2 wikitext text/x-wiki {{Template:Service | description = An [[wikipedia:IRC_bouncer#IRC|IRC Bouncer]] is a proxy, relaying connection to one or multiple IRC servers. When you disconnect from the bouncer, the bouncer keep your connections alive and store messages sent to you or in channels you joined. When you are back connected to the bouncer, all your channels and private chats are automatically reopened, and you can access messages you missed. | prerequisite = You need to provide the following information: * default nick / user / realname * an encrypted password generated using the ''bipmkpw'' command (available on Thorfinn, or in the [http://bip.milkypond.org/ Bip] software) * list of networks you wish to connect to * list of channel you want to autojoin (for each network) * an other specific settings you wish | account = local | ipv6 = false | security_notes = Your messages are securely delivered to our server, but the rest of the transport security depends on the network capabilities (see the network list below). }} == Access == To connect you need and IRC client, as the bouncer acts like an IRC server. See the [[IRC#Using_an_IRC_Software|here]] for examples of usable softwares. The bouncer is able to connect to multiple networks, but so as not to mix connections (which may have users and channels of the same name, creating a conflict), you need to connect to the bouncer multiple times, one for each network. You need to configure these parameters for each connection: * host: irc-bouncer.duckcorp.org * port: 7778 * password: &lt;user&gt;:&lt;user-password&gt;:&lt;connection&gt; * activate SSL/TLS &lt;user&gt; is your username, &lt;user-password&gt; your password, and &lt;connection&gt; the name of the network you want to connect to (see the list of available networks below). == Available Networks == These are the available networks you may access, depending on your configuration: * milkypond (secured) * minbif ([[Services/IRC-IM-GW|IRC to IM gateway]], secured) * debianjp * freenode (secured) * oftc (secured) * ircnet * epiknet * gimpnet * rezosup * iie (secured) * n7mm (secured) == Technical Details == This service is made using: * [http://bip.milkypond.org/ Bip] 326b30a813740219c2f0eed50951ac44883b9f50 0 52 331 281 2012-01-26T21:49:09Z Duck 2 wikitext text/x-wiki {{Template:Service | description = The Media gallery is a website where you can store, enrich, and share your photo and video files. You can organize them in a hierarchy of folders, and setup permissions if you want to restrict access. | prerequisite = | account = local | ipv6 = true | security_notes = This service is secure but beware to properly manage the permissions on your folder. }} == Access == Use this URL in your browser: https://photos.duckcorp.org/ On Android, you can also use [http://f-droid.org/repository/browse/?fdid=net.dahanne.android.regalandroid this application] to access your gallery easily. == Alternate File Upload Method == Besides several methods to transfer files to the gallery, if you have a [[Services/FTP|file repository]] account you may use it to drop your files in the ''photos-perso-dc'' folder. == Documentation == * ''Gallery 2'' section in the [http://codex.gallery2.org/Main_Page Help Page] == Technical Details == This service is made using: * [http://gallery.menalto.com/ Gallery 2] b302b26acb60cf93c843a21af3abb7a0b65d1757 0 53 332 287 2012-01-26T21:52:58Z Duck 2 wikitext text/x-wiki {{Template:Service | description = The file repository is a general-purpose file exchange method. You push files into it and they are kept until you remove them. You may also share them with a other people. | prerequisite = You need to ask an administrator for an account if you want to push your own files, but you don't need anything if you just want to retrieve files from the public folders. | account = global-reg | ipv6 = true | security_notes = This service is secure. }} == Access == You need a FTP client software to access this service, for example: * on GNU/*: filezilla or lftp * on MacOS: CyberDuck * on Windows: filezilla Most browsers should also work for read access. The publics folders are available for read access using this URL: ftp://ftp.duckcorp.org/ If you want to push files, you need to authenticate with SSL/TLS using this URL: ftps://ftps.duckcorp.org/ You may also access files directly on Toushirou in ''/ftp/ftp.duckcorp.org/'' if you have a [[Services/Shell|shell access]]. == Folders == Summary of important folders for write access: * photos-perso-dc: upload zone for the [[Services/Gallery|gallery]] * private: restricted folders, for users or groups of users; ask an administrator if you need private folders * public: folders which can be read by everybody (accessible directly without authentication on ftp://ftp.duckcorp.org/) * repository: upload folders for the [[Services/SoftwareRepository|software repository]] facility * sendfile: arrival folders for the [[Services/SAFT|shell transfer]] service * sites: folders for hosted websites content == Documentation == * generic documentation on [[wikipedia:Ftp|FTP]] == Technical Details == This service is made using: * [http://proftpd.org/ ProFTPD] 6abf82123250da25fa136555a8b364b6e62a8571 0 54 333 280 2012-01-26T21:59:59Z Duck 2 wikitext text/x-wiki {{Template:Service | description = A code review software is a tool to help improve software quality. It is intended for software developers to help them receive feedback on their patches. | prerequisite = You need to ask an administrator for an account if you want to create or comment on review, but you don't need anything if you just want to watch existing ones. | account = global-reg | ipv6 = true | security_notes = This service is secure. }} == Access == Use the following URL and login: https://codereview.duckcorp.org/ == Documentation == * [http://code.google.com/p/rietveld/wiki/CodeReviewHelp Help Page] * generic documentation on [[wikipedia:Code_review|Code Review]] == Technical Details == This service is made using: * [http://code.google.com/p/rietveld/ Rietveld] * [http://www.djangoproject.com/ Django] bac56e536c3ef37df491e4d0834304cd31769638 0 43 334 283 2012-01-26T22:06:37Z Duck 2 wikitext text/x-wiki {{Template:Service | description = Available services: * full hosting (NS1) on our servers * replication (NS2) on our servers or, at your choice, partner servers (currently via Hivane) | prerequisite = You need to buy a domain from a registrar and ask an administrator to configure this service. | account = global-reg | ipv6 = true | security_notes = Your zone content can be secured using DNSSEC, and replication can be secured too using TSIG (see below). }} == Master Zones Administration == To have your master zone modified on our servers, you can: * use our [[UserMagicalInterface]] * ask administrators == DNS Security == To provide as much security as possible, DC supports the following mechanisms. === [[wikipedia:TSIG|TSIG]] === This protocol allows a secure transfer of zones between primary and secondary servers. The DC's DNS servers support TSIG and comminication between them are always secured. The following entities are known to support TSIG and can then securely transfer zones to/from DC: * [http://www.hivane.net/ Hivane] === [[wikipedia:Domain_Name_System_Security_Extensions|DNSSEC]] === ==== What is DNSSEC? ==== This protocol aims at establishing a chain of trust, from the root of the DNS, to ensure response to queries on a zone has not been altered on the way. With the root zone public key, it is possible to validate the replies step by step down to your zone, for example: root public key -> ''.'' zone -> NS for ''org.'' -> ''org.'' zone -> NS for ''milkypond.org.'' -> ''milkypond.org.'' zone -> ''irc.milkypond.org.'' entry. Unfortunately, many DNS providers do not support DNSSEC (Gandi is one of them :-/). In order to help people work on securing their zone, and be ready when their provider is, the [http://www.isc.org/ ISC] created a solution to validate zones using another secure path: by publishing security associations in a special zone (''dlv.isc.org'', called the DLV Registry), which itself can be validated the normal way. This is only a stopgap, but as providers seems not to be in a hurry to do their job, DC decided to use it. ==== How to use it for my zones? ==== DC DNS servers are able to handle the complicated procedure needed to sign a zone for you. You can just modify it the classic way, and have it signed automatically. You just need to ask us to switch the zone to the secure mode. If your provider gladly support DNSSEC, we can provide the necessary information for the chain of trust; if not, we can use the DLV registry. Beware DNS always means propagation delays, so you may have to wait a few days before the switch is completed and your zone fully secured over the whole world. ==== How to test my zone is secured? ==== First, you need a validating DNS server (explanations for ''bind9'' on Debian): * get the root zone public key (using this script for example: [[File:Get dns root zone key.sh]]) * add the key to your configuration (in ''/etc/bind/named.conf''): include "/etc/bind/root.keys"; * add in your global options (''/etc/bind/named.conf.options''): dnssec-enable yes; dnssec-validation yes; dnssec-lookaside auto; * restart bind The DLV Registry public key is already provided in the ''bind9'' package. Then, you can check it with the ''dig'' tool (available in the ''dnsutils'' Debian package): dig +dnssec <zone> Look at the flags: it is secured if you find the ''ad'' flag. If there is the ''aa'' flag instead, then you are interrogating on of the authoritative DNS servers for the zone, it is also secure, but better test it on another server to be sure it is propagated. {{warning}} If you check an entry of your zone which is a CNAME, beware the CNAME is resolved and if the destination name cannot be validated, then your entry won't either. == Documentation == * generic documentation on [[wikipedia:Domain_Name_System|DNS]] == Technical Details == This service is made using: * [http://bind9.net/ Bind9] * [http://www.opendnssec.org/ OpenDNSSEC] 568c3f4cf525137510f5114f41866f029bc0ae04 336 334 2012-01-26T22:16:14Z Duck 2 wikitext text/x-wiki {{Template:Service | description = Available services: * full hosting (NS1) on our servers * replication (NS2) on our servers or, at your choice, partner servers (currently via Hivane) | prerequisite = You need to buy a domain from a [[wikipedia:Domain_name_registrar|registrar]] and ask an administrator to configure this service. | account = global-reg | ipv6 = true | security_notes = Your zone content can be secured using DNSSEC, and replication can be secured too using TSIG (see below). }} == Master Zones Administration == To have your master zone modified on our servers, you can: * use our [[UserMagicalInterface]] * ask administrators == DNS Security == To provide as much security as possible, DC supports the following mechanisms. === [[wikipedia:TSIG|TSIG]] === This protocol allows a secure transfer of zones between primary and secondary servers. The DC's DNS servers support TSIG and comminication between them are always secured. The following entities are known to support TSIG and can then securely transfer zones to/from DC: * [http://www.hivane.net/ Hivane] === [[wikipedia:Domain_Name_System_Security_Extensions|DNSSEC]] === ==== What is DNSSEC? ==== This protocol aims at establishing a chain of trust, from the root of the DNS, to ensure response to queries on a zone has not been altered on the way. With the root zone public key, it is possible to validate the replies step by step down to your zone, for example: root public key -> ''.'' zone -> NS for ''org.'' -> ''org.'' zone -> NS for ''milkypond.org.'' -> ''milkypond.org.'' zone -> ''irc.milkypond.org.'' entry. Unfortunately, many DNS providers do not support DNSSEC (Gandi is one of them :-/). In order to help people work on securing their zone, and be ready when their provider is, the [http://www.isc.org/ ISC] created a solution to validate zones using another secure path: by publishing security associations in a special zone (''dlv.isc.org'', called the DLV Registry), which itself can be validated the normal way. This is only a stopgap, but as providers seems not to be in a hurry to do their job, DC decided to use it. ==== How to use it for my zones? ==== DC DNS servers are able to handle the complicated procedure needed to sign a zone for you. You can just modify it the classic way, and have it signed automatically. You just need to ask us to switch the zone to the secure mode. If your provider gladly support DNSSEC, we can provide the necessary information for the chain of trust; if not, we can use the DLV registry. Beware DNS always means propagation delays, so you may have to wait a few days before the switch is completed and your zone fully secured over the whole world. ==== How to test my zone is secured? ==== First, you need a validating DNS server (explanations for ''bind9'' on Debian): * get the root zone public key (using this script for example: [[File:Get dns root zone key.sh]]) * add the key to your configuration (in ''/etc/bind/named.conf''): include "/etc/bind/root.keys"; * add in your global options (''/etc/bind/named.conf.options''): dnssec-enable yes; dnssec-validation yes; dnssec-lookaside auto; * restart bind The DLV Registry public key is already provided in the ''bind9'' package. Then, you can check it with the ''dig'' tool (available in the ''dnsutils'' Debian package): dig +dnssec <zone> Look at the flags: it is secured if you find the ''ad'' flag. If there is the ''aa'' flag instead, then you are interrogating on of the authoritative DNS servers for the zone, it is also secure, but better test it on another server to be sure it is propagated. {{warning}} If you check an entry of your zone which is a CNAME, beware the CNAME is resolved and if the destination name cannot be validated, then your entry won't either. == Documentation == * generic documentation on [[wikipedia:Domain_Name_System|DNS]] == Technical Details == This service is made using: * [http://bind9.net/ Bind9] * [http://www.opendnssec.org/ OpenDNSSEC] 835fef1080b878d191db63d635003cab046f7ce0 0 51 337 284 2012-01-26T22:19:48Z Duck 2 wikitext text/x-wiki {{Template:Service | description = Available services: * full hosting (MX1) on our servers * fallback retention (MX2) on our servers or, at your choice, partner servers (currently via Hivane) | prerequisite = You need to buy a domain from a [[wikipedia:Domain_name_registrar|registrar]], setup a DNS (can be [[Services/DNS|hosted here]] too), and ask an administrator to configure this service. | account = global-reg | ipv6 = true | security_notes = See the [[Services/Mail|eMail service]]'s security notes. }} == Full Hosting == You can have multiple email addresses which can be: * real mailboxes * redirections towards third party addresses * wildcards based on your domains or sub-domains. Have a look at our [[Services/Mail|complete set of mail services]]. == Fallback retention == The current retention period on our servers is 2 weeks, but can be temporary or permanently increased if needed. Mails flowing back to your primary server can be protected using TLS with certificate verification if you wish. Antivirus and antispam filtering are not applied to relayed mails, so we do not mess with your prefered strategy on your primary server, nevertheless basic checks (EHLO, DNS…) and RBL scoring are done to avoid accepting tons of SPAMs. == Technical Details == See the [[Services/Mail#Technical_Details|eMail service page]]. c7fab58d42debb6226ad88820db067d24a0252c3 0 39 343 298 2012-01-26T23:10:11Z Duck 2 wikitext text/x-wiki Here is a short overview of the services provided by DuckCorp. Our services are supervised and important data are [[Services/Backup|saved regularly]]. {{warning}} [[Services/Security|Notes about security !]] {| class="wikitable" style="text-align: center; width: 100%;" |+ Available Services |- ! Category !! colspan="2" | Service !! Access !! Description |- | rowspan="7" | Communication || rowspan="2" | Mail || [[Services/Mail|eMails]] || users || style="text-align: left;" | Mail boxes with anti-spam/anti-virus, filtering…, or mail redirections |- | [[Services/ML|Mailing-Lists]] || users || style="text-align: left;" | Distribution lists for mails |- | rowspan="3" | IRC || [[Services/IRC|IRC Network]] || public || style="text-align: left;" | MilkyPond Chat Network using a dedicated software or a Web-interface |- | [[Services/IRC-Bouncer|IRC Bouncer]] || users || style="text-align: left;" | IRC proxy (IRC server relaying IRC communications, keeping connections open and remembering logs) |- | [[Services/IRC-IM-GW|IRC to IM gateway]] || users || style="text-align: left;" | Communication to multiple instant messaging networks through a unified IRC-like interface |- | colspan="2" | [[Services/XMPP|XMPP (Jabber)]] || users || style="text-align: left;" | Global Chat Network (inter-communication between many [[wikipedia:Xmpp#History|well-known public IM services]]) |- | colspan="2" | [[Services/Tribioune|Triboune Libre]] || public || style="text-align: left;" | MilkyPond Web-chat system inspired by [http://linuxfr.org/board the famous one] on [http://linuxfr.org/ Linuxfr.org] |- | rowspan="5" | Sharing || colspan="2" | [[Services/Gallery|Media Gallery]] || public/users || style="text-align: left;" | Photo and video gallery |- | colspan="2" | [[Services/Wiki|Wiki]] || public/users || style="text-align: left;" | Technical knowledge, useful tips… |- | rowspan="3" | Generic || [[Services/FTP|File Repository]] || public/users || style="text-align: left;" | Generic file sharing system (using FTP) |- | [[Services/WebFileExchange|Downloads Links]] || public/users || style="text-align: left;" | Web-based generic file sharing |- | [[Services/SAFT|Shell Transfer]] || trusted || style="text-align: left;" | File transfer system using the SAFT protocol (shell access needed) |- | rowspan="3" | Utilities || colspan="2" | [[Services/WebFeeds|News WebReader]] || users || style="text-align: left;" | News feeds reader through a web interface |- | colspan="2" | [[Services/NTP|Time Server]] || public || style="text-align: left;" | System used to automatically setup time on your machines (and also part of the [http://www.pool.ntp.org/en/ NTP Pool Project]) |- | colspan="2" | [[Services/Dico|Dictionary Server]] || public || style="text-align: left;" | Words searching system via a dedicated software (using the DICT protocol) or a Web-interface |- | rowspan="6" | Development || colspan="2" | [[Services/Projects|Project Management & Issue Tracking]] || public/users || style="text-align: left;" | |- | colspan="2" | [[Services/CodeReview|Code Review]] || public/users || style="text-align: left;" | |- | colspan="2" | [[Services/VCS|VCS]] || public/users || style="text-align: left;" | Code/configuration versioning tools (Git, SVN, Baz, Bzr…) |- | rowspan="2" | Databases || [[Services/SQL|SQL]] || users || style="text-align: left;" | SQL server (PostgreSQL or MySQL) |- | [[Services/LDAP|LDAP]] || users || style="text-align: left;" | LDAP server (OpenLDAP) |- | colspan="2" | [[Services/SoftwareRepository|Software Repository]] || public/users || style="text-align: left;" | Software repository, to provide custom packages (think Debian debs) or installation media (thinks DVDs) |- | rowspan="5" | Hosting || colspan="2" | [[Services/DNS|DNS]] || users || style="text-align: left;" | Domain Name System (NS1/NS2, DNSSEC…) |- | colspan="2" | [[Services/MailHosting|Mail Domains]] || users || style="text-align: left;" | Mail hosting (MX1/MX2) |- | colspan="2" | [[Services/WebHosting|Web Sites/Applications]] || users || style="text-align: left;" | Web pages using HTML/XHTML, CSS, JS, and various server-side programming languages (SSI, PHP, Perl, Python, Ruby…), and statistics (analytics data/reports) |- | colspan="2" | [[Services/XMPPHosting|XMPP Domains]] || users || style="text-align: left;" | XMPP Node for a custom domain |- | colspan="2" | [[Services/Shell|Shell]] || trusted || style="text-align: left;" | Useful for website administration, development, run custom scripts, persistent applications for text-mode geeks… |- | rowspan="2" | Network || colspan="2" | [[Services/IPv6-Broker|IPv6 tunnels]] || users || style="text-align: left;" | Access to the IPv6 world through an IPv4 connection |- | colspan="2" | [[Services/NSTX|NSTX]] || users || style="text-align: left;" | Access to the Internet through a restricted WIFI connection (via an IP over DNS tunnel) |} == TODO == * in Services/Wiki: https://wiki.duckcorp.org/ * in Services/Shell: link to SAFT * in Services/XMPP: chitchat * in Services/WebFileExchange: https://stuff.milkypond.org/ * in Services/WebFeeds: https://gossip.duckcorp.org/ * in Services/Projects: https://projects.duckcorp.org/ * in Services/VCS: https://rcs.duckcorp.org/ … 4f4d6d3fd1455a55a49a1167265d05f2094efad1 344 343 2012-01-26T23:27:33Z Duck 2 wikitext text/x-wiki Here is a short overview of the services provided by DuckCorp. Our services are supervised and important data are [[Services/Backup|saved regularly]]. {{warning}} [[Services/Security|Notes about security !]] {| class="wikitable" style="text-align: center; width: 100%;" |+ Available Services |- ! Category !! colspan="2" | Service !! Access !! Description |- | rowspan="7" | Communication || rowspan="2" | Mail || [[Services/Mail|eMails]] || users || style="text-align: left;" | Mail boxes with anti-spam/anti-virus, filtering…, or mail redirections |- | [[Services/ML|Mailing-Lists]] || users || style="text-align: left;" | Distribution lists for mails |- | rowspan="3" | IRC || [[Services/IRC|IRC Network]] || public || style="text-align: left;" | MilkyPond Chat Network using a dedicated software or a Web-interface |- | [[Services/IRC-Bouncer|IRC Bouncer]] || users || style="text-align: left;" | IRC proxy (IRC server relaying IRC communications, keeping connections open and remembering logs) |- | [[Services/IRC-IM-GW|IRC to IM gateway]] || users || style="text-align: left;" | Communication to multiple instant messaging networks through a unified IRC-like interface |- | colspan="2" | [[Services/XMPP|XMPP (Jabber)]] || users || style="text-align: left;" | Global Chat Network (inter-communication between many [[wikipedia:Xmpp#History|well-known public IM services]]) |- | colspan="2" | [[Services/Tribioune|Triboune Libre]] || public || style="text-align: left;" | MilkyPond Web-chat system inspired by [http://linuxfr.org/board the famous one] on [http://linuxfr.org/ Linuxfr.org] |- | rowspan="5" | Sharing || colspan="2" | [[Services/Gallery|Media Gallery]] || public/users || style="text-align: left;" | Photo and video gallery |- | colspan="2" | [[Services/Wiki|Wiki]] || public/users || style="text-align: left;" | Technical knowledge, useful tips… |- | rowspan="3" | Generic || [[Services/FTP|File Repository]] || public/users || style="text-align: left;" | Generic file sharing system (using FTP) |- | [[Services/WebFileExchange|Downloads Links]] || public/users || style="text-align: left;" | Web-based generic file sharing |- | [[Services/SAFT|Shell Transfer]] || trusted || style="text-align: left;" | File transfer system using the SAFT protocol (shell access needed) |- | rowspan="3" | Utilities || colspan="2" | [[Services/WebFeeds|News WebReader]] || users || style="text-align: left;" | News feeds reader through a web interface |- | colspan="2" | [[Services/NTP|Time Server]] || public || style="text-align: left;" | System used to automatically setup time on your machines (and also part of the [http://www.pool.ntp.org/en/ NTP Pool Project]) |- | colspan="2" | [[Services/Dico|Dictionary Server]] || public || style="text-align: left;" | Words searching system via a dedicated software (using the DICT protocol) or a Web-interface |- | rowspan="6" | Development || colspan="2" | [[Services/Projects|Project Management & Issue Tracking]] || public/users || style="text-align: left;" | |- | colspan="2" | [[Services/CodeReview|Code Review]] || public/users || style="text-align: left;" | |- | colspan="2" | [[Services/VCS|VCS]] || public/users || style="text-align: left;" | Code/configuration versioning tools (Git, SVN, Baz, Bzr…) |- | rowspan="2" | Databases || [[Services/SQL|SQL]] || users || style="text-align: left;" | SQL server (PostgreSQL or MySQL) |- | [[Services/LDAP|LDAP]] || users || style="text-align: left;" | LDAP server (OpenLDAP) |- | colspan="2" | [[Services/SoftwareRepository|Software Repository]] || public/users || style="text-align: left;" | Software repository, to provide custom packages (think Debian debs) or installation media (thinks DVDs) |- | rowspan="6" | Hosting || colspan="2" | [[Services/DNS|DNS]] || users || style="text-align: left;" | Domain Name System (NS1/NS2, DNSSEC…) |- | rowspan="2" | Mail || [[Services/MailHosting|Mail Domains]] || users || style="text-align: left;" | Mail hosting (MX1/MX2) |- | [[Services/MLHosting|Mailing-Lists]] || users || style="text-align: left;" | Distribution lists for mail domains |- | colspan="2" | [[Services/WebHosting|Web Sites/Applications]] || users || style="text-align: left;" | Web pages using HTML/XHTML, CSS, JS, and various server-side programming languages (SSI, PHP, Perl, Python, Ruby…), and statistics (analytics data/reports) |- | colspan="2" | [[Services/XMPPHosting|XMPP Domains]] || users || style="text-align: left;" | XMPP Node for a custom domain |- | colspan="2" | [[Services/Shell|Shell]] || trusted || style="text-align: left;" | Useful for website administration, development, run custom scripts, persistent applications for text-mode geeks… |- | rowspan="2" | Network || colspan="2" | [[Services/IPv6-Broker|IPv6 tunnels]] || users || style="text-align: left;" | Access to the IPv6 world through an IPv4 connection |- | colspan="2" | [[Services/NSTX|NSTX]] || users || style="text-align: left;" | Access to the Internet through a restricted WIFI connection (via an IP over DNS tunnel) |} == TODO == * in Services/Wiki: https://wiki.duckcorp.org/ * in Services/Shell: link to SAFT * in Services/XMPP: chitchat * in Services/WebFileExchange: https://stuff.milkypond.org/ * in Services/WebFeeds: https://gossip.duckcorp.org/ * in Services/Projects: https://projects.duckcorp.org/ * in Services/VCS: https://rcs.duckcorp.org/ … 98bf7271b98a6a23ab2abd441176921d491bc08d 345 344 2012-01-26T23:31:11Z Duck 2 wikitext text/x-wiki Here is a short overview of the services provided by DuckCorp. Our services are supervised and important data are [[Services/Backup|saved regularly]]. {{warning}} [[Services/Security|Notes about security !]] {| class="wikitable" style="text-align: center; width: 100%;" |+ Available Services |- ! Category !! colspan="2" | Service !! Access !! Description |- | rowspan="7" | Communication || rowspan="2" | Mail || [[Services/Mail|eMails]] || users || style="text-align: left;" | Mail boxes with anti-spam/anti-virus, filtering…, or mail redirections |- | [[Services/ML|Mailing-Lists]] || users || style="text-align: left;" | Distribution lists for mails |- | rowspan="3" | IRC || [[Services/IRC|IRC Network]] || public || style="text-align: left;" | MilkyPond Chat Network using a dedicated software or a Web-interface |- | [[Services/IRC-Bouncer|IRC Bouncer]] || users || style="text-align: left;" | IRC proxy (IRC server relaying IRC communications, keeping connections open and remembering logs) |- | [[Services/IRC-IM-GW|IRC to IM gateway]] || users || style="text-align: left;" | Communication to multiple instant messaging networks through a unified IRC-like interface |- | colspan="2" | [[Services/XMPP|XMPP (Jabber)]] || users || style="text-align: left;" | Global Chat Network (inter-communication between many [[wikipedia:Xmpp#History|well-known public IM services]]) |- | colspan="2" | [[Services/Tribioune|Triboune Libre]] || public || style="text-align: left;" | MilkyPond Web-chat system inspired by [http://linuxfr.org/board the famous one] on [http://linuxfr.org/ Linuxfr.org] |- | rowspan="5" | Sharing || colspan="2" | [[Services/Gallery|Media Gallery]] || public/users || style="text-align: left;" | Photo and video gallery |- | colspan="2" | [[Services/Wiki|Wiki]] || public/users || style="text-align: left;" | Technical knowledge, useful tips… |- | rowspan="3" | Generic || [[Services/FTP|File Repository]] || public/users || style="text-align: left;" | Generic file sharing system (using FTP) |- | [[Services/WebFileExchange|Downloads Links]] || public/users || style="text-align: left;" | Web-based generic file sharing |- | [[Services/SAFT|Shell Transfer]] || trusted || style="text-align: left;" | File transfer system using the SAFT protocol (shell access needed) |- | rowspan="3" | Utilities || colspan="2" | [[Services/WebFeeds|News WebReader]] || users || style="text-align: left;" | News feeds reader through a web interface |- | colspan="2" | [[Services/NTP|Time Server]] || public || style="text-align: left;" | System used to automatically setup time on your machines (and also part of the [http://www.pool.ntp.org/en/ NTP Pool Project]) |- | colspan="2" | [[Services/Dico|Dictionary Server]] || public || style="text-align: left;" | Words searching system via a dedicated software (using the DICT protocol) or a Web-interface |- | rowspan="6" | Development || colspan="2" | [[Services/Projects|Project Management & Issue Tracking]] || public/users || style="text-align: left;" | |- | colspan="2" | [[Services/CodeReview|Code Review]] || public/users || style="text-align: left;" | |- | colspan="2" | [[Services/VCS|VCS]] || public/users || style="text-align: left;" | Code/configuration versioning tools (Git, SVN, Baz, Bzr…) |- | rowspan="2" | Databases || [[Services/SQL|SQL]] || users || style="text-align: left;" | SQL server (PostgreSQL or MySQL) |- | [[Services/LDAP|LDAP]] || users || style="text-align: left;" | LDAP server (OpenLDAP) |- | colspan="2" | [[Services/SoftwareRepository|Software Repository]] || public/users || style="text-align: left;" | Software repository, to provide custom packages (think Debian debs) or installation media (thinks DVDs) |- | rowspan="6" | Hosting || colspan="2" | [[Services/DNS|DNS]] || users || style="text-align: left;" | Domain Name System (NS1/NS2, DNSSEC…) |- | rowspan="2" | Mail || [[Services/MailHosting|Mail Domains]] || users || style="text-align: left;" | Mail hosting (MX1/MX2) |- | [[Services/MLHosting|Mailing-Lists]] || users || style="text-align: left;" | Distribution lists for mail domains |- | colspan="2" | [[Services/WebHosting|Web Sites/Applications]] || users || style="text-align: left;" | Web pages using HTML/XHTML, CSS, JS, and various server-side programming languages (SSI, PHP, Perl, Python, Ruby…), and statistics (analytics data/reports) |- | colspan="2" | [[Services/XMPPHosting|XMPP Domains]] || users || style="text-align: left;" | XMPP Node for a custom domain |- | colspan="2" | [[Services/Shell|Shell]] || trusted || style="text-align: left;" | Useful for website administration, development, run custom scripts, persistent applications for text-mode geeks… |- | rowspan="2" | Network || colspan="2" | [[Services/IPv6-Broker|IPv6 tunnels]] || users || style="text-align: left;" | Access to the IPv6 world through an IPv4 connection |- | colspan="2" | [[Services/NSTX|NSTX]] || users || style="text-align: left;" | Access to the Internet through a restricted WIFI connection (via an IP over DNS tunnel) |} == TODO == * in Services/Wiki: https://wiki.duckcorp.org/ * in Services/Shell: link to SAFT * in Services/XMPP: chitchat * in Services/WebFeeds: https://gossip.duckcorp.org/ * in Services/Projects: https://projects.duckcorp.org/ * in Services/VCS: https://rcs.duckcorp.org/ … d9f8b89773c823ff476ae8f7c09609c464321ec2 347 345 2012-01-27T23:30:11Z Duck 2 /* TODO */ wikitext text/x-wiki Here is a short overview of the services provided by DuckCorp. Our services are supervised and important data are [[Services/Backup|saved regularly]]. {{warning}} [[Services/Security|Notes about security !]] {| class="wikitable" style="text-align: center; width: 100%;" |+ Available Services |- ! Category !! colspan="2" | Service !! Access !! Description |- | rowspan="7" | Communication || rowspan="2" | Mail || [[Services/Mail|eMails]] || users || style="text-align: left;" | Mail boxes with anti-spam/anti-virus, filtering…, or mail redirections |- | [[Services/ML|Mailing-Lists]] || users || style="text-align: left;" | Distribution lists for mails |- | rowspan="3" | IRC || [[Services/IRC|IRC Network]] || public || style="text-align: left;" | MilkyPond Chat Network using a dedicated software or a Web-interface |- | [[Services/IRC-Bouncer|IRC Bouncer]] || users || style="text-align: left;" | IRC proxy (IRC server relaying IRC communications, keeping connections open and remembering logs) |- | [[Services/IRC-IM-GW|IRC to IM gateway]] || users || style="text-align: left;" | Communication to multiple instant messaging networks through a unified IRC-like interface |- | colspan="2" | [[Services/XMPP|XMPP (Jabber)]] || users || style="text-align: left;" | Global Chat Network (inter-communication between many [[wikipedia:Xmpp#History|well-known public IM services]]) |- | colspan="2" | [[Services/Tribioune|Triboune Libre]] || public || style="text-align: left;" | MilkyPond Web-chat system inspired by [http://linuxfr.org/board the famous one] on [http://linuxfr.org/ Linuxfr.org] |- | rowspan="5" | Sharing || colspan="2" | [[Services/Gallery|Media Gallery]] || public/users || style="text-align: left;" | Photo and video gallery |- | colspan="2" | [[Services/Wiki|Wiki]] || public/users || style="text-align: left;" | Technical knowledge, useful tips… |- | rowspan="3" | Generic || [[Services/FTP|File Repository]] || public/users || style="text-align: left;" | Generic file sharing system (using FTP) |- | [[Services/WebFileExchange|Downloads Links]] || public/users || style="text-align: left;" | Web-based generic file sharing |- | [[Services/SAFT|Shell Transfer]] || trusted || style="text-align: left;" | File transfer system using the SAFT protocol (shell access needed) |- | rowspan="3" | Utilities || colspan="2" | [[Services/WebFeeds|News WebReader]] || users || style="text-align: left;" | News feeds reader through a web interface |- | colspan="2" | [[Services/NTP|Time Server]] || public || style="text-align: left;" | System used to automatically setup time on your machines (and also part of the [http://www.pool.ntp.org/en/ NTP Pool Project]) |- | colspan="2" | [[Services/Dico|Dictionary Server]] || public || style="text-align: left;" | Words searching system via a dedicated software (using the DICT protocol) or a Web-interface |- | rowspan="6" | Development || colspan="2" | [[Services/Projects|Project Management & Issue Tracking]] || public/users || style="text-align: left;" | |- | colspan="2" | [[Services/CodeReview|Code Review]] || public/users || style="text-align: left;" | |- | colspan="2" | [[Services/VCS|VCS]] || public/users || style="text-align: left;" | Code/configuration versioning tools (Git, SVN, Baz, Bzr…) |- | rowspan="2" | Databases || [[Services/SQL|SQL]] || users || style="text-align: left;" | SQL server (PostgreSQL or MySQL) |- | [[Services/LDAP|LDAP]] || users || style="text-align: left;" | LDAP server (OpenLDAP) |- | colspan="2" | [[Services/SoftwareRepository|Software Repository]] || public/users || style="text-align: left;" | Software repository, to provide custom packages (think Debian debs) or installation media (thinks DVDs) |- | rowspan="6" | Hosting || colspan="2" | [[Services/DNS|DNS]] || users || style="text-align: left;" | Domain Name System (NS1/NS2, DNSSEC…) |- | rowspan="2" | Mail || [[Services/MailHosting|Mail Domains]] || users || style="text-align: left;" | Mail hosting (MX1/MX2) |- | [[Services/MLHosting|Mailing-Lists]] || users || style="text-align: left;" | Distribution lists for mail domains |- | colspan="2" | [[Services/WebHosting|Web Sites/Applications]] || users || style="text-align: left;" | Web pages using HTML/XHTML, CSS, JS, and various server-side programming languages (SSI, PHP, Perl, Python, Ruby…), and statistics (analytics data/reports) |- | colspan="2" | [[Services/XMPPHosting|XMPP Domains]] || users || style="text-align: left;" | XMPP Node for a custom domain |- | colspan="2" | [[Services/Shell|Shell]] || trusted || style="text-align: left;" | Useful for website administration, development, run custom scripts, persistent applications for text-mode geeks… |- | rowspan="2" | Network || colspan="2" | [[Services/IPv6-Broker|IPv6 tunnels]] || users || style="text-align: left;" | Access to the IPv6 world through an IPv4 connection |- | colspan="2" | [[Services/NSTX|NSTX]] || users || style="text-align: left;" | Access to the Internet through a restricted WIFI connection (via an IP over DNS tunnel) |} == TODO == * in Services/Wiki: https://wiki.duckcorp.org/ * in Services/Shell: link to SAFT * in Services/XMPP: chitchat * in Services/WebFeeds: https://gossip.duckcorp.org/ * in Services/Projects: https://projects.duckcorp.org/ * in Services/VCS: https://rcs.duckcorp.org/ * Radio … f576dbf368e9b48f47296466b68eeff750f91932 351 347 2012-01-29T00:31:15Z Duck 2 wikitext text/x-wiki Here is a short overview of the services provided by DuckCorp. Our services are supervised and important data are [[Services/Backup|saved regularly]]. {{warning}} [[Services/Security|Notes about security !]] {| class="wikitable" style="text-align: center; width: 100%;" |+ Available Services |- ! Category !! colspan="2" | Service !! Access !! Description |- | rowspan="7" | Communication || rowspan="2" | Mail || [[Services/Mail|eMails]] || users || style="text-align: left;" | Mail boxes with anti-spam/anti-virus, filtering…, or mail redirections |- | [[Services/ML|Mailing-Lists]] || users || style="text-align: left;" | Distribution lists for mails |- | rowspan="3" | IRC || [[Services/IRC|IRC Network]] || public || style="text-align: left;" | MilkyPond Chat Network using a dedicated software or a Web-interface |- | [[Services/IRC-Bouncer|IRC Bouncer]] || users || style="text-align: left;" | IRC proxy (IRC server relaying IRC communications, keeping connections open and remembering logs) |- | [[Services/IRC-IM-GW|IRC to IM gateway]] || users || style="text-align: left;" | Communication to multiple instant messaging networks through a unified IRC-like interface |- | colspan="2" | [[Services/XMPP|XMPP (Jabber)]] || users || style="text-align: left;" | Global Chat Network (inter-communication between many [[wikipedia:Xmpp#History|well-known public IM services]]) |- | colspan="2" | [[Services/Tribioune|Triboune Libre]] || public || style="text-align: left;" | MilkyPond Web-chat system inspired by [http://linuxfr.org/board the famous one] on [http://linuxfr.org/ Linuxfr.org] |- | rowspan="5" | Sharing || colspan="2" | [[Services/Gallery|Media Gallery]] || public/users || style="text-align: left;" | Photo and video gallery |- | colspan="2" | [[Services/Wiki|Wiki]] || public/users || style="text-align: left;" | Technical knowledge, useful tips… |- | rowspan="3" | Generic || [[Services/FTP|File Repository]] || public/users || style="text-align: left;" | Generic file sharing system (using FTP) |- | [[Services/WebFileExchange|Downloads Links]] || public/users || style="text-align: left;" | Web-based generic file sharing |- | [[Services/SAFT|Shell Transfer]] || trusted || style="text-align: left;" | File transfer system using the SAFT protocol (shell access needed) |- | rowspan="3" | Utilities || colspan="2" | [[Services/WebFeeds|News WebReader]] || users || style="text-align: left;" | News feeds reader through a web interface |- | colspan="2" | [[Services/NTP|Time Server]] || public || style="text-align: left;" | System used to automatically setup time on your machines |- | colspan="2" | [[Services/Dico|Dictionary Server]] || public || style="text-align: left;" | Words searching system via a dedicated software (using the DICT protocol) or a Web-interface |- | rowspan="6" | Development || colspan="2" | [[Services/Projects|Project Management & Issue Tracking]] || public/users || style="text-align: left;" | |- | colspan="2" | [[Services/CodeReview|Code Review]] || public/users || style="text-align: left;" | |- | colspan="2" | [[Services/VCS|VCS]] || public/users || style="text-align: left;" | Code/configuration versioning tools (Git, SVN, Baz, Bzr…) |- | rowspan="2" | Databases || [[Services/SQL|SQL]] || users || style="text-align: left;" | SQL server (PostgreSQL or MySQL) |- | [[Services/LDAP|LDAP]] || users || style="text-align: left;" | LDAP server (OpenLDAP) |- | colspan="2" | [[Services/SoftwareRepository|Software Repository]] || public/users || style="text-align: left;" | Software repository, to provide custom packages (think Debian debs) or installation media (thinks DVDs) |- | rowspan="6" | Hosting || colspan="2" | [[Services/DNS|DNS]] || users || style="text-align: left;" | Domain Name System (NS1/NS2, DNSSEC…) |- | rowspan="2" | Mail || [[Services/MailHosting|Mail Domains]] || users || style="text-align: left;" | Mail hosting (MX1/MX2) |- | [[Services/MLHosting|Mailing-Lists]] || users || style="text-align: left;" | Distribution lists for mail domains |- | colspan="2" | [[Services/WebHosting|Web Sites/Applications]] || users || style="text-align: left;" | Web pages using HTML/XHTML, CSS, JS, and various server-side programming languages (SSI, PHP, Perl, Python, Ruby…), and statistics (analytics data/reports) |- | colspan="2" | [[Services/XMPPHosting|XMPP Domains]] || users || style="text-align: left;" | XMPP Node for a custom domain |- | colspan="2" | [[Services/Shell|Shell]] || trusted || style="text-align: left;" | Useful for website administration, development, run custom scripts, persistent applications for text-mode geeks… |- | rowspan="2" | Network || colspan="2" | [[Services/IPv6-Broker|IPv6 tunnels]] || users || style="text-align: left;" | Access to the IPv6 world through an IPv4 connection |- | colspan="2" | [[Services/NSTX|NSTX]] || users || style="text-align: left;" | Access to the Internet through a restricted WIFI connection (via an IP over DNS tunnel) |} == TODO == * in Services/Wiki: https://wiki.duckcorp.org/ * in Services/Shell: link to SAFT * in Services/XMPP: chitchat * in Services/WebFeeds: https://gossip.duckcorp.org/ * in Services/Projects: https://projects.duckcorp.org/ * in Services/VCS: https://rcs.duckcorp.org/ * Radio … 299d4ecc7e05764e38160fc91fbb10cb066fed5e 0 64 348 2012-01-28T23:59:33Z Duck 2 Created page with "{{Template:Service | description = This service allows to keep your machine on time, by being synchronized with a remote time server. The later may itself be synchronized with a …" wikitext text/x-wiki {{Template:Service | description = This service allows to keep your machine on time, by being synchronized with a remote time server. The later may itself be synchronized with a better time server and so on. The last one (stratum 1) uses an accurate source of time (stratum 0), like an atomic or GPS clock, and distribute it over the Internet. | prerequisite = | account = | ipv6 = true | security_notes = There is no big security concern except you can't be sure you're talking to our NTP server (no DTLS support). }} == Access == You need a NTP software to synchronize your machine. On Debian you can install it easily using: apt-get install ntp You then need to edit the configuration file ''/etc/ntp.conf'' to add this line: server ntp.duckcorp.org iburst prefer And then restart the service: service ntp restart == Documentation == * generic documentation on [[wikipedia:Network_Time_Protocol]] == Technical Details == This service is made using: * [http://www.ntp.org/ NTP daemon] 6637878e550924bfce5b4e68420f06f2dc77e6a7 349 348 2012-01-28T23:59:57Z Duck 2 wikitext text/x-wiki {{Template:Service | description = This service allows to keep your machine on time, by being synchronized with a remote time server. The later may itself be synchronized with a better time server and so on. The last one (stratum 1) uses an accurate source of time (stratum 0), like an atomic or GPS clock, and distribute it over the Internet. | prerequisite = | account = | ipv6 = true | security_notes = There is no big security concern except you can't be sure you're talking to our NTP server (no DTLS support). }} == Access == You need a NTP software to synchronize your machine. On Debian you can install it easily using: apt-get install ntp You then need to edit the configuration file ''/etc/ntp.conf'' to add this line: server ntp.duckcorp.org iburst prefer And then restart the service: service ntp restart == Documentation == * generic documentation on [[wikipedia:Network_Time_Protocol|NTP]] == Technical Details == This service is made using: * [http://www.ntp.org/ NTP daemon] 60d5eb443fa172cc962e62f8bb30a5952270cae8 350 349 2012-01-29T00:30:57Z Duck 2 wikitext text/x-wiki {{Template:Service | description = This service allows to keep your machine on time, by being synchronized with a remote time server. The later may itself be synchronized with a better time server and so on. The last one (stratum 1) uses an accurate source of time (stratum 0), like an atomic or GPS clock, and distribute it over the Internet. | prerequisite = | account = | ipv6 = true | security_notes = There is no big security concern except you can't be sure you're talking to our NTP server (no DTLS support). }} == Access == You need a NTP software to synchronize your machine. On Debian you can install it easily using: apt-get install ntp You then need to edit the configuration file ''/etc/ntp.conf'' to add this line: server ntp.duckcorp.org iburst prefer And then restart the service: service ntp restart == NTP Pool == Our server is also part of the [http://www.pool.ntp.org/en/ NTP Pool Project]. If you use servers named like ''*.pool.ntp.org'', then you may use our server sometimes. It is often used by vendors and GNU/* distributions. == Documentation == * generic documentation on [[wikipedia:Network_Time_Protocol|NTP]] == Technical Details == This service is made using: * [http://www.ntp.org/ NTP daemon] 8f193fdffddf9cbcaaf94141a40871bfe3dff04d 0 49 359 358 2012-01-30T19:36:18Z Duck 2 /* Antivirus and Antispam */ wikitext text/x-wiki {{Template:Service | description = Available services: * multiple email addresses (mailboxes+aliases or redirections) based on the ''milkypond.org'' (or maybe ''duckcorp.org'') domain * roaming accounts to be able to send emails wherever you are If you want email addresses using you own domain(s), see the [[Services/MailHosting|mail hosting service]]. | prerequisite = | account = global-reg | ipv6 = true | security_notes = Access to the mail services are fully secured, and to your data, nevertheless most mail exchange on the Internet are not. Complete security can be achieved using signed and encrypted mail (see [[wikipedia:Pretty_Good_Privacy|OpenPGP]] and [[wikipedia:S/MIME|S/MIME]]) }} == Access == === Using a Mail Reader === You can retrieve your mails, in case of a real mailbox, using either: * IMAP+TLS (TCP 143) / IMAPS (TCP 993) on imap.duckcorp.org * or POP3+TLS (TCP 110) / POP3S (TCP 995) on pop.duckcorp.org The IMAP protocol is recommended over POP3, as it provides many interesting features. If you want to download all your mails absolutely at home, loosing the ability to read your mail from anywhere on the planet, you can do that with IMAP too (look at your mail client settings). You can use our servers to send mails out too via smtp.duckcorp.org using: * SMTP+TLS (TCP 25) / SMTPS (TCP 465) * and SASL authentication === Using a Web Interface === Several [https://webmail.duckcorp.org/ webmail interfaces] are available. == Antivirus and Antispam == Mails stored on our server are checked upon arrival for viruses and SPAMs. Mail redirected to a third party mailbox are not, not to mess with the strategy of the the final destination (which could arm learning greatly). Mails being viruses are suppressed automatically upon arrival. Once in a week, an extra antivirus check is done on all hosted mailboxes, to remove viruses not detected at the time it arrived (our antivirus database is updated daily), so you may see such mail disappear from your mailbox, don't fear. SPAMs are more difficult to detect, and it is an error-prone process, so we chose to use a learning software instead of using a global database. On the bright side of things, you would never loose mails and the software should be able to learn what is a SPAM from '''your''' point of view (which has proved to differ slightly between our users), but on the grey side you will have to teach him regularly to avoid errors. When your account is created, it acts like an empty headed body letting everything through, but after a few weeks of teaching it is able to recognize most of your habits and block a lot of annoying SPAM. === Web Interface === The web interface is an easy way to view your mail history, changes your settings, and more. It is available using this URL: https://spamfilter.duckcorp.org/ ==== User Settings ==== You can yourself setup a few parameters in the ''Preferences'' page of the [https://spamfilter.duckcorp.org/ web interface], mostly: * how the system should train: ** TEFT (''On every new message scanned by the filter''): useful to learn very quickly especially on a new mailbox or when you've got tons of spam on your addresses, but you need to train it regulary (daily is better) or it will learn wrong (very quickly too !) ** TOE (''Only when the filter makes a mistake''): slow learning, but if you don't have time for training very often or go on long holidays without internet access this mode will give you a stable behavior ** TUM (''Only with new data or if the filter makes a mistake''): trade-off between the two previous modes, learn quite fast and not too demanding, adapts better to new SPAMs then TOE * filter sensitivity: you can ask the system to be more or less aggressive * message handling: see [[#Delivery Mode|delivery mode]] below * ''Disable DSPAM filtering'': you may switch off filtering at your own risk We strongly recommend using TEFT with daily training for a few weeks then switching to TUM. If you need to go away for a long time, switching to TOE is recommended. Using the quarantine feature is also a safe choice, as the web interface is quite easy to use. === Delivery Mode === ==== Quarantine ==== With the ''message handling'' setting set to ''Quarantine the message'' (see [[#User Settings|user preferences]]), then your SPAMs will not go into your mailbox but stay in this stagging area. These mails are kept by the system until you decide their fate. Through the ''Quarantine'' page of the web interface, you can list these mails and: * free legitimate mails wrongly considered as SPAM by the system * delete real SPAMs if the system was right about them (freeing useful space) In this mode, you need to flush your quarantine once in a while. ==== Delivered with Special Header ==== With the ''message handling'' setting set to ''Deliver the message normally with a X-DSPAM-Result header'', mails are delivered with a special field in your mail headers (not always visible depending on your mail client and its configuration); this is quite handy if you prefer SPAMs arranged in a specific folder. {{todo}} ==== Delivered with Modified Subject (not recommended) ==== With the ''message handling'' setting set to ''Tag the Subject header with'', mails are delivered with a modified title (which is a tad ugly). {{todo}} === Retraining === Teaching the system what is SPAM and HAM (non-SPAM) is called ''retraining''. ==== Retraining using the Special ''Junk'' Folder (recommended) ==== {{warning}} This feature is to be available soon! ==== Retraining via Web Interface ==== If you are using the ''quarantine'', then freed mails will automatically be retrained as HAM. Use the [https://spamfilter.duckcorp.org/ web interface] to retrain from errors in the ''History'' page. ==== Retraining via Mail ==== Resend SPAMs to [mailto:dc-spam@duckcorp.org dc-spam@duckcorp.org] and HAM (non-SPAM) to [mailto:dc-ham@duckcorp.org dc-ham@duckcorp.org]. {{warning}} PLEASE TAKE CARE to use the ''resend'' function of your mailer and never use ''forward'', which would result in '''yourself''' being considered as SPAN or HAM. == Mail Filtering == With your favourite mail client, you can probably filter your mails in proper folders already. Nevertheless, this can be a annoying operation: * blocking you mail client for a long time if you have to process plenty of mails * downloading each mail information, and sometimes content (depending on your filters), is lenghty too, and cost much bandwidth * syncing filters accross your machines (home desktop, laptop, office machine…) is a pain in the ass * processing only when you're online prevents triggering actions in a timely manner (automatic redirect, vacation messages…), and running a machine 24/7 with a mail client polling new mails every 30s is not a solution We provide a much better way to do this using the [[wikipedia:Sieve_(mail_filtering_language)|SIEVE]] filters. Shortly, SIEVE is a language dedicated to expressing mail filters. Our server is able to process your mails according to these filters as soon as they arrive. You then don't have to care about them anymore, and may use light mail clients or webmails when you're not on your machine with your favourite software. To push your filters on the server, a dedicated protocol exists: : MANAGESIEVE (TCP 4190) on sieve.duckcorp.org Several softwares support managing SIEVE rules: * Icedove/Thunderbird using the SIEVE extension (in xul-ext-sieve Debian package) provides a rules editor * Horde (Ingo) provides an easy to use web interface * Squirrelmail with the Avelsieve extension provides an easy to use web interface * Roundcube with an extension provides an easy to use web interface * sieve-connect provides a CLI to upload/download/activate your rules files (tell us if you know more software supporting this feature) You can read more info about SIEVE here: * supported SIEVE features on our server: http://pigeonhole.dovecot.org/ * http://www.fastmail.fm/docs/sieve/ * http://sieve.info/ == Fetching eMails from an External Mailbox == {{todo}} == Shared/Public Folders == You may need to share mails or messages with friends or people you do stuff with (in a project or association). Depending on your needs, two solutions are possible: * share some of your own private folders, thus called ''shared folders'' * manage a special folder hierarchy, called ''public folders'' (even if they may not be accessible to everyone) Through IMAP, or our webmails internally using IMAP, it is possible to partition the folder hierarchy into ''namespaces''. Traditionally you are using the root namespace for your private folders. Additionnal namespaces can be created and will appear among your own folders or separate, depending on your mail client's choice of representation. To avoid name clashes, we decided to prefix all additionnal namespace names with a '''#'''. Since 2011-05-14, the following extra namespaces are created and reserved: * #Shared, containing all folders other users decided to share with you * #MilkyPond, containing public MP/DC information mailboxes you may subscribe at will Using IMAP, it is possible to setup rights (read only, write allowed…) to your own folders in order to share them with other users, or group of users. Public folders are owned by noone, and must be created by DC administrators ; if you need one, send us a request and we may be able to create it and delegate administration to your care (namespace name is subject to approval). Once created, public folders can be administered like shared folders. Client mail softwares support: * Horde: support namespaces, shared folders configurable via ''Options->Share Folders'' menu but no ACLs for public folders * Icedove/Thunderbird: support namespaces, shared and public folders configurable via folder selection and ''Tools->Imap-ACL'' menu action Most other softwares have namespace support only, so you should be able to use shared/public folders you have rights on but not configure them yourself (tell us if you know more software supporting this feature) == Limitations == === Maximum Mail Size === Mail you send or receive are limited to '''10MB'''. If you need to transmit much bigger data, then a mail transport is not appropriate, you'd better use a file sharing method instead. === Quotas === Even if it would be nice to live without it, we had to establish quotas to force people sort their mails out once in a while and delete useless things instead of leaving an ever-growing mess behind. The default quota is '''512MB''' which is not that big but should match needs of most users. This said, you may ask us for more and there's no reason we would refuse a reasonable demand. == Technical Details == This service is made using: * [http://www.postfix.org/ Postfix] * [http://dovecot.org/ Dovecot] * [http://dspam.sourceforge.net DSPAM] * [http://johannes.sipsolutions.net/Projects/dovecot-antispam dovecot-antispam] * [https://projects.duckcorp.org/projects/spoolinger Spoolinger] * [http://www.horde.org/ Horde] * [http://www.squirrelmail.org/ SquirrelMail] * [http://www.roundcube.net/ RoundCube] fe19af84895ea3bbbd3fb41f0662eb04f4ad5727 360 359 2012-01-30T23:03:15Z Duck 2 /* Delivery Mode */ wikitext text/x-wiki {{Template:Service | description = Available services: * multiple email addresses (mailboxes+aliases or redirections) based on the ''milkypond.org'' (or maybe ''duckcorp.org'') domain * roaming accounts to be able to send emails wherever you are If you want email addresses using you own domain(s), see the [[Services/MailHosting|mail hosting service]]. | prerequisite = | account = global-reg | ipv6 = true | security_notes = Access to the mail services are fully secured, and to your data, nevertheless most mail exchange on the Internet are not. Complete security can be achieved using signed and encrypted mail (see [[wikipedia:Pretty_Good_Privacy|OpenPGP]] and [[wikipedia:S/MIME|S/MIME]]) }} == Access == === Using a Mail Reader === You can retrieve your mails, in case of a real mailbox, using either: * IMAP+TLS (TCP 143) / IMAPS (TCP 993) on imap.duckcorp.org * or POP3+TLS (TCP 110) / POP3S (TCP 995) on pop.duckcorp.org The IMAP protocol is recommended over POP3, as it provides many interesting features. If you want to download all your mails absolutely at home, loosing the ability to read your mail from anywhere on the planet, you can do that with IMAP too (look at your mail client settings). You can use our servers to send mails out too via smtp.duckcorp.org using: * SMTP+TLS (TCP 25) / SMTPS (TCP 465) * and SASL authentication === Using a Web Interface === Several [https://webmail.duckcorp.org/ webmail interfaces] are available. == Antivirus and Antispam == Mails stored on our server are checked upon arrival for viruses and SPAMs. Mail redirected to a third party mailbox are not, not to mess with the strategy of the the final destination (which could arm learning greatly). Mails being viruses are suppressed automatically upon arrival. Once in a week, an extra antivirus check is done on all hosted mailboxes, to remove viruses not detected at the time it arrived (our antivirus database is updated daily), so you may see such mail disappear from your mailbox, don't fear. SPAMs are more difficult to detect, and it is an error-prone process, so we chose to use a learning software instead of using a global database. On the bright side of things, you would never loose mails and the software should be able to learn what is a SPAM from '''your''' point of view (which has proved to differ slightly between our users), but on the grey side you will have to teach him regularly to avoid errors. When your account is created, it acts like an empty headed body letting everything through, but after a few weeks of teaching it is able to recognize most of your habits and block a lot of annoying SPAM. === Web Interface === The web interface is an easy way to view your mail history, changes your settings, and more. It is available using this URL: https://spamfilter.duckcorp.org/ ==== User Settings ==== You can yourself setup a few parameters in the ''Preferences'' page of the [https://spamfilter.duckcorp.org/ web interface], mostly: * how the system should train: ** TEFT (''On every new message scanned by the filter''): useful to learn very quickly especially on a new mailbox or when you've got tons of spam on your addresses, but you need to train it regulary (daily is better) or it will learn wrong (very quickly too !) ** TOE (''Only when the filter makes a mistake''): slow learning, but if you don't have time for training very often or go on long holidays without internet access this mode will give you a stable behavior ** TUM (''Only with new data or if the filter makes a mistake''): trade-off between the two previous modes, learn quite fast and not too demanding, adapts better to new SPAMs then TOE * filter sensitivity: you can ask the system to be more or less aggressive * message handling: see [[#Delivery Mode|delivery mode]] below * ''Disable DSPAM filtering'': you may switch off filtering at your own risk We strongly recommend using TEFT with daily training for a few weeks then switching to TUM. If you need to go away for a long time, switching to TOE is recommended. Using the quarantine feature is also a safe choice, as the web interface is quite easy to use. === Delivery Mode === ==== Quarantine ==== With the ''message handling'' setting set to ''Quarantine the message'' (see [[#User Settings|user preferences]]), then your SPAMs will not go into your mailbox but stay in this stagging area. These mails are kept by the system until you decide their fate. Through the ''Quarantine'' page of the web interface, you can list these mails and: * free legitimate mails wrongly considered as SPAM by the system * delete real SPAMs if the system was right about them (freeing useful space) In this mode, you need to flush your quarantine once in a while. ==== Delivered with Special Header ==== With the ''message handling'' setting set to ''Deliver the message normally with a X-DSPAM-Result header'', mails are delivered normally, but with a special field added to your mail headers (not always visible depending on your mail client and its configuration). This is quite handy if you prefer SPAMs arranged in a specific folder. You may use then the provided [#Mail Filtering |filtering system] to sort them properly, or configure your eMail client. ==== Delivered with Modified Subject (not recommended) ==== With the ''message handling'' setting set to ''Tag the Subject header with'', mails are delivered normally, but with a modified title to alert you this is a SPAM (which is a tad ugly). This mode is really not clean and not recommended, but it exist for historical purposes, so you might still use it if you really wish to. === Retraining === Teaching the system what is SPAM and HAM (non-SPAM) is called ''retraining''. ==== Retraining using the Special ''Junk'' Folder (recommended) ==== {{warning}} This feature is to be available soon! ==== Retraining via Web Interface ==== If you are using the ''quarantine'', then freed mails will automatically be retrained as HAM. Use the [https://spamfilter.duckcorp.org/ web interface] to retrain from errors in the ''History'' page. ==== Retraining via Mail ==== Resend SPAMs to [mailto:dc-spam@duckcorp.org dc-spam@duckcorp.org] and HAM (non-SPAM) to [mailto:dc-ham@duckcorp.org dc-ham@duckcorp.org]. {{warning}} PLEASE TAKE CARE to use the ''resend'' function of your mailer and never use ''forward'', which would result in '''yourself''' being considered as SPAN or HAM. == Mail Filtering == With your favourite mail client, you can probably filter your mails in proper folders already. Nevertheless, this can be a annoying operation: * blocking you mail client for a long time if you have to process plenty of mails * downloading each mail information, and sometimes content (depending on your filters), is lenghty too, and cost much bandwidth * syncing filters accross your machines (home desktop, laptop, office machine…) is a pain in the ass * processing only when you're online prevents triggering actions in a timely manner (automatic redirect, vacation messages…), and running a machine 24/7 with a mail client polling new mails every 30s is not a solution We provide a much better way to do this using the [[wikipedia:Sieve_(mail_filtering_language)|SIEVE]] filters. Shortly, SIEVE is a language dedicated to expressing mail filters. Our server is able to process your mails according to these filters as soon as they arrive. You then don't have to care about them anymore, and may use light mail clients or webmails when you're not on your machine with your favourite software. To push your filters on the server, a dedicated protocol exists: : MANAGESIEVE (TCP 4190) on sieve.duckcorp.org Several softwares support managing SIEVE rules: * Icedove/Thunderbird using the SIEVE extension (in xul-ext-sieve Debian package) provides a rules editor * Horde (Ingo) provides an easy to use web interface * Squirrelmail with the Avelsieve extension provides an easy to use web interface * Roundcube with an extension provides an easy to use web interface * sieve-connect provides a CLI to upload/download/activate your rules files (tell us if you know more software supporting this feature) You can read more info about SIEVE here: * supported SIEVE features on our server: http://pigeonhole.dovecot.org/ * http://www.fastmail.fm/docs/sieve/ * http://sieve.info/ == Fetching eMails from an External Mailbox == {{todo}} == Shared/Public Folders == You may need to share mails or messages with friends or people you do stuff with (in a project or association). Depending on your needs, two solutions are possible: * share some of your own private folders, thus called ''shared folders'' * manage a special folder hierarchy, called ''public folders'' (even if they may not be accessible to everyone) Through IMAP, or our webmails internally using IMAP, it is possible to partition the folder hierarchy into ''namespaces''. Traditionally you are using the root namespace for your private folders. Additionnal namespaces can be created and will appear among your own folders or separate, depending on your mail client's choice of representation. To avoid name clashes, we decided to prefix all additionnal namespace names with a '''#'''. Since 2011-05-14, the following extra namespaces are created and reserved: * #Shared, containing all folders other users decided to share with you * #MilkyPond, containing public MP/DC information mailboxes you may subscribe at will Using IMAP, it is possible to setup rights (read only, write allowed…) to your own folders in order to share them with other users, or group of users. Public folders are owned by noone, and must be created by DC administrators ; if you need one, send us a request and we may be able to create it and delegate administration to your care (namespace name is subject to approval). Once created, public folders can be administered like shared folders. Client mail softwares support: * Horde: support namespaces, shared folders configurable via ''Options->Share Folders'' menu but no ACLs for public folders * Icedove/Thunderbird: support namespaces, shared and public folders configurable via folder selection and ''Tools->Imap-ACL'' menu action Most other softwares have namespace support only, so you should be able to use shared/public folders you have rights on but not configure them yourself (tell us if you know more software supporting this feature) == Limitations == === Maximum Mail Size === Mail you send or receive are limited to '''10MB'''. If you need to transmit much bigger data, then a mail transport is not appropriate, you'd better use a file sharing method instead. === Quotas === Even if it would be nice to live without it, we had to establish quotas to force people sort their mails out once in a while and delete useless things instead of leaving an ever-growing mess behind. The default quota is '''512MB''' which is not that big but should match needs of most users. This said, you may ask us for more and there's no reason we would refuse a reasonable demand. == Technical Details == This service is made using: * [http://www.postfix.org/ Postfix] * [http://dovecot.org/ Dovecot] * [http://dspam.sourceforge.net DSPAM] * [http://johannes.sipsolutions.net/Projects/dovecot-antispam dovecot-antispam] * [https://projects.duckcorp.org/projects/spoolinger Spoolinger] * [http://www.horde.org/ Horde] * [http://www.squirrelmail.org/ SquirrelMail] * [http://www.roundcube.net/ RoundCube] c057041a4f6cae3c4429e8c6f234cf2510fb2dbf 361 360 2012-01-30T23:17:33Z Duck 2 /* Retraining via Web Interface */ wikitext text/x-wiki {{Template:Service | description = Available services: * multiple email addresses (mailboxes+aliases or redirections) based on the ''milkypond.org'' (or maybe ''duckcorp.org'') domain * roaming accounts to be able to send emails wherever you are If you want email addresses using you own domain(s), see the [[Services/MailHosting|mail hosting service]]. | prerequisite = | account = global-reg | ipv6 = true | security_notes = Access to the mail services are fully secured, and to your data, nevertheless most mail exchange on the Internet are not. Complete security can be achieved using signed and encrypted mail (see [[wikipedia:Pretty_Good_Privacy|OpenPGP]] and [[wikipedia:S/MIME|S/MIME]]) }} == Access == === Using a Mail Reader === You can retrieve your mails, in case of a real mailbox, using either: * IMAP+TLS (TCP 143) / IMAPS (TCP 993) on imap.duckcorp.org * or POP3+TLS (TCP 110) / POP3S (TCP 995) on pop.duckcorp.org The IMAP protocol is recommended over POP3, as it provides many interesting features. If you want to download all your mails absolutely at home, loosing the ability to read your mail from anywhere on the planet, you can do that with IMAP too (look at your mail client settings). You can use our servers to send mails out too via smtp.duckcorp.org using: * SMTP+TLS (TCP 25) / SMTPS (TCP 465) * and SASL authentication === Using a Web Interface === Several [https://webmail.duckcorp.org/ webmail interfaces] are available. == Antivirus and Antispam == Mails stored on our server are checked upon arrival for viruses and SPAMs. Mail redirected to a third party mailbox are not, not to mess with the strategy of the the final destination (which could arm learning greatly). Mails being viruses are suppressed automatically upon arrival. Once in a week, an extra antivirus check is done on all hosted mailboxes, to remove viruses not detected at the time it arrived (our antivirus database is updated daily), so you may see such mail disappear from your mailbox, don't fear. SPAMs are more difficult to detect, and it is an error-prone process, so we chose to use a learning software instead of using a global database. On the bright side of things, you would never loose mails and the software should be able to learn what is a SPAM from '''your''' point of view (which has proved to differ slightly between our users), but on the grey side you will have to teach him regularly to avoid errors. When your account is created, it acts like an empty headed body letting everything through, but after a few weeks of teaching it is able to recognize most of your habits and block a lot of annoying SPAM. === Web Interface === The web interface is an easy way to view your mail history, changes your settings, and more. It is available using this URL: https://spamfilter.duckcorp.org/ ==== User Settings ==== You can yourself setup a few parameters in the ''Preferences'' page of the [https://spamfilter.duckcorp.org/ web interface], mostly: * how the system should train: ** TEFT (''On every new message scanned by the filter''): useful to learn very quickly especially on a new mailbox or when you've got tons of spam on your addresses, but you need to train it regulary (daily is better) or it will learn wrong (very quickly too !) ** TOE (''Only when the filter makes a mistake''): slow learning, but if you don't have time for training very often or go on long holidays without internet access this mode will give you a stable behavior ** TUM (''Only with new data or if the filter makes a mistake''): trade-off between the two previous modes, learn quite fast and not too demanding, adapts better to new SPAMs then TOE * filter sensitivity: you can ask the system to be more or less aggressive * message handling: see [[#Delivery Mode|delivery mode]] below * ''Disable DSPAM filtering'': you may switch off filtering at your own risk We strongly recommend using TEFT with daily training for a few weeks then switching to TUM. If you need to go away for a long time, switching to TOE is recommended. Using the quarantine feature is also a safe choice, as the web interface is quite easy to use. === Delivery Mode === ==== Quarantine ==== With the ''message handling'' setting set to ''Quarantine the message'' (see [[#User Settings|user preferences]]), then your SPAMs will not go into your mailbox but stay in this stagging area. These mails are kept by the system until you decide their fate. Through the ''Quarantine'' page of the web interface, you can list these mails and: * free legitimate mails wrongly considered as SPAM by the system * delete real SPAMs if the system was right about them (freeing useful space) In this mode, you need to flush your quarantine once in a while. ==== Delivered with Special Header ==== With the ''message handling'' setting set to ''Deliver the message normally with a X-DSPAM-Result header'', mails are delivered normally, but with a special field added to your mail headers (not always visible depending on your mail client and its configuration). This is quite handy if you prefer SPAMs arranged in a specific folder. You may use then the provided [#Mail Filtering |filtering system] to sort them properly, or configure your eMail client. ==== Delivered with Modified Subject (not recommended) ==== With the ''message handling'' setting set to ''Tag the Subject header with'', mails are delivered normally, but with a modified title to alert you this is a SPAM (which is a tad ugly). This mode is really not clean and not recommended, but it exist for historical purposes, so you might still use it if you really wish to. === Retraining === Teaching the system what is SPAM and HAM (non-SPAM) is called ''retraining''. ==== Retraining using the Special ''Junk'' Folder (recommended) ==== {{warning}} This feature is to be available soon! ==== Retraining via Web Interface ==== Use the [https://spamfilter.duckcorp.org/ web interface] to retrain from errors in the ''History'' page. If you are using the ''quarantine'', then freed mails will automatically be retrained as HAM. ==== Retraining via Mail ==== Resend SPAMs to [mailto:dc-spam@duckcorp.org dc-spam@duckcorp.org] and HAM (non-SPAM) to [mailto:dc-ham@duckcorp.org dc-ham@duckcorp.org]. {{warning}} PLEASE TAKE CARE to use the ''resend'' function of your mailer and never use ''forward'', which would result in '''yourself''' being considered as SPAN or HAM. == Mail Filtering == With your favourite mail client, you can probably filter your mails in proper folders already. Nevertheless, this can be a annoying operation: * blocking you mail client for a long time if you have to process plenty of mails * downloading each mail information, and sometimes content (depending on your filters), is lenghty too, and cost much bandwidth * syncing filters accross your machines (home desktop, laptop, office machine…) is a pain in the ass * processing only when you're online prevents triggering actions in a timely manner (automatic redirect, vacation messages…), and running a machine 24/7 with a mail client polling new mails every 30s is not a solution We provide a much better way to do this using the [[wikipedia:Sieve_(mail_filtering_language)|SIEVE]] filters. Shortly, SIEVE is a language dedicated to expressing mail filters. Our server is able to process your mails according to these filters as soon as they arrive. You then don't have to care about them anymore, and may use light mail clients or webmails when you're not on your machine with your favourite software. To push your filters on the server, a dedicated protocol exists: : MANAGESIEVE (TCP 4190) on sieve.duckcorp.org Several softwares support managing SIEVE rules: * Icedove/Thunderbird using the SIEVE extension (in xul-ext-sieve Debian package) provides a rules editor * Horde (Ingo) provides an easy to use web interface * Squirrelmail with the Avelsieve extension provides an easy to use web interface * Roundcube with an extension provides an easy to use web interface * sieve-connect provides a CLI to upload/download/activate your rules files (tell us if you know more software supporting this feature) You can read more info about SIEVE here: * supported SIEVE features on our server: http://pigeonhole.dovecot.org/ * http://www.fastmail.fm/docs/sieve/ * http://sieve.info/ == Fetching eMails from an External Mailbox == {{todo}} == Shared/Public Folders == You may need to share mails or messages with friends or people you do stuff with (in a project or association). Depending on your needs, two solutions are possible: * share some of your own private folders, thus called ''shared folders'' * manage a special folder hierarchy, called ''public folders'' (even if they may not be accessible to everyone) Through IMAP, or our webmails internally using IMAP, it is possible to partition the folder hierarchy into ''namespaces''. Traditionally you are using the root namespace for your private folders. Additionnal namespaces can be created and will appear among your own folders or separate, depending on your mail client's choice of representation. To avoid name clashes, we decided to prefix all additionnal namespace names with a '''#'''. Since 2011-05-14, the following extra namespaces are created and reserved: * #Shared, containing all folders other users decided to share with you * #MilkyPond, containing public MP/DC information mailboxes you may subscribe at will Using IMAP, it is possible to setup rights (read only, write allowed…) to your own folders in order to share them with other users, or group of users. Public folders are owned by noone, and must be created by DC administrators ; if you need one, send us a request and we may be able to create it and delegate administration to your care (namespace name is subject to approval). Once created, public folders can be administered like shared folders. Client mail softwares support: * Horde: support namespaces, shared folders configurable via ''Options->Share Folders'' menu but no ACLs for public folders * Icedove/Thunderbird: support namespaces, shared and public folders configurable via folder selection and ''Tools->Imap-ACL'' menu action Most other softwares have namespace support only, so you should be able to use shared/public folders you have rights on but not configure them yourself (tell us if you know more software supporting this feature) == Limitations == === Maximum Mail Size === Mail you send or receive are limited to '''10MB'''. If you need to transmit much bigger data, then a mail transport is not appropriate, you'd better use a file sharing method instead. === Quotas === Even if it would be nice to live without it, we had to establish quotas to force people sort their mails out once in a while and delete useless things instead of leaving an ever-growing mess behind. The default quota is '''512MB''' which is not that big but should match needs of most users. This said, you may ask us for more and there's no reason we would refuse a reasonable demand. == Technical Details == This service is made using: * [http://www.postfix.org/ Postfix] * [http://dovecot.org/ Dovecot] * [http://dspam.sourceforge.net DSPAM] * [http://johannes.sipsolutions.net/Projects/dovecot-antispam dovecot-antispam] * [https://projects.duckcorp.org/projects/spoolinger Spoolinger] * [http://www.horde.org/ Horde] * [http://www.squirrelmail.org/ SquirrelMail] * [http://www.roundcube.net/ RoundCube] 3d229fc31a306b92573102bd4f1f278aaa6ebf5a 362 361 2012-01-30T23:40:32Z Duck 2 /* Retraining using the Special Junk Folder (recommended) */ wikitext text/x-wiki {{Template:Service | description = Available services: * multiple email addresses (mailboxes+aliases or redirections) based on the ''milkypond.org'' (or maybe ''duckcorp.org'') domain * roaming accounts to be able to send emails wherever you are If you want email addresses using you own domain(s), see the [[Services/MailHosting|mail hosting service]]. | prerequisite = | account = global-reg | ipv6 = true | security_notes = Access to the mail services are fully secured, and to your data, nevertheless most mail exchange on the Internet are not. Complete security can be achieved using signed and encrypted mail (see [[wikipedia:Pretty_Good_Privacy|OpenPGP]] and [[wikipedia:S/MIME|S/MIME]]) }} == Access == === Using a Mail Reader === You can retrieve your mails, in case of a real mailbox, using either: * IMAP+TLS (TCP 143) / IMAPS (TCP 993) on imap.duckcorp.org * or POP3+TLS (TCP 110) / POP3S (TCP 995) on pop.duckcorp.org The IMAP protocol is recommended over POP3, as it provides many interesting features. If you want to download all your mails absolutely at home, loosing the ability to read your mail from anywhere on the planet, you can do that with IMAP too (look at your mail client settings). You can use our servers to send mails out too via smtp.duckcorp.org using: * SMTP+TLS (TCP 25) / SMTPS (TCP 465) * and SASL authentication === Using a Web Interface === Several [https://webmail.duckcorp.org/ webmail interfaces] are available. == Antivirus and Antispam == Mails stored on our server are checked upon arrival for viruses and SPAMs. Mail redirected to a third party mailbox are not, not to mess with the strategy of the the final destination (which could arm learning greatly). Mails being viruses are suppressed automatically upon arrival. Once in a week, an extra antivirus check is done on all hosted mailboxes, to remove viruses not detected at the time it arrived (our antivirus database is updated daily), so you may see such mail disappear from your mailbox, don't fear. SPAMs are more difficult to detect, and it is an error-prone process, so we chose to use a learning software instead of using a global database. On the bright side of things, you would never loose mails and the software should be able to learn what is a SPAM from '''your''' point of view (which has proved to differ slightly between our users), but on the grey side you will have to teach him regularly to avoid errors. When your account is created, it acts like an empty headed body letting everything through, but after a few weeks of teaching it is able to recognize most of your habits and block a lot of annoying SPAM. === Web Interface === The web interface is an easy way to view your mail history, changes your settings, and more. It is available using this URL: https://spamfilter.duckcorp.org/ ==== User Settings ==== You can yourself setup a few parameters in the ''Preferences'' page of the [https://spamfilter.duckcorp.org/ web interface], mostly: * how the system should train: ** TEFT (''On every new message scanned by the filter''): useful to learn very quickly especially on a new mailbox or when you've got tons of spam on your addresses, but you need to train it regulary (daily is better) or it will learn wrong (very quickly too !) ** TOE (''Only when the filter makes a mistake''): slow learning, but if you don't have time for training very often or go on long holidays without internet access this mode will give you a stable behavior ** TUM (''Only with new data or if the filter makes a mistake''): trade-off between the two previous modes, learn quite fast and not too demanding, adapts better to new SPAMs then TOE * filter sensitivity: you can ask the system to be more or less aggressive * message handling: see [[#Delivery Mode|delivery mode]] below * ''Disable DSPAM filtering'': you may switch off filtering at your own risk We strongly recommend using TEFT with daily training for a few weeks then switching to TUM. If you need to go away for a long time, switching to TOE is recommended. Using the quarantine feature is also a safe choice, as the web interface is quite easy to use. === Delivery Mode === ==== Quarantine ==== With the ''message handling'' setting set to ''Quarantine the message'' (see [[#User Settings|user preferences]]), then your SPAMs will not go into your mailbox but stay in this stagging area. These mails are kept by the system until you decide their fate. Through the ''Quarantine'' page of the web interface, you can list these mails and: * free legitimate mails wrongly considered as SPAM by the system * delete real SPAMs if the system was right about them (freeing useful space) In this mode, you need to flush your quarantine once in a while. ==== Delivered with Special Header ==== With the ''message handling'' setting set to ''Deliver the message normally with a X-DSPAM-Result header'', mails are delivered normally, but with a special field added to your mail headers (not always visible depending on your mail client and its configuration). This is quite handy if you prefer SPAMs arranged in a specific folder. You may use then the provided [#Mail Filtering |filtering system] to sort them properly, or configure your eMail client. ==== Delivered with Modified Subject (not recommended) ==== With the ''message handling'' setting set to ''Tag the Subject header with'', mails are delivered normally, but with a modified title to alert you this is a SPAM (which is a tad ugly). This mode is really not clean and not recommended, but it exist for historical purposes, so you might still use it if you really wish to. === Retraining === Teaching the system what is SPAM and HAM (non-SPAM) is called ''retraining''. ==== Retraining using the Special ''Junk'' Folder (recommended) ==== {{warning}} This feature is to be available at 2012-02-04/05 If you have of create a folder named ''Junk'', then it is automatically magic: * if you drop mail into it, it is automatically retrained as SPAM * if you move it out of it, it is automatically retrained as HAM To use this folder properly, SPAMs '''must''' be delivered in the ''Junk'' folder automatically, so you can move them out in case of error. To achieve this, select the [[#Delivered with Special Header|delivery mode using a special header]], and use the provided [[#Mail Filtering|filtering system]] to drop them in the ''Junk'' folder ('''Do not use your mail software for this filtering, this is horribly inefficient and might alter the learning badly'''). {{warning}} This is gonna be the default at 2012-02-11/12 (but if you selected a mode in your settings it will not change, and if you have custom filtering rules they will not change either) ==== Retraining via Web Interface ==== Use the [https://spamfilter.duckcorp.org/ web interface] to retrain from errors in the ''History'' page. If you are using the ''quarantine'', then freed mails will automatically be retrained as HAM. ==== Retraining via Mail ==== Resend SPAMs to [mailto:dc-spam@duckcorp.org dc-spam@duckcorp.org] and HAM (non-SPAM) to [mailto:dc-ham@duckcorp.org dc-ham@duckcorp.org]. {{warning}} PLEASE TAKE CARE to use the ''resend'' function of your mailer and never use ''forward'', which would result in '''yourself''' being considered as SPAN or HAM. == Mail Filtering == With your favourite mail client, you can probably filter your mails in proper folders already. Nevertheless, this can be a annoying operation: * blocking you mail client for a long time if you have to process plenty of mails * downloading each mail information, and sometimes content (depending on your filters), is lenghty too, and cost much bandwidth * syncing filters accross your machines (home desktop, laptop, office machine…) is a pain in the ass * processing only when you're online prevents triggering actions in a timely manner (automatic redirect, vacation messages…), and running a machine 24/7 with a mail client polling new mails every 30s is not a solution We provide a much better way to do this using the [[wikipedia:Sieve_(mail_filtering_language)|SIEVE]] filters. Shortly, SIEVE is a language dedicated to expressing mail filters. Our server is able to process your mails according to these filters as soon as they arrive. You then don't have to care about them anymore, and may use light mail clients or webmails when you're not on your machine with your favourite software. To push your filters on the server, a dedicated protocol exists: : MANAGESIEVE (TCP 4190) on sieve.duckcorp.org Several softwares support managing SIEVE rules: * Icedove/Thunderbird using the SIEVE extension (in xul-ext-sieve Debian package) provides a rules editor * Horde (Ingo) provides an easy to use web interface * Squirrelmail with the Avelsieve extension provides an easy to use web interface * Roundcube with an extension provides an easy to use web interface * sieve-connect provides a CLI to upload/download/activate your rules files (tell us if you know more software supporting this feature) You can read more info about SIEVE here: * supported SIEVE features on our server: http://pigeonhole.dovecot.org/ * http://www.fastmail.fm/docs/sieve/ * http://sieve.info/ == Fetching eMails from an External Mailbox == {{todo}} == Shared/Public Folders == You may need to share mails or messages with friends or people you do stuff with (in a project or association). Depending on your needs, two solutions are possible: * share some of your own private folders, thus called ''shared folders'' * manage a special folder hierarchy, called ''public folders'' (even if they may not be accessible to everyone) Through IMAP, or our webmails internally using IMAP, it is possible to partition the folder hierarchy into ''namespaces''. Traditionally you are using the root namespace for your private folders. Additionnal namespaces can be created and will appear among your own folders or separate, depending on your mail client's choice of representation. To avoid name clashes, we decided to prefix all additionnal namespace names with a '''#'''. Since 2011-05-14, the following extra namespaces are created and reserved: * #Shared, containing all folders other users decided to share with you * #MilkyPond, containing public MP/DC information mailboxes you may subscribe at will Using IMAP, it is possible to setup rights (read only, write allowed…) to your own folders in order to share them with other users, or group of users. Public folders are owned by noone, and must be created by DC administrators ; if you need one, send us a request and we may be able to create it and delegate administration to your care (namespace name is subject to approval). Once created, public folders can be administered like shared folders. Client mail softwares support: * Horde: support namespaces, shared folders configurable via ''Options->Share Folders'' menu but no ACLs for public folders * Icedove/Thunderbird: support namespaces, shared and public folders configurable via folder selection and ''Tools->Imap-ACL'' menu action Most other softwares have namespace support only, so you should be able to use shared/public folders you have rights on but not configure them yourself (tell us if you know more software supporting this feature) == Limitations == === Maximum Mail Size === Mail you send or receive are limited to '''10MB'''. If you need to transmit much bigger data, then a mail transport is not appropriate, you'd better use a file sharing method instead. === Quotas === Even if it would be nice to live without it, we had to establish quotas to force people sort their mails out once in a while and delete useless things instead of leaving an ever-growing mess behind. The default quota is '''512MB''' which is not that big but should match needs of most users. This said, you may ask us for more and there's no reason we would refuse a reasonable demand. == Technical Details == This service is made using: * [http://www.postfix.org/ Postfix] * [http://dovecot.org/ Dovecot] * [http://dspam.sourceforge.net DSPAM] * [http://johannes.sipsolutions.net/Projects/dovecot-antispam dovecot-antispam] * [https://projects.duckcorp.org/projects/spoolinger Spoolinger] * [http://www.horde.org/ Horde] * [http://www.squirrelmail.org/ SquirrelMail] * [http://www.roundcube.net/ RoundCube] a7aeb81915f4704174c62e8799d4224fd140b917 363 362 2012-01-30T23:40:57Z Duck 2 /* Delivered with Special Header */ wikitext text/x-wiki {{Template:Service | description = Available services: * multiple email addresses (mailboxes+aliases or redirections) based on the ''milkypond.org'' (or maybe ''duckcorp.org'') domain * roaming accounts to be able to send emails wherever you are If you want email addresses using you own domain(s), see the [[Services/MailHosting|mail hosting service]]. | prerequisite = | account = global-reg | ipv6 = true | security_notes = Access to the mail services are fully secured, and to your data, nevertheless most mail exchange on the Internet are not. Complete security can be achieved using signed and encrypted mail (see [[wikipedia:Pretty_Good_Privacy|OpenPGP]] and [[wikipedia:S/MIME|S/MIME]]) }} == Access == === Using a Mail Reader === You can retrieve your mails, in case of a real mailbox, using either: * IMAP+TLS (TCP 143) / IMAPS (TCP 993) on imap.duckcorp.org * or POP3+TLS (TCP 110) / POP3S (TCP 995) on pop.duckcorp.org The IMAP protocol is recommended over POP3, as it provides many interesting features. If you want to download all your mails absolutely at home, loosing the ability to read your mail from anywhere on the planet, you can do that with IMAP too (look at your mail client settings). You can use our servers to send mails out too via smtp.duckcorp.org using: * SMTP+TLS (TCP 25) / SMTPS (TCP 465) * and SASL authentication === Using a Web Interface === Several [https://webmail.duckcorp.org/ webmail interfaces] are available. == Antivirus and Antispam == Mails stored on our server are checked upon arrival for viruses and SPAMs. Mail redirected to a third party mailbox are not, not to mess with the strategy of the the final destination (which could arm learning greatly). Mails being viruses are suppressed automatically upon arrival. Once in a week, an extra antivirus check is done on all hosted mailboxes, to remove viruses not detected at the time it arrived (our antivirus database is updated daily), so you may see such mail disappear from your mailbox, don't fear. SPAMs are more difficult to detect, and it is an error-prone process, so we chose to use a learning software instead of using a global database. On the bright side of things, you would never loose mails and the software should be able to learn what is a SPAM from '''your''' point of view (which has proved to differ slightly between our users), but on the grey side you will have to teach him regularly to avoid errors. When your account is created, it acts like an empty headed body letting everything through, but after a few weeks of teaching it is able to recognize most of your habits and block a lot of annoying SPAM. === Web Interface === The web interface is an easy way to view your mail history, changes your settings, and more. It is available using this URL: https://spamfilter.duckcorp.org/ ==== User Settings ==== You can yourself setup a few parameters in the ''Preferences'' page of the [https://spamfilter.duckcorp.org/ web interface], mostly: * how the system should train: ** TEFT (''On every new message scanned by the filter''): useful to learn very quickly especially on a new mailbox or when you've got tons of spam on your addresses, but you need to train it regulary (daily is better) or it will learn wrong (very quickly too !) ** TOE (''Only when the filter makes a mistake''): slow learning, but if you don't have time for training very often or go on long holidays without internet access this mode will give you a stable behavior ** TUM (''Only with new data or if the filter makes a mistake''): trade-off between the two previous modes, learn quite fast and not too demanding, adapts better to new SPAMs then TOE * filter sensitivity: you can ask the system to be more or less aggressive * message handling: see [[#Delivery Mode|delivery mode]] below * ''Disable DSPAM filtering'': you may switch off filtering at your own risk We strongly recommend using TEFT with daily training for a few weeks then switching to TUM. If you need to go away for a long time, switching to TOE is recommended. Using the quarantine feature is also a safe choice, as the web interface is quite easy to use. === Delivery Mode === ==== Quarantine ==== With the ''message handling'' setting set to ''Quarantine the message'' (see [[#User Settings|user preferences]]), then your SPAMs will not go into your mailbox but stay in this stagging area. These mails are kept by the system until you decide their fate. Through the ''Quarantine'' page of the web interface, you can list these mails and: * free legitimate mails wrongly considered as SPAM by the system * delete real SPAMs if the system was right about them (freeing useful space) In this mode, you need to flush your quarantine once in a while. ==== Delivered with Special Header (recommended) ==== With the ''message handling'' setting set to ''Deliver the message normally with a X-DSPAM-Result header'', mails are delivered normally, but with a special field added to your mail headers (not always visible depending on your mail client and its configuration). This is quite handy if you prefer SPAMs arranged in a specific folder. You may use then the provided [#Mail Filtering |filtering system] to sort them properly, or configure your eMail client. ==== Delivered with Modified Subject (not recommended) ==== With the ''message handling'' setting set to ''Tag the Subject header with'', mails are delivered normally, but with a modified title to alert you this is a SPAM (which is a tad ugly). This mode is really not clean and not recommended, but it exist for historical purposes, so you might still use it if you really wish to. === Retraining === Teaching the system what is SPAM and HAM (non-SPAM) is called ''retraining''. ==== Retraining using the Special ''Junk'' Folder (recommended) ==== {{warning}} This feature is to be available at 2012-02-04/05 If you have of create a folder named ''Junk'', then it is automatically magic: * if you drop mail into it, it is automatically retrained as SPAM * if you move it out of it, it is automatically retrained as HAM To use this folder properly, SPAMs '''must''' be delivered in the ''Junk'' folder automatically, so you can move them out in case of error. To achieve this, select the [[#Delivered with Special Header|delivery mode using a special header]], and use the provided [[#Mail Filtering|filtering system]] to drop them in the ''Junk'' folder ('''Do not use your mail software for this filtering, this is horribly inefficient and might alter the learning badly'''). {{warning}} This is gonna be the default at 2012-02-11/12 (but if you selected a mode in your settings it will not change, and if you have custom filtering rules they will not change either) ==== Retraining via Web Interface ==== Use the [https://spamfilter.duckcorp.org/ web interface] to retrain from errors in the ''History'' page. If you are using the ''quarantine'', then freed mails will automatically be retrained as HAM. ==== Retraining via Mail ==== Resend SPAMs to [mailto:dc-spam@duckcorp.org dc-spam@duckcorp.org] and HAM (non-SPAM) to [mailto:dc-ham@duckcorp.org dc-ham@duckcorp.org]. {{warning}} PLEASE TAKE CARE to use the ''resend'' function of your mailer and never use ''forward'', which would result in '''yourself''' being considered as SPAN or HAM. == Mail Filtering == With your favourite mail client, you can probably filter your mails in proper folders already. Nevertheless, this can be a annoying operation: * blocking you mail client for a long time if you have to process plenty of mails * downloading each mail information, and sometimes content (depending on your filters), is lenghty too, and cost much bandwidth * syncing filters accross your machines (home desktop, laptop, office machine…) is a pain in the ass * processing only when you're online prevents triggering actions in a timely manner (automatic redirect, vacation messages…), and running a machine 24/7 with a mail client polling new mails every 30s is not a solution We provide a much better way to do this using the [[wikipedia:Sieve_(mail_filtering_language)|SIEVE]] filters. Shortly, SIEVE is a language dedicated to expressing mail filters. Our server is able to process your mails according to these filters as soon as they arrive. You then don't have to care about them anymore, and may use light mail clients or webmails when you're not on your machine with your favourite software. To push your filters on the server, a dedicated protocol exists: : MANAGESIEVE (TCP 4190) on sieve.duckcorp.org Several softwares support managing SIEVE rules: * Icedove/Thunderbird using the SIEVE extension (in xul-ext-sieve Debian package) provides a rules editor * Horde (Ingo) provides an easy to use web interface * Squirrelmail with the Avelsieve extension provides an easy to use web interface * Roundcube with an extension provides an easy to use web interface * sieve-connect provides a CLI to upload/download/activate your rules files (tell us if you know more software supporting this feature) You can read more info about SIEVE here: * supported SIEVE features on our server: http://pigeonhole.dovecot.org/ * http://www.fastmail.fm/docs/sieve/ * http://sieve.info/ == Fetching eMails from an External Mailbox == {{todo}} == Shared/Public Folders == You may need to share mails or messages with friends or people you do stuff with (in a project or association). Depending on your needs, two solutions are possible: * share some of your own private folders, thus called ''shared folders'' * manage a special folder hierarchy, called ''public folders'' (even if they may not be accessible to everyone) Through IMAP, or our webmails internally using IMAP, it is possible to partition the folder hierarchy into ''namespaces''. Traditionally you are using the root namespace for your private folders. Additionnal namespaces can be created and will appear among your own folders or separate, depending on your mail client's choice of representation. To avoid name clashes, we decided to prefix all additionnal namespace names with a '''#'''. Since 2011-05-14, the following extra namespaces are created and reserved: * #Shared, containing all folders other users decided to share with you * #MilkyPond, containing public MP/DC information mailboxes you may subscribe at will Using IMAP, it is possible to setup rights (read only, write allowed…) to your own folders in order to share them with other users, or group of users. Public folders are owned by noone, and must be created by DC administrators ; if you need one, send us a request and we may be able to create it and delegate administration to your care (namespace name is subject to approval). Once created, public folders can be administered like shared folders. Client mail softwares support: * Horde: support namespaces, shared folders configurable via ''Options->Share Folders'' menu but no ACLs for public folders * Icedove/Thunderbird: support namespaces, shared and public folders configurable via folder selection and ''Tools->Imap-ACL'' menu action Most other softwares have namespace support only, so you should be able to use shared/public folders you have rights on but not configure them yourself (tell us if you know more software supporting this feature) == Limitations == === Maximum Mail Size === Mail you send or receive are limited to '''10MB'''. If you need to transmit much bigger data, then a mail transport is not appropriate, you'd better use a file sharing method instead. === Quotas === Even if it would be nice to live without it, we had to establish quotas to force people sort their mails out once in a while and delete useless things instead of leaving an ever-growing mess behind. The default quota is '''512MB''' which is not that big but should match needs of most users. This said, you may ask us for more and there's no reason we would refuse a reasonable demand. == Technical Details == This service is made using: * [http://www.postfix.org/ Postfix] * [http://dovecot.org/ Dovecot] * [http://dspam.sourceforge.net DSPAM] * [http://johannes.sipsolutions.net/Projects/dovecot-antispam dovecot-antispam] * [https://projects.duckcorp.org/projects/spoolinger Spoolinger] * [http://www.horde.org/ Horde] * [http://www.squirrelmail.org/ SquirrelMail] * [http://www.roundcube.net/ RoundCube] db1db5acef2d7dd8678195bcb9e85fbe828b8865 364 363 2012-01-31T00:09:44Z Duck 2 /* Mail Filtering */ wikitext text/x-wiki {{Template:Service | description = Available services: * multiple email addresses (mailboxes+aliases or redirections) based on the ''milkypond.org'' (or maybe ''duckcorp.org'') domain * roaming accounts to be able to send emails wherever you are If you want email addresses using you own domain(s), see the [[Services/MailHosting|mail hosting service]]. | prerequisite = | account = global-reg | ipv6 = true | security_notes = Access to the mail services are fully secured, and to your data, nevertheless most mail exchange on the Internet are not. Complete security can be achieved using signed and encrypted mail (see [[wikipedia:Pretty_Good_Privacy|OpenPGP]] and [[wikipedia:S/MIME|S/MIME]]) }} == Access == === Using a Mail Reader === You can retrieve your mails, in case of a real mailbox, using either: * IMAP+TLS (TCP 143) / IMAPS (TCP 993) on imap.duckcorp.org * or POP3+TLS (TCP 110) / POP3S (TCP 995) on pop.duckcorp.org The IMAP protocol is recommended over POP3, as it provides many interesting features. If you want to download all your mails absolutely at home, loosing the ability to read your mail from anywhere on the planet, you can do that with IMAP too (look at your mail client settings). You can use our servers to send mails out too via smtp.duckcorp.org using: * SMTP+TLS (TCP 25) / SMTPS (TCP 465) * and SASL authentication === Using a Web Interface === Several [https://webmail.duckcorp.org/ webmail interfaces] are available. == Antivirus and Antispam == Mails stored on our server are checked upon arrival for viruses and SPAMs. Mail redirected to a third party mailbox are not, not to mess with the strategy of the the final destination (which could arm learning greatly). Mails being viruses are suppressed automatically upon arrival. Once in a week, an extra antivirus check is done on all hosted mailboxes, to remove viruses not detected at the time it arrived (our antivirus database is updated daily), so you may see such mail disappear from your mailbox, don't fear. SPAMs are more difficult to detect, and it is an error-prone process, so we chose to use a learning software instead of using a global database. On the bright side of things, you would never loose mails and the software should be able to learn what is a SPAM from '''your''' point of view (which has proved to differ slightly between our users), but on the grey side you will have to teach him regularly to avoid errors. When your account is created, it acts like an empty headed body letting everything through, but after a few weeks of teaching it is able to recognize most of your habits and block a lot of annoying SPAM. === Web Interface === The web interface is an easy way to view your mail history, changes your settings, and more. It is available using this URL: https://spamfilter.duckcorp.org/ ==== User Settings ==== You can yourself setup a few parameters in the ''Preferences'' page of the [https://spamfilter.duckcorp.org/ web interface], mostly: * how the system should train: ** TEFT (''On every new message scanned by the filter''): useful to learn very quickly especially on a new mailbox or when you've got tons of spam on your addresses, but you need to train it regulary (daily is better) or it will learn wrong (very quickly too !) ** TOE (''Only when the filter makes a mistake''): slow learning, but if you don't have time for training very often or go on long holidays without internet access this mode will give you a stable behavior ** TUM (''Only with new data or if the filter makes a mistake''): trade-off between the two previous modes, learn quite fast and not too demanding, adapts better to new SPAMs then TOE * filter sensitivity: you can ask the system to be more or less aggressive * message handling: see [[#Delivery Mode|delivery mode]] below * ''Disable DSPAM filtering'': you may switch off filtering at your own risk We strongly recommend using TEFT with daily training for a few weeks then switching to TUM. If you need to go away for a long time, switching to TOE is recommended. Using the quarantine feature is also a safe choice, as the web interface is quite easy to use. === Delivery Mode === ==== Quarantine ==== With the ''message handling'' setting set to ''Quarantine the message'' (see [[#User Settings|user preferences]]), then your SPAMs will not go into your mailbox but stay in this stagging area. These mails are kept by the system until you decide their fate. Through the ''Quarantine'' page of the web interface, you can list these mails and: * free legitimate mails wrongly considered as SPAM by the system * delete real SPAMs if the system was right about them (freeing useful space) In this mode, you need to flush your quarantine once in a while. ==== Delivered with Special Header (recommended) ==== With the ''message handling'' setting set to ''Deliver the message normally with a X-DSPAM-Result header'', mails are delivered normally, but with a special field added to your mail headers (not always visible depending on your mail client and its configuration). This is quite handy if you prefer SPAMs arranged in a specific folder. You may use then the provided [#Mail Filtering |filtering system] to sort them properly, or configure your eMail client. ==== Delivered with Modified Subject (not recommended) ==== With the ''message handling'' setting set to ''Tag the Subject header with'', mails are delivered normally, but with a modified title to alert you this is a SPAM (which is a tad ugly). This mode is really not clean and not recommended, but it exist for historical purposes, so you might still use it if you really wish to. === Retraining === Teaching the system what is SPAM and HAM (non-SPAM) is called ''retraining''. ==== Retraining using the Special ''Junk'' Folder (recommended) ==== {{warning}} This feature is to be available at 2012-02-04/05 If you have of create a folder named ''Junk'', then it is automatically magic: * if you drop mail into it, it is automatically retrained as SPAM * if you move it out of it, it is automatically retrained as HAM To use this folder properly, SPAMs '''must''' be delivered in the ''Junk'' folder automatically, so you can move them out in case of error. To achieve this, select the [[#Delivered with Special Header|delivery mode using a special header]], and use the provided [[#Mail Filtering|filtering system]] to drop them in the ''Junk'' folder ('''Do not use your mail software for this filtering, this is horribly inefficient and might alter the learning badly'''). {{warning}} This is gonna be the default at 2012-02-11/12 (but if you selected a mode in your settings it will not change, and if you have custom filtering rules they will not change either) ==== Retraining via Web Interface ==== Use the [https://spamfilter.duckcorp.org/ web interface] to retrain from errors in the ''History'' page. If you are using the ''quarantine'', then freed mails will automatically be retrained as HAM. ==== Retraining via Mail ==== Resend SPAMs to [mailto:dc-spam@duckcorp.org dc-spam@duckcorp.org] and HAM (non-SPAM) to [mailto:dc-ham@duckcorp.org dc-ham@duckcorp.org]. {{warning}} PLEASE TAKE CARE to use the ''resend'' function of your mailer and never use ''forward'', which would result in '''yourself''' being considered as SPAN or HAM. == Mail Filtering == With your favourite mail client, you can probably filter your mails in proper folders already. Nevertheless, this can be aa annoying operation: * blocking you mail client for a long time if you have to process plenty of mails * downloading each mail information, and sometimes content (depending on your filters), is lenghty too, and cost much bandwidth * syncing filters across your machines (home desktop, laptop, office machine…) is a pain in the ass * processing only when you're online prevents triggering actions in a timely manner (automatic redirect, vacation messages…), and running a machine 24/7 with a mail client polling new mails every 30s is not a solution We provide a much better way to do this using the [[wikipedia:Sieve_(mail_filtering_language)|SIEVE]] filters. Shortly, SIEVE is a language dedicated to expressing mail filters (also called ''rules''). Our server is able to process your mails according to these filters as soon as they arrive. You then don't have to care about them anymore, and may use light mail clients or webmails when you're not on your machine with your favourite software. === Rules Configuration === You can express sort/reject/vacation/… filters using these rules, as the capabilities are very rich. Several softwares support managing SIEVE rules: * Icedove/Thunderbird: *: using the SIEVE extension (in ''xul-ext-sieve'' Debian package), it provides a rules editor (for power-users) * Horde (Ingo): *: provides an easy to use web interface *: this webmail has been made available [https://webdesk.duckcorp.org/ here] * Squirrelmail: *: coupled with the Avelsieve extension, provides an easy to use web interface *: this webmail has been made available [https://webmail-sm.duckcorp.org/ here] * Roundcube: *: coupled with the sieverules extension, provides an easy to use web interface *: this webmail has been made available [https://webmail-rc.duckcorp.org/ here] * sieve-connect: *: provides a CLI to upload/download/activate your rules files *: this tool is available on [[Services/Shell|shell hosts]] (tell us if you know more software supporting this feature) To push your filters on the server, a dedicated protocol exists: MANAGESIEVE (TCP 4190) on ''sieve.duckcorp.org''. Our webmails are already configured to use it, but it you use sieve-connect from our hosts or your own mail software, you'll need these parameters. You can read more info about SIEVE here: * supported SIEVE features on our server: http://pigeonhole.dovecot.org/ * http://www.fastmail.fm/docs/sieve/ * http://sieve.info/ === Default Rules === There are no default rules. All your mails will end-up in your ''Inbox'' folder and you may then to sort them by yourself. {{warning}} Starting at 2012-02-11/12, the default rules will include the global ''Junk folder'' rule, coupled with the [[#Delivered with Special Header|delivery using a special header]], in order to provide a simple default configuration for most users (but this won't affect power-users having custom rules) === Global Rules === == Fetching eMails from an External Mailbox == {{todo}} == Shared/Public Folders == You may need to share mails or messages with friends or people you do stuff with (in a project or association). Depending on your needs, two solutions are possible: * share some of your own private folders, thus called ''shared folders'' * manage a special folder hierarchy, called ''public folders'' (even if they may not be accessible to everyone) Through IMAP, or our webmails internally using IMAP, it is possible to partition the folder hierarchy into ''namespaces''. Traditionally you are using the root namespace for your private folders. Additionnal namespaces can be created and will appear among your own folders or separate, depending on your mail client's choice of representation. To avoid name clashes, we decided to prefix all additionnal namespace names with a '''#'''. Since 2011-05-14, the following extra namespaces are created and reserved: * #Shared, containing all folders other users decided to share with you * #MilkyPond, containing public MP/DC information mailboxes you may subscribe at will Using IMAP, it is possible to setup rights (read only, write allowed…) to your own folders in order to share them with other users, or group of users. Public folders are owned by noone, and must be created by DC administrators ; if you need one, send us a request and we may be able to create it and delegate administration to your care (namespace name is subject to approval). Once created, public folders can be administered like shared folders. Client mail softwares support: * Horde: support namespaces, shared folders configurable via ''Options->Share Folders'' menu but no ACLs for public folders * Icedove/Thunderbird: support namespaces, shared and public folders configurable via folder selection and ''Tools->Imap-ACL'' menu action Most other softwares have namespace support only, so you should be able to use shared/public folders you have rights on but not configure them yourself (tell us if you know more software supporting this feature) == Limitations == === Maximum Mail Size === Mail you send or receive are limited to '''10MB'''. If you need to transmit much bigger data, then a mail transport is not appropriate, you'd better use a file sharing method instead. === Quotas === Even if it would be nice to live without it, we had to establish quotas to force people sort their mails out once in a while and delete useless things instead of leaving an ever-growing mess behind. The default quota is '''512MB''' which is not that big but should match needs of most users. This said, you may ask us for more and there's no reason we would refuse a reasonable demand. == Technical Details == This service is made using: * [http://www.postfix.org/ Postfix] * [http://dovecot.org/ Dovecot] * [http://dspam.sourceforge.net DSPAM] * [http://johannes.sipsolutions.net/Projects/dovecot-antispam dovecot-antispam] * [https://projects.duckcorp.org/projects/spoolinger Spoolinger] * [http://www.horde.org/ Horde] * [http://www.squirrelmail.org/ SquirrelMail] * [http://www.roundcube.net/ RoundCube] 22562fafd9312949dd5b7162699fffb6e53dfc92 365 364 2012-01-31T00:11:15Z Duck 2 /* Default Rules */ wikitext text/x-wiki {{Template:Service | description = Available services: * multiple email addresses (mailboxes+aliases or redirections) based on the ''milkypond.org'' (or maybe ''duckcorp.org'') domain * roaming accounts to be able to send emails wherever you are If you want email addresses using you own domain(s), see the [[Services/MailHosting|mail hosting service]]. | prerequisite = | account = global-reg | ipv6 = true | security_notes = Access to the mail services are fully secured, and to your data, nevertheless most mail exchange on the Internet are not. Complete security can be achieved using signed and encrypted mail (see [[wikipedia:Pretty_Good_Privacy|OpenPGP]] and [[wikipedia:S/MIME|S/MIME]]) }} == Access == === Using a Mail Reader === You can retrieve your mails, in case of a real mailbox, using either: * IMAP+TLS (TCP 143) / IMAPS (TCP 993) on imap.duckcorp.org * or POP3+TLS (TCP 110) / POP3S (TCP 995) on pop.duckcorp.org The IMAP protocol is recommended over POP3, as it provides many interesting features. If you want to download all your mails absolutely at home, loosing the ability to read your mail from anywhere on the planet, you can do that with IMAP too (look at your mail client settings). You can use our servers to send mails out too via smtp.duckcorp.org using: * SMTP+TLS (TCP 25) / SMTPS (TCP 465) * and SASL authentication === Using a Web Interface === Several [https://webmail.duckcorp.org/ webmail interfaces] are available. == Antivirus and Antispam == Mails stored on our server are checked upon arrival for viruses and SPAMs. Mail redirected to a third party mailbox are not, not to mess with the strategy of the the final destination (which could arm learning greatly). Mails being viruses are suppressed automatically upon arrival. Once in a week, an extra antivirus check is done on all hosted mailboxes, to remove viruses not detected at the time it arrived (our antivirus database is updated daily), so you may see such mail disappear from your mailbox, don't fear. SPAMs are more difficult to detect, and it is an error-prone process, so we chose to use a learning software instead of using a global database. On the bright side of things, you would never loose mails and the software should be able to learn what is a SPAM from '''your''' point of view (which has proved to differ slightly between our users), but on the grey side you will have to teach him regularly to avoid errors. When your account is created, it acts like an empty headed body letting everything through, but after a few weeks of teaching it is able to recognize most of your habits and block a lot of annoying SPAM. === Web Interface === The web interface is an easy way to view your mail history, changes your settings, and more. It is available using this URL: https://spamfilter.duckcorp.org/ ==== User Settings ==== You can yourself setup a few parameters in the ''Preferences'' page of the [https://spamfilter.duckcorp.org/ web interface], mostly: * how the system should train: ** TEFT (''On every new message scanned by the filter''): useful to learn very quickly especially on a new mailbox or when you've got tons of spam on your addresses, but you need to train it regulary (daily is better) or it will learn wrong (very quickly too !) ** TOE (''Only when the filter makes a mistake''): slow learning, but if you don't have time for training very often or go on long holidays without internet access this mode will give you a stable behavior ** TUM (''Only with new data or if the filter makes a mistake''): trade-off between the two previous modes, learn quite fast and not too demanding, adapts better to new SPAMs then TOE * filter sensitivity: you can ask the system to be more or less aggressive * message handling: see [[#Delivery Mode|delivery mode]] below * ''Disable DSPAM filtering'': you may switch off filtering at your own risk We strongly recommend using TEFT with daily training for a few weeks then switching to TUM. If you need to go away for a long time, switching to TOE is recommended. Using the quarantine feature is also a safe choice, as the web interface is quite easy to use. === Delivery Mode === ==== Quarantine ==== With the ''message handling'' setting set to ''Quarantine the message'' (see [[#User Settings|user preferences]]), then your SPAMs will not go into your mailbox but stay in this stagging area. These mails are kept by the system until you decide their fate. Through the ''Quarantine'' page of the web interface, you can list these mails and: * free legitimate mails wrongly considered as SPAM by the system * delete real SPAMs if the system was right about them (freeing useful space) In this mode, you need to flush your quarantine once in a while. ==== Delivered with Special Header (recommended) ==== With the ''message handling'' setting set to ''Deliver the message normally with a X-DSPAM-Result header'', mails are delivered normally, but with a special field added to your mail headers (not always visible depending on your mail client and its configuration). This is quite handy if you prefer SPAMs arranged in a specific folder. You may use then the provided [#Mail Filtering |filtering system] to sort them properly, or configure your eMail client. ==== Delivered with Modified Subject (not recommended) ==== With the ''message handling'' setting set to ''Tag the Subject header with'', mails are delivered normally, but with a modified title to alert you this is a SPAM (which is a tad ugly). This mode is really not clean and not recommended, but it exist for historical purposes, so you might still use it if you really wish to. === Retraining === Teaching the system what is SPAM and HAM (non-SPAM) is called ''retraining''. ==== Retraining using the Special ''Junk'' Folder (recommended) ==== {{warning}} This feature is to be available at 2012-02-04/05 If you have of create a folder named ''Junk'', then it is automatically magic: * if you drop mail into it, it is automatically retrained as SPAM * if you move it out of it, it is automatically retrained as HAM To use this folder properly, SPAMs '''must''' be delivered in the ''Junk'' folder automatically, so you can move them out in case of error. To achieve this, select the [[#Delivered with Special Header|delivery mode using a special header]], and use the provided [[#Mail Filtering|filtering system]] to drop them in the ''Junk'' folder ('''Do not use your mail software for this filtering, this is horribly inefficient and might alter the learning badly'''). {{warning}} This is gonna be the default at 2012-02-11/12 (but if you selected a mode in your settings it will not change, and if you have custom filtering rules they will not change either) ==== Retraining via Web Interface ==== Use the [https://spamfilter.duckcorp.org/ web interface] to retrain from errors in the ''History'' page. If you are using the ''quarantine'', then freed mails will automatically be retrained as HAM. ==== Retraining via Mail ==== Resend SPAMs to [mailto:dc-spam@duckcorp.org dc-spam@duckcorp.org] and HAM (non-SPAM) to [mailto:dc-ham@duckcorp.org dc-ham@duckcorp.org]. {{warning}} PLEASE TAKE CARE to use the ''resend'' function of your mailer and never use ''forward'', which would result in '''yourself''' being considered as SPAN or HAM. == Mail Filtering == With your favourite mail client, you can probably filter your mails in proper folders already. Nevertheless, this can be aa annoying operation: * blocking you mail client for a long time if you have to process plenty of mails * downloading each mail information, and sometimes content (depending on your filters), is lenghty too, and cost much bandwidth * syncing filters across your machines (home desktop, laptop, office machine…) is a pain in the ass * processing only when you're online prevents triggering actions in a timely manner (automatic redirect, vacation messages…), and running a machine 24/7 with a mail client polling new mails every 30s is not a solution We provide a much better way to do this using the [[wikipedia:Sieve_(mail_filtering_language)|SIEVE]] filters. Shortly, SIEVE is a language dedicated to expressing mail filters (also called ''rules''). Our server is able to process your mails according to these filters as soon as they arrive. You then don't have to care about them anymore, and may use light mail clients or webmails when you're not on your machine with your favourite software. === Rules Configuration === You can express sort/reject/vacation/… filters using these rules, as the capabilities are very rich. Several softwares support managing SIEVE rules: * Icedove/Thunderbird: *: using the SIEVE extension (in ''xul-ext-sieve'' Debian package), it provides a rules editor (for power-users) * Horde (Ingo): *: provides an easy to use web interface *: this webmail has been made available [https://webdesk.duckcorp.org/ here] * Squirrelmail: *: coupled with the Avelsieve extension, provides an easy to use web interface *: this webmail has been made available [https://webmail-sm.duckcorp.org/ here] * Roundcube: *: coupled with the sieverules extension, provides an easy to use web interface *: this webmail has been made available [https://webmail-rc.duckcorp.org/ here] * sieve-connect: *: provides a CLI to upload/download/activate your rules files *: this tool is available on [[Services/Shell|shell hosts]] (tell us if you know more software supporting this feature) To push your filters on the server, a dedicated protocol exists: MANAGESIEVE (TCP 4190) on ''sieve.duckcorp.org''. Our webmails are already configured to use it, but it you use sieve-connect from our hosts or your own mail software, you'll need these parameters. You can read more info about SIEVE here: * supported SIEVE features on our server: http://pigeonhole.dovecot.org/ * http://www.fastmail.fm/docs/sieve/ * http://sieve.info/ === Default Rules === There are no default rules. All your mails will end-up in your ''Inbox'' folder and you may then to sort them by yourself. {{warning}} Starting at 2012-02-11/12, the default rules will include the global ''incoming_spam'' rule, coupled with the [[#Delivered with Special Header|delivery using a special header]], in order to provide a simple default configuration for most users (but this won't affect power-users having custom rules) === Global Rules === == Fetching eMails from an External Mailbox == {{todo}} == Shared/Public Folders == You may need to share mails or messages with friends or people you do stuff with (in a project or association). Depending on your needs, two solutions are possible: * share some of your own private folders, thus called ''shared folders'' * manage a special folder hierarchy, called ''public folders'' (even if they may not be accessible to everyone) Through IMAP, or our webmails internally using IMAP, it is possible to partition the folder hierarchy into ''namespaces''. Traditionally you are using the root namespace for your private folders. Additionnal namespaces can be created and will appear among your own folders or separate, depending on your mail client's choice of representation. To avoid name clashes, we decided to prefix all additionnal namespace names with a '''#'''. Since 2011-05-14, the following extra namespaces are created and reserved: * #Shared, containing all folders other users decided to share with you * #MilkyPond, containing public MP/DC information mailboxes you may subscribe at will Using IMAP, it is possible to setup rights (read only, write allowed…) to your own folders in order to share them with other users, or group of users. Public folders are owned by noone, and must be created by DC administrators ; if you need one, send us a request and we may be able to create it and delegate administration to your care (namespace name is subject to approval). Once created, public folders can be administered like shared folders. Client mail softwares support: * Horde: support namespaces, shared folders configurable via ''Options->Share Folders'' menu but no ACLs for public folders * Icedove/Thunderbird: support namespaces, shared and public folders configurable via folder selection and ''Tools->Imap-ACL'' menu action Most other softwares have namespace support only, so you should be able to use shared/public folders you have rights on but not configure them yourself (tell us if you know more software supporting this feature) == Limitations == === Maximum Mail Size === Mail you send or receive are limited to '''10MB'''. If you need to transmit much bigger data, then a mail transport is not appropriate, you'd better use a file sharing method instead. === Quotas === Even if it would be nice to live without it, we had to establish quotas to force people sort their mails out once in a while and delete useless things instead of leaving an ever-growing mess behind. The default quota is '''512MB''' which is not that big but should match needs of most users. This said, you may ask us for more and there's no reason we would refuse a reasonable demand. == Technical Details == This service is made using: * [http://www.postfix.org/ Postfix] * [http://dovecot.org/ Dovecot] * [http://dspam.sourceforge.net DSPAM] * [http://johannes.sipsolutions.net/Projects/dovecot-antispam dovecot-antispam] * [https://projects.duckcorp.org/projects/spoolinger Spoolinger] * [http://www.horde.org/ Horde] * [http://www.squirrelmail.org/ SquirrelMail] * [http://www.roundcube.net/ RoundCube] 1baf5343fe40f97ab1dbf3ef5954b67960c74aa2 366 365 2012-01-31T00:19:23Z Duck 2 /* Global Rules */ wikitext text/x-wiki {{Template:Service | description = Available services: * multiple email addresses (mailboxes+aliases or redirections) based on the ''milkypond.org'' (or maybe ''duckcorp.org'') domain * roaming accounts to be able to send emails wherever you are If you want email addresses using you own domain(s), see the [[Services/MailHosting|mail hosting service]]. | prerequisite = | account = global-reg | ipv6 = true | security_notes = Access to the mail services are fully secured, and to your data, nevertheless most mail exchange on the Internet are not. Complete security can be achieved using signed and encrypted mail (see [[wikipedia:Pretty_Good_Privacy|OpenPGP]] and [[wikipedia:S/MIME|S/MIME]]) }} == Access == === Using a Mail Reader === You can retrieve your mails, in case of a real mailbox, using either: * IMAP+TLS (TCP 143) / IMAPS (TCP 993) on imap.duckcorp.org * or POP3+TLS (TCP 110) / POP3S (TCP 995) on pop.duckcorp.org The IMAP protocol is recommended over POP3, as it provides many interesting features. If you want to download all your mails absolutely at home, loosing the ability to read your mail from anywhere on the planet, you can do that with IMAP too (look at your mail client settings). You can use our servers to send mails out too via smtp.duckcorp.org using: * SMTP+TLS (TCP 25) / SMTPS (TCP 465) * and SASL authentication === Using a Web Interface === Several [https://webmail.duckcorp.org/ webmail interfaces] are available. == Antivirus and Antispam == Mails stored on our server are checked upon arrival for viruses and SPAMs. Mail redirected to a third party mailbox are not, not to mess with the strategy of the the final destination (which could arm learning greatly). Mails being viruses are suppressed automatically upon arrival. Once in a week, an extra antivirus check is done on all hosted mailboxes, to remove viruses not detected at the time it arrived (our antivirus database is updated daily), so you may see such mail disappear from your mailbox, don't fear. SPAMs are more difficult to detect, and it is an error-prone process, so we chose to use a learning software instead of using a global database. On the bright side of things, you would never loose mails and the software should be able to learn what is a SPAM from '''your''' point of view (which has proved to differ slightly between our users), but on the grey side you will have to teach him regularly to avoid errors. When your account is created, it acts like an empty headed body letting everything through, but after a few weeks of teaching it is able to recognize most of your habits and block a lot of annoying SPAM. === Web Interface === The web interface is an easy way to view your mail history, changes your settings, and more. It is available using this URL: https://spamfilter.duckcorp.org/ ==== User Settings ==== You can yourself setup a few parameters in the ''Preferences'' page of the [https://spamfilter.duckcorp.org/ web interface], mostly: * how the system should train: ** TEFT (''On every new message scanned by the filter''): useful to learn very quickly especially on a new mailbox or when you've got tons of spam on your addresses, but you need to train it regulary (daily is better) or it will learn wrong (very quickly too !) ** TOE (''Only when the filter makes a mistake''): slow learning, but if you don't have time for training very often or go on long holidays without internet access this mode will give you a stable behavior ** TUM (''Only with new data or if the filter makes a mistake''): trade-off between the two previous modes, learn quite fast and not too demanding, adapts better to new SPAMs then TOE * filter sensitivity: you can ask the system to be more or less aggressive * message handling: see [[#Delivery Mode|delivery mode]] below * ''Disable DSPAM filtering'': you may switch off filtering at your own risk We strongly recommend using TEFT with daily training for a few weeks then switching to TUM. If you need to go away for a long time, switching to TOE is recommended. Using the quarantine feature is also a safe choice, as the web interface is quite easy to use. === Delivery Mode === ==== Quarantine ==== With the ''message handling'' setting set to ''Quarantine the message'' (see [[#User Settings|user preferences]]), then your SPAMs will not go into your mailbox but stay in this stagging area. These mails are kept by the system until you decide their fate. Through the ''Quarantine'' page of the web interface, you can list these mails and: * free legitimate mails wrongly considered as SPAM by the system * delete real SPAMs if the system was right about them (freeing useful space) In this mode, you need to flush your quarantine once in a while. ==== Delivered with Special Header (recommended) ==== With the ''message handling'' setting set to ''Deliver the message normally with a X-DSPAM-Result header'', mails are delivered normally, but with a special field added to your mail headers (not always visible depending on your mail client and its configuration). This is quite handy if you prefer SPAMs arranged in a specific folder. You may use then the provided [#Mail Filtering |filtering system] to sort them properly, or configure your eMail client. ==== Delivered with Modified Subject (not recommended) ==== With the ''message handling'' setting set to ''Tag the Subject header with'', mails are delivered normally, but with a modified title to alert you this is a SPAM (which is a tad ugly). This mode is really not clean and not recommended, but it exist for historical purposes, so you might still use it if you really wish to. === Retraining === Teaching the system what is SPAM and HAM (non-SPAM) is called ''retraining''. ==== Retraining using the Special ''Junk'' Folder (recommended) ==== {{warning}} This feature is to be available at 2012-02-04/05 If you have of create a folder named ''Junk'', then it is automatically magic: * if you drop mail into it, it is automatically retrained as SPAM * if you move it out of it, it is automatically retrained as HAM To use this folder properly, SPAMs '''must''' be delivered in the ''Junk'' folder automatically, so you can move them out in case of error. To achieve this, select the [[#Delivered with Special Header|delivery mode using a special header]], and use the provided [[#Mail Filtering|filtering system]] to drop them in the ''Junk'' folder ('''Do not use your mail software for this filtering, this is horribly inefficient and might alter the learning badly'''). {{warning}} This is gonna be the default at 2012-02-11/12 (but if you selected a mode in your settings it will not change, and if you have custom filtering rules they will not change either) ==== Retraining via Web Interface ==== Use the [https://spamfilter.duckcorp.org/ web interface] to retrain from errors in the ''History'' page. If you are using the ''quarantine'', then freed mails will automatically be retrained as HAM. ==== Retraining via Mail ==== Resend SPAMs to [mailto:dc-spam@duckcorp.org dc-spam@duckcorp.org] and HAM (non-SPAM) to [mailto:dc-ham@duckcorp.org dc-ham@duckcorp.org]. {{warning}} PLEASE TAKE CARE to use the ''resend'' function of your mailer and never use ''forward'', which would result in '''yourself''' being considered as SPAN or HAM. == Mail Filtering == With your favourite mail client, you can probably filter your mails in proper folders already. Nevertheless, this can be aa annoying operation: * blocking you mail client for a long time if you have to process plenty of mails * downloading each mail information, and sometimes content (depending on your filters), is lenghty too, and cost much bandwidth * syncing filters across your machines (home desktop, laptop, office machine…) is a pain in the ass * processing only when you're online prevents triggering actions in a timely manner (automatic redirect, vacation messages…), and running a machine 24/7 with a mail client polling new mails every 30s is not a solution We provide a much better way to do this using the [[wikipedia:Sieve_(mail_filtering_language)|SIEVE]] filters. Shortly, SIEVE is a language dedicated to expressing mail filters (also called ''rules''). Our server is able to process your mails according to these filters as soon as they arrive. You then don't have to care about them anymore, and may use light mail clients or webmails when you're not on your machine with your favourite software. === Rules Configuration === You can express sort/reject/vacation/… filters using these rules, as the capabilities are very rich. Several softwares support managing SIEVE rules: * Icedove/Thunderbird: *: using the SIEVE extension (in ''xul-ext-sieve'' Debian package), it provides a rules editor (for power-users) * Horde (Ingo): *: provides an easy to use web interface *: this webmail has been made available [https://webdesk.duckcorp.org/ here] * Squirrelmail: *: coupled with the Avelsieve extension, provides an easy to use web interface *: this webmail has been made available [https://webmail-sm.duckcorp.org/ here] * Roundcube: *: coupled with the sieverules extension, provides an easy to use web interface *: this webmail has been made available [https://webmail-rc.duckcorp.org/ here] * sieve-connect: *: provides a CLI to upload/download/activate your rules files *: this tool is available on [[Services/Shell|shell hosts]] (tell us if you know more software supporting this feature) To push your filters on the server, a dedicated protocol exists: MANAGESIEVE (TCP 4190) on ''sieve.duckcorp.org''. Our webmails are already configured to use it, but it you use sieve-connect from our hosts or your own mail software, you'll need these parameters. You can read more info about SIEVE here: * supported SIEVE features on our server: http://pigeonhole.dovecot.org/ * http://www.fastmail.fm/docs/sieve/ * http://sieve.info/ === Default Rules === There are no default rules. All your mails will end-up in your ''Inbox'' folder and you may then to sort them by yourself. {{warning}} Starting at 2012-02-11/12, the default rules will include the global ''incoming_spam'' rule, coupled with the [[#Delivered with Special Header|delivery using a special header]], in order to provide a simple default configuration for most users (but this won't affect power-users having custom rules) === Global Rules === Global rules are provided to ease configuration on specific filters. They can easily be included in your own configuration. Available rules: * ''incoming_spam'': *: SPAMs will automatically be delivered in the ''Junk'' folder *: you need to use the [[#Delivered with Special Header|delivery using a special header]] for this rule to have any effect If you write your own custom rules, here is an example on how to use one of them: require ["include"]; include :global "&lt;rule-name&gt;"; == Fetching eMails from an External Mailbox == {{todo}} == Shared/Public Folders == You may need to share mails or messages with friends or people you do stuff with (in a project or association). Depending on your needs, two solutions are possible: * share some of your own private folders, thus called ''shared folders'' * manage a special folder hierarchy, called ''public folders'' (even if they may not be accessible to everyone) Through IMAP, or our webmails internally using IMAP, it is possible to partition the folder hierarchy into ''namespaces''. Traditionally you are using the root namespace for your private folders. Additionnal namespaces can be created and will appear among your own folders or separate, depending on your mail client's choice of representation. To avoid name clashes, we decided to prefix all additionnal namespace names with a '''#'''. Since 2011-05-14, the following extra namespaces are created and reserved: * #Shared, containing all folders other users decided to share with you * #MilkyPond, containing public MP/DC information mailboxes you may subscribe at will Using IMAP, it is possible to setup rights (read only, write allowed…) to your own folders in order to share them with other users, or group of users. Public folders are owned by noone, and must be created by DC administrators ; if you need one, send us a request and we may be able to create it and delegate administration to your care (namespace name is subject to approval). Once created, public folders can be administered like shared folders. Client mail softwares support: * Horde: support namespaces, shared folders configurable via ''Options->Share Folders'' menu but no ACLs for public folders * Icedove/Thunderbird: support namespaces, shared and public folders configurable via folder selection and ''Tools->Imap-ACL'' menu action Most other softwares have namespace support only, so you should be able to use shared/public folders you have rights on but not configure them yourself (tell us if you know more software supporting this feature) == Limitations == === Maximum Mail Size === Mail you send or receive are limited to '''10MB'''. If you need to transmit much bigger data, then a mail transport is not appropriate, you'd better use a file sharing method instead. === Quotas === Even if it would be nice to live without it, we had to establish quotas to force people sort their mails out once in a while and delete useless things instead of leaving an ever-growing mess behind. The default quota is '''512MB''' which is not that big but should match needs of most users. This said, you may ask us for more and there's no reason we would refuse a reasonable demand. == Technical Details == This service is made using: * [http://www.postfix.org/ Postfix] * [http://dovecot.org/ Dovecot] * [http://dspam.sourceforge.net DSPAM] * [http://johannes.sipsolutions.net/Projects/dovecot-antispam dovecot-antispam] * [https://projects.duckcorp.org/projects/spoolinger Spoolinger] * [http://www.horde.org/ Horde] * [http://www.squirrelmail.org/ SquirrelMail] * [http://www.roundcube.net/ RoundCube] 9eb2ef5293d37ac481603bac7f9d69ca4b0f037a 367 366 2012-01-31T00:40:02Z Duck 2 /* Shared/Public Folders */ wikitext text/x-wiki {{Template:Service | description = Available services: * multiple email addresses (mailboxes+aliases or redirections) based on the ''milkypond.org'' (or maybe ''duckcorp.org'') domain * roaming accounts to be able to send emails wherever you are If you want email addresses using you own domain(s), see the [[Services/MailHosting|mail hosting service]]. | prerequisite = | account = global-reg | ipv6 = true | security_notes = Access to the mail services are fully secured, and to your data, nevertheless most mail exchange on the Internet are not. Complete security can be achieved using signed and encrypted mail (see [[wikipedia:Pretty_Good_Privacy|OpenPGP]] and [[wikipedia:S/MIME|S/MIME]]) }} == Access == === Using a Mail Reader === You can retrieve your mails, in case of a real mailbox, using either: * IMAP+TLS (TCP 143) / IMAPS (TCP 993) on imap.duckcorp.org * or POP3+TLS (TCP 110) / POP3S (TCP 995) on pop.duckcorp.org The IMAP protocol is recommended over POP3, as it provides many interesting features. If you want to download all your mails absolutely at home, loosing the ability to read your mail from anywhere on the planet, you can do that with IMAP too (look at your mail client settings). You can use our servers to send mails out too via smtp.duckcorp.org using: * SMTP+TLS (TCP 25) / SMTPS (TCP 465) * and SASL authentication === Using a Web Interface === Several [https://webmail.duckcorp.org/ webmail interfaces] are available. == Antivirus and Antispam == Mails stored on our server are checked upon arrival for viruses and SPAMs. Mail redirected to a third party mailbox are not, not to mess with the strategy of the the final destination (which could arm learning greatly). Mails being viruses are suppressed automatically upon arrival. Once in a week, an extra antivirus check is done on all hosted mailboxes, to remove viruses not detected at the time it arrived (our antivirus database is updated daily), so you may see such mail disappear from your mailbox, don't fear. SPAMs are more difficult to detect, and it is an error-prone process, so we chose to use a learning software instead of using a global database. On the bright side of things, you would never loose mails and the software should be able to learn what is a SPAM from '''your''' point of view (which has proved to differ slightly between our users), but on the grey side you will have to teach him regularly to avoid errors. When your account is created, it acts like an empty headed body letting everything through, but after a few weeks of teaching it is able to recognize most of your habits and block a lot of annoying SPAM. === Web Interface === The web interface is an easy way to view your mail history, changes your settings, and more. It is available using this URL: https://spamfilter.duckcorp.org/ ==== User Settings ==== You can yourself setup a few parameters in the ''Preferences'' page of the [https://spamfilter.duckcorp.org/ web interface], mostly: * how the system should train: ** TEFT (''On every new message scanned by the filter''): useful to learn very quickly especially on a new mailbox or when you've got tons of spam on your addresses, but you need to train it regulary (daily is better) or it will learn wrong (very quickly too !) ** TOE (''Only when the filter makes a mistake''): slow learning, but if you don't have time for training very often or go on long holidays without internet access this mode will give you a stable behavior ** TUM (''Only with new data or if the filter makes a mistake''): trade-off between the two previous modes, learn quite fast and not too demanding, adapts better to new SPAMs then TOE * filter sensitivity: you can ask the system to be more or less aggressive * message handling: see [[#Delivery Mode|delivery mode]] below * ''Disable DSPAM filtering'': you may switch off filtering at your own risk We strongly recommend using TEFT with daily training for a few weeks then switching to TUM. If you need to go away for a long time, switching to TOE is recommended. Using the quarantine feature is also a safe choice, as the web interface is quite easy to use. === Delivery Mode === ==== Quarantine ==== With the ''message handling'' setting set to ''Quarantine the message'' (see [[#User Settings|user preferences]]), then your SPAMs will not go into your mailbox but stay in this stagging area. These mails are kept by the system until you decide their fate. Through the ''Quarantine'' page of the web interface, you can list these mails and: * free legitimate mails wrongly considered as SPAM by the system * delete real SPAMs if the system was right about them (freeing useful space) In this mode, you need to flush your quarantine once in a while. ==== Delivered with Special Header (recommended) ==== With the ''message handling'' setting set to ''Deliver the message normally with a X-DSPAM-Result header'', mails are delivered normally, but with a special field added to your mail headers (not always visible depending on your mail client and its configuration). This is quite handy if you prefer SPAMs arranged in a specific folder. You may use then the provided [#Mail Filtering |filtering system] to sort them properly, or configure your eMail client. ==== Delivered with Modified Subject (not recommended) ==== With the ''message handling'' setting set to ''Tag the Subject header with'', mails are delivered normally, but with a modified title to alert you this is a SPAM (which is a tad ugly). This mode is really not clean and not recommended, but it exist for historical purposes, so you might still use it if you really wish to. === Retraining === Teaching the system what is SPAM and HAM (non-SPAM) is called ''retraining''. ==== Retraining using the Special ''Junk'' Folder (recommended) ==== {{warning}} This feature is to be available at 2012-02-04/05 If you have of create a folder named ''Junk'', then it is automatically magic: * if you drop mail into it, it is automatically retrained as SPAM * if you move it out of it, it is automatically retrained as HAM To use this folder properly, SPAMs '''must''' be delivered in the ''Junk'' folder automatically, so you can move them out in case of error. To achieve this, select the [[#Delivered with Special Header|delivery mode using a special header]], and use the provided [[#Mail Filtering|filtering system]] to drop them in the ''Junk'' folder ('''Do not use your mail software for this filtering, this is horribly inefficient and might alter the learning badly'''). {{warning}} This is gonna be the default at 2012-02-11/12 (but if you selected a mode in your settings it will not change, and if you have custom filtering rules they will not change either) ==== Retraining via Web Interface ==== Use the [https://spamfilter.duckcorp.org/ web interface] to retrain from errors in the ''History'' page. If you are using the ''quarantine'', then freed mails will automatically be retrained as HAM. ==== Retraining via Mail ==== Resend SPAMs to [mailto:dc-spam@duckcorp.org dc-spam@duckcorp.org] and HAM (non-SPAM) to [mailto:dc-ham@duckcorp.org dc-ham@duckcorp.org]. {{warning}} PLEASE TAKE CARE to use the ''resend'' function of your mailer and never use ''forward'', which would result in '''yourself''' being considered as SPAN or HAM. == Mail Filtering == With your favourite mail client, you can probably filter your mails in proper folders already. Nevertheless, this can be aa annoying operation: * blocking you mail client for a long time if you have to process plenty of mails * downloading each mail information, and sometimes content (depending on your filters), is lenghty too, and cost much bandwidth * syncing filters across your machines (home desktop, laptop, office machine…) is a pain in the ass * processing only when you're online prevents triggering actions in a timely manner (automatic redirect, vacation messages…), and running a machine 24/7 with a mail client polling new mails every 30s is not a solution We provide a much better way to do this using the [[wikipedia:Sieve_(mail_filtering_language)|SIEVE]] filters. Shortly, SIEVE is a language dedicated to expressing mail filters (also called ''rules''). Our server is able to process your mails according to these filters as soon as they arrive. You then don't have to care about them anymore, and may use light mail clients or webmails when you're not on your machine with your favourite software. === Rules Configuration === You can express sort/reject/vacation/… filters using these rules, as the capabilities are very rich. Several softwares support managing SIEVE rules: * Icedove/Thunderbird: *: using the SIEVE extension (in ''xul-ext-sieve'' Debian package), it provides a rules editor (for power-users) * Horde (Ingo): *: provides an easy to use web interface *: this webmail has been made available [https://webdesk.duckcorp.org/ here] * Squirrelmail: *: coupled with the Avelsieve extension, provides an easy to use web interface *: this webmail has been made available [https://webmail-sm.duckcorp.org/ here] * Roundcube: *: coupled with the sieverules extension, provides an easy to use web interface *: this webmail has been made available [https://webmail-rc.duckcorp.org/ here] * sieve-connect: *: provides a CLI to upload/download/activate your rules files *: this tool is available on [[Services/Shell|shell hosts]] (tell us if you know more software supporting this feature) To push your filters on the server, a dedicated protocol exists: MANAGESIEVE (TCP 4190) on ''sieve.duckcorp.org''. Our webmails are already configured to use it, but it you use sieve-connect from our hosts or your own mail software, you'll need these parameters. You can read more info about SIEVE here: * supported SIEVE features on our server: http://pigeonhole.dovecot.org/ * http://www.fastmail.fm/docs/sieve/ * http://sieve.info/ === Default Rules === There are no default rules. All your mails will end-up in your ''Inbox'' folder and you may then to sort them by yourself. {{warning}} Starting at 2012-02-11/12, the default rules will include the global ''incoming_spam'' rule, coupled with the [[#Delivered with Special Header|delivery using a special header]], in order to provide a simple default configuration for most users (but this won't affect power-users having custom rules) === Global Rules === Global rules are provided to ease configuration on specific filters. They can easily be included in your own configuration. Available rules: * ''incoming_spam'': *: SPAMs will automatically be delivered in the ''Junk'' folder *: you need to use the [[#Delivered with Special Header|delivery using a special header]] for this rule to have any effect If you write your own custom rules, here is an example on how to use one of them: require ["include"]; include :global "&lt;rule-name&gt;"; == Fetching eMails from an External Mailbox == {{todo}} == Shared/Public Folders == You may need to share mails or messages with friends or people you do stuff with (in a project or association). Depending on your needs, two solutions are possible: * share some of your own private folders, thus called ''shared folders'' * manage a special folder hierarchy, called ''public folders'' (even if they may not be accessible to everyone) *: if you need one, ask an administrator; the namespace name can be freely chosen but must be unambiguous and is subject to approval === Namespaces === Through IMAP, or our webmails internally using IMAP, it is possible to partition the folder hierarchy into ''namespaces''. Traditionally you are using the root namespace for your private folders. Additional namespaces can be created and will appear among your own folders or separate, depending on your mail client's choice of representation. To avoid name clashes, we decided to prefix all additional namespace names with a '''#'''. Since 2011-05-14, the following extra namespaces are created and reserved: * #Shared, containing all folders other users decided to share with you * #MilkyPond, containing public MP/DC informational mailboxes you may subscribe at will === Folders Permissions === Using IMAP, it is possible to setup rights (read only, write allowed…) to your own folders in order to share them with other users, or group of users. Public folders are owned by no-one, and must be created by the administrators. Once your request is accepted we will delegate its administration to your care. It can then can be managed like shared folders. === Software Support === Client mail softwares support: * Horde: *: support namespaces, shared folders configurable via ''Options->Share Folders'' menu but no ACLs for public folders * RoundCube: *: support namespaces, shared and public folders configurable via ''Settings->Folders'', selecting a folder then using the ''Sharing'' tab * Icedove/Thunderbird: *: support namespaces, shared and public folders configurable via folder selection and ''Tools->Imap-ACL'' menu action Most other softwares have namespace support only, so you should be able to use shared/public folders you have rights on but not configure them yourself (tell us if you know more software supporting this feature). == Limitations == === Maximum Mail Size === Mail you send or receive are limited to '''10MB'''. If you need to transmit much bigger data, then a mail transport is not appropriate, you'd better use a file sharing method instead. === Quotas === Even if it would be nice to live without it, we had to establish quotas to force people sort their mails out once in a while and delete useless things instead of leaving an ever-growing mess behind. The default quota is '''512MB''' which is not that big but should match needs of most users. This said, you may ask us for more and there's no reason we would refuse a reasonable demand. == Technical Details == This service is made using: * [http://www.postfix.org/ Postfix] * [http://dovecot.org/ Dovecot] * [http://dspam.sourceforge.net DSPAM] * [http://johannes.sipsolutions.net/Projects/dovecot-antispam dovecot-antispam] * [https://projects.duckcorp.org/projects/spoolinger Spoolinger] * [http://www.horde.org/ Horde] * [http://www.squirrelmail.org/ SquirrelMail] * [http://www.roundcube.net/ RoundCube] 479208dd21428f806e37a7c02b5fb042f0df1225 369 367 2012-02-04T09:54:18Z Duck 2 /* Retraining using the Special Junk Folder (recommended) */ wikitext text/x-wiki {{Template:Service | description = Available services: * multiple email addresses (mailboxes+aliases or redirections) based on the ''milkypond.org'' (or maybe ''duckcorp.org'') domain * roaming accounts to be able to send emails wherever you are If you want email addresses using you own domain(s), see the [[Services/MailHosting|mail hosting service]]. | prerequisite = | account = global-reg | ipv6 = true | security_notes = Access to the mail services are fully secured, and to your data, nevertheless most mail exchange on the Internet are not. Complete security can be achieved using signed and encrypted mail (see [[wikipedia:Pretty_Good_Privacy|OpenPGP]] and [[wikipedia:S/MIME|S/MIME]]) }} == Access == === Using a Mail Reader === You can retrieve your mails, in case of a real mailbox, using either: * IMAP+TLS (TCP 143) / IMAPS (TCP 993) on imap.duckcorp.org * or POP3+TLS (TCP 110) / POP3S (TCP 995) on pop.duckcorp.org The IMAP protocol is recommended over POP3, as it provides many interesting features. If you want to download all your mails absolutely at home, loosing the ability to read your mail from anywhere on the planet, you can do that with IMAP too (look at your mail client settings). You can use our servers to send mails out too via smtp.duckcorp.org using: * SMTP+TLS (TCP 25) / SMTPS (TCP 465) * and SASL authentication === Using a Web Interface === Several [https://webmail.duckcorp.org/ webmail interfaces] are available. == Antivirus and Antispam == Mails stored on our server are checked upon arrival for viruses and SPAMs. Mail redirected to a third party mailbox are not, not to mess with the strategy of the the final destination (which could arm learning greatly). Mails being viruses are suppressed automatically upon arrival. Once in a week, an extra antivirus check is done on all hosted mailboxes, to remove viruses not detected at the time it arrived (our antivirus database is updated daily), so you may see such mail disappear from your mailbox, don't fear. SPAMs are more difficult to detect, and it is an error-prone process, so we chose to use a learning software instead of using a global database. On the bright side of things, you would never loose mails and the software should be able to learn what is a SPAM from '''your''' point of view (which has proved to differ slightly between our users), but on the grey side you will have to teach him regularly to avoid errors. When your account is created, it acts like an empty headed body letting everything through, but after a few weeks of teaching it is able to recognize most of your habits and block a lot of annoying SPAM. === Web Interface === The web interface is an easy way to view your mail history, changes your settings, and more. It is available using this URL: https://spamfilter.duckcorp.org/ ==== User Settings ==== You can yourself setup a few parameters in the ''Preferences'' page of the [https://spamfilter.duckcorp.org/ web interface], mostly: * how the system should train: ** TEFT (''On every new message scanned by the filter''): useful to learn very quickly especially on a new mailbox or when you've got tons of spam on your addresses, but you need to train it regulary (daily is better) or it will learn wrong (very quickly too !) ** TOE (''Only when the filter makes a mistake''): slow learning, but if you don't have time for training very often or go on long holidays without internet access this mode will give you a stable behavior ** TUM (''Only with new data or if the filter makes a mistake''): trade-off between the two previous modes, learn quite fast and not too demanding, adapts better to new SPAMs then TOE * filter sensitivity: you can ask the system to be more or less aggressive * message handling: see [[#Delivery Mode|delivery mode]] below * ''Disable DSPAM filtering'': you may switch off filtering at your own risk We strongly recommend using TEFT with daily training for a few weeks then switching to TUM. If you need to go away for a long time, switching to TOE is recommended. Using the quarantine feature is also a safe choice, as the web interface is quite easy to use. === Delivery Mode === ==== Quarantine ==== With the ''message handling'' setting set to ''Quarantine the message'' (see [[#User Settings|user preferences]]), then your SPAMs will not go into your mailbox but stay in this stagging area. These mails are kept by the system until you decide their fate. Through the ''Quarantine'' page of the web interface, you can list these mails and: * free legitimate mails wrongly considered as SPAM by the system * delete real SPAMs if the system was right about them (freeing useful space) In this mode, you need to flush your quarantine once in a while. ==== Delivered with Special Header (recommended) ==== With the ''message handling'' setting set to ''Deliver the message normally with a X-DSPAM-Result header'', mails are delivered normally, but with a special field added to your mail headers (not always visible depending on your mail client and its configuration). This is quite handy if you prefer SPAMs arranged in a specific folder. You may use then the provided [#Mail Filtering |filtering system] to sort them properly, or configure your eMail client. ==== Delivered with Modified Subject (not recommended) ==== With the ''message handling'' setting set to ''Tag the Subject header with'', mails are delivered normally, but with a modified title to alert you this is a SPAM (which is a tad ugly). This mode is really not clean and not recommended, but it exist for historical purposes, so you might still use it if you really wish to. === Retraining === Teaching the system what is SPAM and HAM (non-SPAM) is called ''retraining''. ==== Retraining using the Special ''Junk'' Folder (recommended) ==== If you have of create a folder named ''Junk'', then it is automatically magic: * if you drop mail into it, it is automatically retrained as SPAM * if you move it out of it, it is automatically retrained as HAM To use this folder properly, SPAMs '''must''' be delivered in the ''Junk'' folder automatically, so you can move them out in case of error. To achieve this, select the [[#Delivered with Special Header|delivery mode using a special header]], and use the provided [[#Mail Filtering|filtering system]] to drop them in the ''Junk'' folder ('''Do not use your mail software for this filtering, this is horribly inefficient and might alter the learning badly'''). {{warning}} This is gonna be the default at 2012-02-11/12 (but if you selected a mode in your settings it will not change, and if you have custom filtering rules they will not change either) ==== Retraining via Web Interface ==== Use the [https://spamfilter.duckcorp.org/ web interface] to retrain from errors in the ''History'' page. If you are using the ''quarantine'', then freed mails will automatically be retrained as HAM. ==== Retraining via Mail ==== Resend SPAMs to [mailto:dc-spam@duckcorp.org dc-spam@duckcorp.org] and HAM (non-SPAM) to [mailto:dc-ham@duckcorp.org dc-ham@duckcorp.org]. {{warning}} PLEASE TAKE CARE to use the ''resend'' function of your mailer and never use ''forward'', which would result in '''yourself''' being considered as SPAN or HAM. == Mail Filtering == With your favourite mail client, you can probably filter your mails in proper folders already. Nevertheless, this can be aa annoying operation: * blocking you mail client for a long time if you have to process plenty of mails * downloading each mail information, and sometimes content (depending on your filters), is lenghty too, and cost much bandwidth * syncing filters across your machines (home desktop, laptop, office machine…) is a pain in the ass * processing only when you're online prevents triggering actions in a timely manner (automatic redirect, vacation messages…), and running a machine 24/7 with a mail client polling new mails every 30s is not a solution We provide a much better way to do this using the [[wikipedia:Sieve_(mail_filtering_language)|SIEVE]] filters. Shortly, SIEVE is a language dedicated to expressing mail filters (also called ''rules''). Our server is able to process your mails according to these filters as soon as they arrive. You then don't have to care about them anymore, and may use light mail clients or webmails when you're not on your machine with your favourite software. === Rules Configuration === You can express sort/reject/vacation/… filters using these rules, as the capabilities are very rich. Several softwares support managing SIEVE rules: * Icedove/Thunderbird: *: using the SIEVE extension (in ''xul-ext-sieve'' Debian package), it provides a rules editor (for power-users) * Horde (Ingo): *: provides an easy to use web interface *: this webmail has been made available [https://webdesk.duckcorp.org/ here] * Squirrelmail: *: coupled with the Avelsieve extension, provides an easy to use web interface *: this webmail has been made available [https://webmail-sm.duckcorp.org/ here] * Roundcube: *: coupled with the sieverules extension, provides an easy to use web interface *: this webmail has been made available [https://webmail-rc.duckcorp.org/ here] * sieve-connect: *: provides a CLI to upload/download/activate your rules files *: this tool is available on [[Services/Shell|shell hosts]] (tell us if you know more software supporting this feature) To push your filters on the server, a dedicated protocol exists: MANAGESIEVE (TCP 4190) on ''sieve.duckcorp.org''. Our webmails are already configured to use it, but it you use sieve-connect from our hosts or your own mail software, you'll need these parameters. You can read more info about SIEVE here: * supported SIEVE features on our server: http://pigeonhole.dovecot.org/ * http://www.fastmail.fm/docs/sieve/ * http://sieve.info/ === Default Rules === There are no default rules. All your mails will end-up in your ''Inbox'' folder and you may then to sort them by yourself. {{warning}} Starting at 2012-02-11/12, the default rules will include the global ''incoming_spam'' rule, coupled with the [[#Delivered with Special Header|delivery using a special header]], in order to provide a simple default configuration for most users (but this won't affect power-users having custom rules) === Global Rules === Global rules are provided to ease configuration on specific filters. They can easily be included in your own configuration. Available rules: * ''incoming_spam'': *: SPAMs will automatically be delivered in the ''Junk'' folder *: you need to use the [[#Delivered with Special Header|delivery using a special header]] for this rule to have any effect If you write your own custom rules, here is an example on how to use one of them: require ["include"]; include :global "&lt;rule-name&gt;"; == Fetching eMails from an External Mailbox == {{todo}} == Shared/Public Folders == You may need to share mails or messages with friends or people you do stuff with (in a project or association). Depending on your needs, two solutions are possible: * share some of your own private folders, thus called ''shared folders'' * manage a special folder hierarchy, called ''public folders'' (even if they may not be accessible to everyone) *: if you need one, ask an administrator; the namespace name can be freely chosen but must be unambiguous and is subject to approval === Namespaces === Through IMAP, or our webmails internally using IMAP, it is possible to partition the folder hierarchy into ''namespaces''. Traditionally you are using the root namespace for your private folders. Additional namespaces can be created and will appear among your own folders or separate, depending on your mail client's choice of representation. To avoid name clashes, we decided to prefix all additional namespace names with a '''#'''. Since 2011-05-14, the following extra namespaces are created and reserved: * #Shared, containing all folders other users decided to share with you * #MilkyPond, containing public MP/DC informational mailboxes you may subscribe at will === Folders Permissions === Using IMAP, it is possible to setup rights (read only, write allowed…) to your own folders in order to share them with other users, or group of users. Public folders are owned by no-one, and must be created by the administrators. Once your request is accepted we will delegate its administration to your care. It can then can be managed like shared folders. === Software Support === Client mail softwares support: * Horde: *: support namespaces, shared folders configurable via ''Options->Share Folders'' menu but no ACLs for public folders * RoundCube: *: support namespaces, shared and public folders configurable via ''Settings->Folders'', selecting a folder then using the ''Sharing'' tab * Icedove/Thunderbird: *: support namespaces, shared and public folders configurable via folder selection and ''Tools->Imap-ACL'' menu action Most other softwares have namespace support only, so you should be able to use shared/public folders you have rights on but not configure them yourself (tell us if you know more software supporting this feature). == Limitations == === Maximum Mail Size === Mail you send or receive are limited to '''10MB'''. If you need to transmit much bigger data, then a mail transport is not appropriate, you'd better use a file sharing method instead. === Quotas === Even if it would be nice to live without it, we had to establish quotas to force people sort their mails out once in a while and delete useless things instead of leaving an ever-growing mess behind. The default quota is '''512MB''' which is not that big but should match needs of most users. This said, you may ask us for more and there's no reason we would refuse a reasonable demand. == Technical Details == This service is made using: * [http://www.postfix.org/ Postfix] * [http://dovecot.org/ Dovecot] * [http://dspam.sourceforge.net DSPAM] * [http://johannes.sipsolutions.net/Projects/dovecot-antispam dovecot-antispam] * [https://projects.duckcorp.org/projects/spoolinger Spoolinger] * [http://www.horde.org/ Horde] * [http://www.squirrelmail.org/ SquirrelMail] * [http://www.roundcube.net/ RoundCube] de11d1b435e9d2aea5df319fc3b6b14d6e952670 370 369 2012-02-04T10:07:01Z Duck 2 /* Retraining using the Special Junk Folder (recommended) */ wikitext text/x-wiki {{Template:Service | description = Available services: * multiple email addresses (mailboxes+aliases or redirections) based on the ''milkypond.org'' (or maybe ''duckcorp.org'') domain * roaming accounts to be able to send emails wherever you are If you want email addresses using you own domain(s), see the [[Services/MailHosting|mail hosting service]]. | prerequisite = | account = global-reg | ipv6 = true | security_notes = Access to the mail services are fully secured, and to your data, nevertheless most mail exchange on the Internet are not. Complete security can be achieved using signed and encrypted mail (see [[wikipedia:Pretty_Good_Privacy|OpenPGP]] and [[wikipedia:S/MIME|S/MIME]]) }} == Access == === Using a Mail Reader === You can retrieve your mails, in case of a real mailbox, using either: * IMAP+TLS (TCP 143) / IMAPS (TCP 993) on imap.duckcorp.org * or POP3+TLS (TCP 110) / POP3S (TCP 995) on pop.duckcorp.org The IMAP protocol is recommended over POP3, as it provides many interesting features. If you want to download all your mails absolutely at home, loosing the ability to read your mail from anywhere on the planet, you can do that with IMAP too (look at your mail client settings). You can use our servers to send mails out too via smtp.duckcorp.org using: * SMTP+TLS (TCP 25) / SMTPS (TCP 465) * and SASL authentication === Using a Web Interface === Several [https://webmail.duckcorp.org/ webmail interfaces] are available. == Antivirus and Antispam == Mails stored on our server are checked upon arrival for viruses and SPAMs. Mail redirected to a third party mailbox are not, not to mess with the strategy of the the final destination (which could arm learning greatly). Mails being viruses are suppressed automatically upon arrival. Once in a week, an extra antivirus check is done on all hosted mailboxes, to remove viruses not detected at the time it arrived (our antivirus database is updated daily), so you may see such mail disappear from your mailbox, don't fear. SPAMs are more difficult to detect, and it is an error-prone process, so we chose to use a learning software instead of using a global database. On the bright side of things, you would never loose mails and the software should be able to learn what is a SPAM from '''your''' point of view (which has proved to differ slightly between our users), but on the grey side you will have to teach him regularly to avoid errors. When your account is created, it acts like an empty headed body letting everything through, but after a few weeks of teaching it is able to recognize most of your habits and block a lot of annoying SPAM. === Web Interface === The web interface is an easy way to view your mail history, changes your settings, and more. It is available using this URL: https://spamfilter.duckcorp.org/ ==== User Settings ==== You can yourself setup a few parameters in the ''Preferences'' page of the [https://spamfilter.duckcorp.org/ web interface], mostly: * how the system should train: ** TEFT (''On every new message scanned by the filter''): useful to learn very quickly especially on a new mailbox or when you've got tons of spam on your addresses, but you need to train it regulary (daily is better) or it will learn wrong (very quickly too !) ** TOE (''Only when the filter makes a mistake''): slow learning, but if you don't have time for training very often or go on long holidays without internet access this mode will give you a stable behavior ** TUM (''Only with new data or if the filter makes a mistake''): trade-off between the two previous modes, learn quite fast and not too demanding, adapts better to new SPAMs then TOE * filter sensitivity: you can ask the system to be more or less aggressive * message handling: see [[#Delivery Mode|delivery mode]] below * ''Disable DSPAM filtering'': you may switch off filtering at your own risk We strongly recommend using TEFT with daily training for a few weeks then switching to TUM. If you need to go away for a long time, switching to TOE is recommended. Using the quarantine feature is also a safe choice, as the web interface is quite easy to use. === Delivery Mode === ==== Quarantine ==== With the ''message handling'' setting set to ''Quarantine the message'' (see [[#User Settings|user preferences]]), then your SPAMs will not go into your mailbox but stay in this stagging area. These mails are kept by the system until you decide their fate. Through the ''Quarantine'' page of the web interface, you can list these mails and: * free legitimate mails wrongly considered as SPAM by the system * delete real SPAMs if the system was right about them (freeing useful space) In this mode, you need to flush your quarantine once in a while. ==== Delivered with Special Header (recommended) ==== With the ''message handling'' setting set to ''Deliver the message normally with a X-DSPAM-Result header'', mails are delivered normally, but with a special field added to your mail headers (not always visible depending on your mail client and its configuration). This is quite handy if you prefer SPAMs arranged in a specific folder. You may use then the provided [#Mail Filtering |filtering system] to sort them properly, or configure your eMail client. ==== Delivered with Modified Subject (not recommended) ==== With the ''message handling'' setting set to ''Tag the Subject header with'', mails are delivered normally, but with a modified title to alert you this is a SPAM (which is a tad ugly). This mode is really not clean and not recommended, but it exist for historical purposes, so you might still use it if you really wish to. === Retraining === Teaching the system what is SPAM and HAM (non-SPAM) is called ''retraining''. ==== Retraining using the Special ''Junk'' Folder (recommended) ==== If you have of create a folder named ''Junk'', then it is automatically magic: * if you drop mail into it, it is automatically retrained as SPAM * if you move it out of it, it is automatically retrained as HAM * with time, certain old mails automatically expire, see below To use this folder properly, SPAMs '''must''' be delivered in the ''Junk'' folder automatically, so you can move them out in case of error. To achieve this, select the [[#Delivered with Special Header|delivery mode using a special header]], and use the provided [[#Mail Filtering|filtering system]] to drop them in the ''Junk'' folder ('''Do not use your mail software for this filtering, this is horribly inefficient and might alter the learning badly'''). {{warning}} This is gonna be the default at 2012-02-11/12 (but if you selected a mode in your settings it will not change, and if you have custom filtering rules they will not change either) Automatic expiration logic, based on delivery time (and not the mail timestamp): * deleted mails are purged after 1 day * read mails without an important flag are purge after 7 days * unread mails without an important flag are purge after 30 days If you use the ''incoming_spam'' [[#Global_Rules|global rule]], then SPAMs newly discovered by the system are flagged as important, which means these mails will never by purged until you review it and decide to delete them or mark them as not important. Custom rules might play with this flag and achieve an automatic selection. ==== Retraining via Web Interface ==== Use the [https://spamfilter.duckcorp.org/ web interface] to retrain from errors in the ''History'' page. If you are using the ''quarantine'', then freed mails will automatically be retrained as HAM. ==== Retraining via Mail ==== Resend SPAMs to [mailto:dc-spam@duckcorp.org dc-spam@duckcorp.org] and HAM (non-SPAM) to [mailto:dc-ham@duckcorp.org dc-ham@duckcorp.org]. {{warning}} PLEASE TAKE CARE to use the ''resend'' function of your mailer and never use ''forward'', which would result in '''yourself''' being considered as SPAN or HAM. == Mail Filtering == With your favourite mail client, you can probably filter your mails in proper folders already. Nevertheless, this can be aa annoying operation: * blocking you mail client for a long time if you have to process plenty of mails * downloading each mail information, and sometimes content (depending on your filters), is lenghty too, and cost much bandwidth * syncing filters across your machines (home desktop, laptop, office machine…) is a pain in the ass * processing only when you're online prevents triggering actions in a timely manner (automatic redirect, vacation messages…), and running a machine 24/7 with a mail client polling new mails every 30s is not a solution We provide a much better way to do this using the [[wikipedia:Sieve_(mail_filtering_language)|SIEVE]] filters. Shortly, SIEVE is a language dedicated to expressing mail filters (also called ''rules''). Our server is able to process your mails according to these filters as soon as they arrive. You then don't have to care about them anymore, and may use light mail clients or webmails when you're not on your machine with your favourite software. === Rules Configuration === You can express sort/reject/vacation/… filters using these rules, as the capabilities are very rich. Several softwares support managing SIEVE rules: * Icedove/Thunderbird: *: using the SIEVE extension (in ''xul-ext-sieve'' Debian package), it provides a rules editor (for power-users) * Horde (Ingo): *: provides an easy to use web interface *: this webmail has been made available [https://webdesk.duckcorp.org/ here] * Squirrelmail: *: coupled with the Avelsieve extension, provides an easy to use web interface *: this webmail has been made available [https://webmail-sm.duckcorp.org/ here] * Roundcube: *: coupled with the sieverules extension, provides an easy to use web interface *: this webmail has been made available [https://webmail-rc.duckcorp.org/ here] * sieve-connect: *: provides a CLI to upload/download/activate your rules files *: this tool is available on [[Services/Shell|shell hosts]] (tell us if you know more software supporting this feature) To push your filters on the server, a dedicated protocol exists: MANAGESIEVE (TCP 4190) on ''sieve.duckcorp.org''. Our webmails are already configured to use it, but it you use sieve-connect from our hosts or your own mail software, you'll need these parameters. You can read more info about SIEVE here: * supported SIEVE features on our server: http://pigeonhole.dovecot.org/ * http://www.fastmail.fm/docs/sieve/ * http://sieve.info/ === Default Rules === There are no default rules. All your mails will end-up in your ''Inbox'' folder and you may then to sort them by yourself. {{warning}} Starting at 2012-02-11/12, the default rules will include the global ''incoming_spam'' rule, coupled with the [[#Delivered with Special Header|delivery using a special header]], in order to provide a simple default configuration for most users (but this won't affect power-users having custom rules) === Global Rules === Global rules are provided to ease configuration on specific filters. They can easily be included in your own configuration. Available rules: * ''incoming_spam'': *: SPAMs will automatically be delivered in the ''Junk'' folder *: you need to use the [[#Delivered with Special Header|delivery using a special header]] for this rule to have any effect If you write your own custom rules, here is an example on how to use one of them: require ["include"]; include :global "&lt;rule-name&gt;"; == Fetching eMails from an External Mailbox == {{todo}} == Shared/Public Folders == You may need to share mails or messages with friends or people you do stuff with (in a project or association). Depending on your needs, two solutions are possible: * share some of your own private folders, thus called ''shared folders'' * manage a special folder hierarchy, called ''public folders'' (even if they may not be accessible to everyone) *: if you need one, ask an administrator; the namespace name can be freely chosen but must be unambiguous and is subject to approval === Namespaces === Through IMAP, or our webmails internally using IMAP, it is possible to partition the folder hierarchy into ''namespaces''. Traditionally you are using the root namespace for your private folders. Additional namespaces can be created and will appear among your own folders or separate, depending on your mail client's choice of representation. To avoid name clashes, we decided to prefix all additional namespace names with a '''#'''. Since 2011-05-14, the following extra namespaces are created and reserved: * #Shared, containing all folders other users decided to share with you * #MilkyPond, containing public MP/DC informational mailboxes you may subscribe at will === Folders Permissions === Using IMAP, it is possible to setup rights (read only, write allowed…) to your own folders in order to share them with other users, or group of users. Public folders are owned by no-one, and must be created by the administrators. Once your request is accepted we will delegate its administration to your care. It can then can be managed like shared folders. === Software Support === Client mail softwares support: * Horde: *: support namespaces, shared folders configurable via ''Options->Share Folders'' menu but no ACLs for public folders * RoundCube: *: support namespaces, shared and public folders configurable via ''Settings->Folders'', selecting a folder then using the ''Sharing'' tab * Icedove/Thunderbird: *: support namespaces, shared and public folders configurable via folder selection and ''Tools->Imap-ACL'' menu action Most other softwares have namespace support only, so you should be able to use shared/public folders you have rights on but not configure them yourself (tell us if you know more software supporting this feature). == Limitations == === Maximum Mail Size === Mail you send or receive are limited to '''10MB'''. If you need to transmit much bigger data, then a mail transport is not appropriate, you'd better use a file sharing method instead. === Quotas === Even if it would be nice to live without it, we had to establish quotas to force people sort their mails out once in a while and delete useless things instead of leaving an ever-growing mess behind. The default quota is '''512MB''' which is not that big but should match needs of most users. This said, you may ask us for more and there's no reason we would refuse a reasonable demand. == Technical Details == This service is made using: * [http://www.postfix.org/ Postfix] * [http://dovecot.org/ Dovecot] * [http://dspam.sourceforge.net DSPAM] * [http://johannes.sipsolutions.net/Projects/dovecot-antispam dovecot-antispam] * [https://projects.duckcorp.org/projects/spoolinger Spoolinger] * [http://www.horde.org/ Horde] * [http://www.squirrelmail.org/ SquirrelMail] * [http://www.roundcube.net/ RoundCube] 00df820caaa0f0160f65e5896c69264f19b7ef1c 371 370 2012-02-04T10:07:37Z Duck 2 /* Global Rules */ wikitext text/x-wiki {{Template:Service | description = Available services: * multiple email addresses (mailboxes+aliases or redirections) based on the ''milkypond.org'' (or maybe ''duckcorp.org'') domain * roaming accounts to be able to send emails wherever you are If you want email addresses using you own domain(s), see the [[Services/MailHosting|mail hosting service]]. | prerequisite = | account = global-reg | ipv6 = true | security_notes = Access to the mail services are fully secured, and to your data, nevertheless most mail exchange on the Internet are not. Complete security can be achieved using signed and encrypted mail (see [[wikipedia:Pretty_Good_Privacy|OpenPGP]] and [[wikipedia:S/MIME|S/MIME]]) }} == Access == === Using a Mail Reader === You can retrieve your mails, in case of a real mailbox, using either: * IMAP+TLS (TCP 143) / IMAPS (TCP 993) on imap.duckcorp.org * or POP3+TLS (TCP 110) / POP3S (TCP 995) on pop.duckcorp.org The IMAP protocol is recommended over POP3, as it provides many interesting features. If you want to download all your mails absolutely at home, loosing the ability to read your mail from anywhere on the planet, you can do that with IMAP too (look at your mail client settings). You can use our servers to send mails out too via smtp.duckcorp.org using: * SMTP+TLS (TCP 25) / SMTPS (TCP 465) * and SASL authentication === Using a Web Interface === Several [https://webmail.duckcorp.org/ webmail interfaces] are available. == Antivirus and Antispam == Mails stored on our server are checked upon arrival for viruses and SPAMs. Mail redirected to a third party mailbox are not, not to mess with the strategy of the the final destination (which could arm learning greatly). Mails being viruses are suppressed automatically upon arrival. Once in a week, an extra antivirus check is done on all hosted mailboxes, to remove viruses not detected at the time it arrived (our antivirus database is updated daily), so you may see such mail disappear from your mailbox, don't fear. SPAMs are more difficult to detect, and it is an error-prone process, so we chose to use a learning software instead of using a global database. On the bright side of things, you would never loose mails and the software should be able to learn what is a SPAM from '''your''' point of view (which has proved to differ slightly between our users), but on the grey side you will have to teach him regularly to avoid errors. When your account is created, it acts like an empty headed body letting everything through, but after a few weeks of teaching it is able to recognize most of your habits and block a lot of annoying SPAM. === Web Interface === The web interface is an easy way to view your mail history, changes your settings, and more. It is available using this URL: https://spamfilter.duckcorp.org/ ==== User Settings ==== You can yourself setup a few parameters in the ''Preferences'' page of the [https://spamfilter.duckcorp.org/ web interface], mostly: * how the system should train: ** TEFT (''On every new message scanned by the filter''): useful to learn very quickly especially on a new mailbox or when you've got tons of spam on your addresses, but you need to train it regulary (daily is better) or it will learn wrong (very quickly too !) ** TOE (''Only when the filter makes a mistake''): slow learning, but if you don't have time for training very often or go on long holidays without internet access this mode will give you a stable behavior ** TUM (''Only with new data or if the filter makes a mistake''): trade-off between the two previous modes, learn quite fast and not too demanding, adapts better to new SPAMs then TOE * filter sensitivity: you can ask the system to be more or less aggressive * message handling: see [[#Delivery Mode|delivery mode]] below * ''Disable DSPAM filtering'': you may switch off filtering at your own risk We strongly recommend using TEFT with daily training for a few weeks then switching to TUM. If you need to go away for a long time, switching to TOE is recommended. Using the quarantine feature is also a safe choice, as the web interface is quite easy to use. === Delivery Mode === ==== Quarantine ==== With the ''message handling'' setting set to ''Quarantine the message'' (see [[#User Settings|user preferences]]), then your SPAMs will not go into your mailbox but stay in this stagging area. These mails are kept by the system until you decide their fate. Through the ''Quarantine'' page of the web interface, you can list these mails and: * free legitimate mails wrongly considered as SPAM by the system * delete real SPAMs if the system was right about them (freeing useful space) In this mode, you need to flush your quarantine once in a while. ==== Delivered with Special Header (recommended) ==== With the ''message handling'' setting set to ''Deliver the message normally with a X-DSPAM-Result header'', mails are delivered normally, but with a special field added to your mail headers (not always visible depending on your mail client and its configuration). This is quite handy if you prefer SPAMs arranged in a specific folder. You may use then the provided [#Mail Filtering |filtering system] to sort them properly, or configure your eMail client. ==== Delivered with Modified Subject (not recommended) ==== With the ''message handling'' setting set to ''Tag the Subject header with'', mails are delivered normally, but with a modified title to alert you this is a SPAM (which is a tad ugly). This mode is really not clean and not recommended, but it exist for historical purposes, so you might still use it if you really wish to. === Retraining === Teaching the system what is SPAM and HAM (non-SPAM) is called ''retraining''. ==== Retraining using the Special ''Junk'' Folder (recommended) ==== If you have of create a folder named ''Junk'', then it is automatically magic: * if you drop mail into it, it is automatically retrained as SPAM * if you move it out of it, it is automatically retrained as HAM * with time, certain old mails automatically expire, see below To use this folder properly, SPAMs '''must''' be delivered in the ''Junk'' folder automatically, so you can move them out in case of error. To achieve this, select the [[#Delivered with Special Header|delivery mode using a special header]], and use the provided [[#Mail Filtering|filtering system]] to drop them in the ''Junk'' folder ('''Do not use your mail software for this filtering, this is horribly inefficient and might alter the learning badly'''). {{warning}} This is gonna be the default at 2012-02-11/12 (but if you selected a mode in your settings it will not change, and if you have custom filtering rules they will not change either) Automatic expiration logic, based on delivery time (and not the mail timestamp): * deleted mails are purged after 1 day * read mails without an important flag are purge after 7 days * unread mails without an important flag are purge after 30 days If you use the ''incoming_spam'' [[#Global_Rules|global rule]], then SPAMs newly discovered by the system are flagged as important, which means these mails will never by purged until you review it and decide to delete them or mark them as not important. Custom rules might play with this flag and achieve an automatic selection. ==== Retraining via Web Interface ==== Use the [https://spamfilter.duckcorp.org/ web interface] to retrain from errors in the ''History'' page. If you are using the ''quarantine'', then freed mails will automatically be retrained as HAM. ==== Retraining via Mail ==== Resend SPAMs to [mailto:dc-spam@duckcorp.org dc-spam@duckcorp.org] and HAM (non-SPAM) to [mailto:dc-ham@duckcorp.org dc-ham@duckcorp.org]. {{warning}} PLEASE TAKE CARE to use the ''resend'' function of your mailer and never use ''forward'', which would result in '''yourself''' being considered as SPAN or HAM. == Mail Filtering == With your favourite mail client, you can probably filter your mails in proper folders already. Nevertheless, this can be aa annoying operation: * blocking you mail client for a long time if you have to process plenty of mails * downloading each mail information, and sometimes content (depending on your filters), is lenghty too, and cost much bandwidth * syncing filters across your machines (home desktop, laptop, office machine…) is a pain in the ass * processing only when you're online prevents triggering actions in a timely manner (automatic redirect, vacation messages…), and running a machine 24/7 with a mail client polling new mails every 30s is not a solution We provide a much better way to do this using the [[wikipedia:Sieve_(mail_filtering_language)|SIEVE]] filters. Shortly, SIEVE is a language dedicated to expressing mail filters (also called ''rules''). Our server is able to process your mails according to these filters as soon as they arrive. You then don't have to care about them anymore, and may use light mail clients or webmails when you're not on your machine with your favourite software. === Rules Configuration === You can express sort/reject/vacation/… filters using these rules, as the capabilities are very rich. Several softwares support managing SIEVE rules: * Icedove/Thunderbird: *: using the SIEVE extension (in ''xul-ext-sieve'' Debian package), it provides a rules editor (for power-users) * Horde (Ingo): *: provides an easy to use web interface *: this webmail has been made available [https://webdesk.duckcorp.org/ here] * Squirrelmail: *: coupled with the Avelsieve extension, provides an easy to use web interface *: this webmail has been made available [https://webmail-sm.duckcorp.org/ here] * Roundcube: *: coupled with the sieverules extension, provides an easy to use web interface *: this webmail has been made available [https://webmail-rc.duckcorp.org/ here] * sieve-connect: *: provides a CLI to upload/download/activate your rules files *: this tool is available on [[Services/Shell|shell hosts]] (tell us if you know more software supporting this feature) To push your filters on the server, a dedicated protocol exists: MANAGESIEVE (TCP 4190) on ''sieve.duckcorp.org''. Our webmails are already configured to use it, but it you use sieve-connect from our hosts or your own mail software, you'll need these parameters. You can read more info about SIEVE here: * supported SIEVE features on our server: http://pigeonhole.dovecot.org/ * http://www.fastmail.fm/docs/sieve/ * http://sieve.info/ === Default Rules === There are no default rules. All your mails will end-up in your ''Inbox'' folder and you may then to sort them by yourself. {{warning}} Starting at 2012-02-11/12, the default rules will include the global ''incoming_spam'' rule, coupled with the [[#Delivered with Special Header|delivery using a special header]], in order to provide a simple default configuration for most users (but this won't affect power-users having custom rules) === Global Rules === Global rules are provided to ease configuration on specific filters. They can easily be included in your own configuration. Available rules: * ''incoming_spam'': *: SPAMs will automatically be delivered in the ''Junk'' folder and marked as ''important'' *: you need to use the [[#Delivered with Special Header|delivery using a special header]] for this rule to have any effect If you write your own custom rules, here is an example on how to use one of them: require ["include"]; include :global "&lt;rule-name&gt;"; == Fetching eMails from an External Mailbox == {{todo}} == Shared/Public Folders == You may need to share mails or messages with friends or people you do stuff with (in a project or association). Depending on your needs, two solutions are possible: * share some of your own private folders, thus called ''shared folders'' * manage a special folder hierarchy, called ''public folders'' (even if they may not be accessible to everyone) *: if you need one, ask an administrator; the namespace name can be freely chosen but must be unambiguous and is subject to approval === Namespaces === Through IMAP, or our webmails internally using IMAP, it is possible to partition the folder hierarchy into ''namespaces''. Traditionally you are using the root namespace for your private folders. Additional namespaces can be created and will appear among your own folders or separate, depending on your mail client's choice of representation. To avoid name clashes, we decided to prefix all additional namespace names with a '''#'''. Since 2011-05-14, the following extra namespaces are created and reserved: * #Shared, containing all folders other users decided to share with you * #MilkyPond, containing public MP/DC informational mailboxes you may subscribe at will === Folders Permissions === Using IMAP, it is possible to setup rights (read only, write allowed…) to your own folders in order to share them with other users, or group of users. Public folders are owned by no-one, and must be created by the administrators. Once your request is accepted we will delegate its administration to your care. It can then can be managed like shared folders. === Software Support === Client mail softwares support: * Horde: *: support namespaces, shared folders configurable via ''Options->Share Folders'' menu but no ACLs for public folders * RoundCube: *: support namespaces, shared and public folders configurable via ''Settings->Folders'', selecting a folder then using the ''Sharing'' tab * Icedove/Thunderbird: *: support namespaces, shared and public folders configurable via folder selection and ''Tools->Imap-ACL'' menu action Most other softwares have namespace support only, so you should be able to use shared/public folders you have rights on but not configure them yourself (tell us if you know more software supporting this feature). == Limitations == === Maximum Mail Size === Mail you send or receive are limited to '''10MB'''. If you need to transmit much bigger data, then a mail transport is not appropriate, you'd better use a file sharing method instead. === Quotas === Even if it would be nice to live without it, we had to establish quotas to force people sort their mails out once in a while and delete useless things instead of leaving an ever-growing mess behind. The default quota is '''512MB''' which is not that big but should match needs of most users. This said, you may ask us for more and there's no reason we would refuse a reasonable demand. == Technical Details == This service is made using: * [http://www.postfix.org/ Postfix] * [http://dovecot.org/ Dovecot] * [http://dspam.sourceforge.net DSPAM] * [http://johannes.sipsolutions.net/Projects/dovecot-antispam dovecot-antispam] * [https://projects.duckcorp.org/projects/spoolinger Spoolinger] * [http://www.horde.org/ Horde] * [http://www.squirrelmail.org/ SquirrelMail] * [http://www.roundcube.net/ RoundCube] cec0435937c125a5864b3006bdd24f466b5b7a5a 372 371 2012-02-11T14:34:43Z Duck 2 /* Retraining */ wikitext text/x-wiki {{Template:Service | description = Available services: * multiple email addresses (mailboxes+aliases or redirections) based on the ''milkypond.org'' (or maybe ''duckcorp.org'') domain * roaming accounts to be able to send emails wherever you are If you want email addresses using you own domain(s), see the [[Services/MailHosting|mail hosting service]]. | prerequisite = | account = global-reg | ipv6 = true | security_notes = Access to the mail services are fully secured, and to your data, nevertheless most mail exchange on the Internet are not. Complete security can be achieved using signed and encrypted mail (see [[wikipedia:Pretty_Good_Privacy|OpenPGP]] and [[wikipedia:S/MIME|S/MIME]]) }} == Access == === Using a Mail Reader === You can retrieve your mails, in case of a real mailbox, using either: * IMAP+TLS (TCP 143) / IMAPS (TCP 993) on imap.duckcorp.org * or POP3+TLS (TCP 110) / POP3S (TCP 995) on pop.duckcorp.org The IMAP protocol is recommended over POP3, as it provides many interesting features. If you want to download all your mails absolutely at home, loosing the ability to read your mail from anywhere on the planet, you can do that with IMAP too (look at your mail client settings). You can use our servers to send mails out too via smtp.duckcorp.org using: * SMTP+TLS (TCP 25) / SMTPS (TCP 465) * and SASL authentication === Using a Web Interface === Several [https://webmail.duckcorp.org/ webmail interfaces] are available. == Antivirus and Antispam == Mails stored on our server are checked upon arrival for viruses and SPAMs. Mail redirected to a third party mailbox are not, not to mess with the strategy of the the final destination (which could arm learning greatly). Mails being viruses are suppressed automatically upon arrival. Once in a week, an extra antivirus check is done on all hosted mailboxes, to remove viruses not detected at the time it arrived (our antivirus database is updated daily), so you may see such mail disappear from your mailbox, don't fear. SPAMs are more difficult to detect, and it is an error-prone process, so we chose to use a learning software instead of using a global database. On the bright side of things, you would never loose mails and the software should be able to learn what is a SPAM from '''your''' point of view (which has proved to differ slightly between our users), but on the grey side you will have to teach him regularly to avoid errors. When your account is created, it acts like an empty headed body letting everything through, but after a few weeks of teaching it is able to recognize most of your habits and block a lot of annoying SPAM. === Web Interface === The web interface is an easy way to view your mail history, changes your settings, and more. It is available using this URL: https://spamfilter.duckcorp.org/ ==== User Settings ==== You can yourself setup a few parameters in the ''Preferences'' page of the [https://spamfilter.duckcorp.org/ web interface], mostly: * how the system should train: ** TEFT (''On every new message scanned by the filter''): useful to learn very quickly especially on a new mailbox or when you've got tons of spam on your addresses, but you need to train it regulary (daily is better) or it will learn wrong (very quickly too !) ** TOE (''Only when the filter makes a mistake''): slow learning, but if you don't have time for training very often or go on long holidays without internet access this mode will give you a stable behavior ** TUM (''Only with new data or if the filter makes a mistake''): trade-off between the two previous modes, learn quite fast and not too demanding, adapts better to new SPAMs then TOE * filter sensitivity: you can ask the system to be more or less aggressive * message handling: see [[#Delivery Mode|delivery mode]] below * ''Disable DSPAM filtering'': you may switch off filtering at your own risk We strongly recommend using TEFT with daily training for a few weeks then switching to TUM. If you need to go away for a long time, switching to TOE is recommended. Using the quarantine feature is also a safe choice, as the web interface is quite easy to use. === Delivery Mode === ==== Quarantine ==== With the ''message handling'' setting set to ''Quarantine the message'' (see [[#User Settings|user preferences]]), then your SPAMs will not go into your mailbox but stay in this stagging area. These mails are kept by the system until you decide their fate. Through the ''Quarantine'' page of the web interface, you can list these mails and: * free legitimate mails wrongly considered as SPAM by the system * delete real SPAMs if the system was right about them (freeing useful space) In this mode, you need to flush your quarantine once in a while. ==== Delivered with Special Header (recommended) ==== With the ''message handling'' setting set to ''Deliver the message normally with a X-DSPAM-Result header'', mails are delivered normally, but with a special field added to your mail headers (not always visible depending on your mail client and its configuration). This is quite handy if you prefer SPAMs arranged in a specific folder. You may use then the provided [#Mail Filtering |filtering system] to sort them properly, or configure your eMail client. ==== Delivered with Modified Subject (not recommended) ==== With the ''message handling'' setting set to ''Tag the Subject header with'', mails are delivered normally, but with a modified title to alert you this is a SPAM (which is a tad ugly). This mode is really not clean and not recommended, but it exist for historical purposes, so you might still use it if you really wish to. === Retraining === Teaching the system what is SPAM and HAM (non-SPAM) is called ''retraining''. ==== Retraining using the Special ''Junk'' Folder (default, recommended) ==== If you have of create a folder named ''Junk'', then it is automatically magic: * if you drop mail into it, it is automatically retrained as SPAM * if you move it out of it, it is automatically retrained as HAM * with time, certain old mails automatically expire, see below To use this folder properly, SPAMs '''must''' be delivered in the ''Junk'' folder automatically, so you can move them out in case of error. If using the default settings, you just need to subscribe to this folder in your mail software (this folder is always auto-created). If you are using different setting, you need to select the [[#Delivered with Special Header|delivery mode using a special header]], and use the provided [[#Mail Filtering|filtering system]] to drop them in the ''Junk'' folder ('''Do not use your mail software for this filtering, this is horribly inefficient and might alter the learning badly'''). Automatic expiration logic, based on delivery time (and not the mail timestamp): * deleted mails are purged after 1 day * read mails without an important flag are purge after 7 days * unread mails without an important flag are purge after 30 days If you use the ''incoming_spam'' [[#Global_Rules|global rule]], then SPAMs newly discovered by the system are flagged as important, which means these mails will never by purged until you review it and decide to delete them or mark them as not important. Custom rules might play with this flag and achieve an automatic selection. ==== Retraining via Web Interface ==== Use the [https://spamfilter.duckcorp.org/ web interface] to retrain from errors in the ''History'' page. If you are using the ''quarantine'', then freed mails will automatically be retrained as HAM. ==== Retraining via Mail ==== Resend SPAMs to [mailto:dc-spam@duckcorp.org dc-spam@duckcorp.org] and HAM (non-SPAM) to [mailto:dc-ham@duckcorp.org dc-ham@duckcorp.org]. {{warning}} PLEASE TAKE CARE to use the ''resend'' function of your mailer and never use ''forward'', which would result in '''yourself''' being considered as SPAN or HAM. == Mail Filtering == With your favourite mail client, you can probably filter your mails in proper folders already. Nevertheless, this can be aa annoying operation: * blocking you mail client for a long time if you have to process plenty of mails * downloading each mail information, and sometimes content (depending on your filters), is lenghty too, and cost much bandwidth * syncing filters across your machines (home desktop, laptop, office machine…) is a pain in the ass * processing only when you're online prevents triggering actions in a timely manner (automatic redirect, vacation messages…), and running a machine 24/7 with a mail client polling new mails every 30s is not a solution We provide a much better way to do this using the [[wikipedia:Sieve_(mail_filtering_language)|SIEVE]] filters. Shortly, SIEVE is a language dedicated to expressing mail filters (also called ''rules''). Our server is able to process your mails according to these filters as soon as they arrive. You then don't have to care about them anymore, and may use light mail clients or webmails when you're not on your machine with your favourite software. === Rules Configuration === You can express sort/reject/vacation/… filters using these rules, as the capabilities are very rich. Several softwares support managing SIEVE rules: * Icedove/Thunderbird: *: using the SIEVE extension (in ''xul-ext-sieve'' Debian package), it provides a rules editor (for power-users) * Horde (Ingo): *: provides an easy to use web interface *: this webmail has been made available [https://webdesk.duckcorp.org/ here] * Squirrelmail: *: coupled with the Avelsieve extension, provides an easy to use web interface *: this webmail has been made available [https://webmail-sm.duckcorp.org/ here] * Roundcube: *: coupled with the sieverules extension, provides an easy to use web interface *: this webmail has been made available [https://webmail-rc.duckcorp.org/ here] * sieve-connect: *: provides a CLI to upload/download/activate your rules files *: this tool is available on [[Services/Shell|shell hosts]] (tell us if you know more software supporting this feature) To push your filters on the server, a dedicated protocol exists: MANAGESIEVE (TCP 4190) on ''sieve.duckcorp.org''. Our webmails are already configured to use it, but it you use sieve-connect from our hosts or your own mail software, you'll need these parameters. You can read more info about SIEVE here: * supported SIEVE features on our server: http://pigeonhole.dovecot.org/ * http://www.fastmail.fm/docs/sieve/ * http://sieve.info/ === Default Rules === There are no default rules. All your mails will end-up in your ''Inbox'' folder and you may then to sort them by yourself. {{warning}} Starting at 2012-02-11/12, the default rules will include the global ''incoming_spam'' rule, coupled with the [[#Delivered with Special Header|delivery using a special header]], in order to provide a simple default configuration for most users (but this won't affect power-users having custom rules) === Global Rules === Global rules are provided to ease configuration on specific filters. They can easily be included in your own configuration. Available rules: * ''incoming_spam'': *: SPAMs will automatically be delivered in the ''Junk'' folder and marked as ''important'' *: you need to use the [[#Delivered with Special Header|delivery using a special header]] for this rule to have any effect If you write your own custom rules, here is an example on how to use one of them: require ["include"]; include :global "&lt;rule-name&gt;"; == Fetching eMails from an External Mailbox == {{todo}} == Shared/Public Folders == You may need to share mails or messages with friends or people you do stuff with (in a project or association). Depending on your needs, two solutions are possible: * share some of your own private folders, thus called ''shared folders'' * manage a special folder hierarchy, called ''public folders'' (even if they may not be accessible to everyone) *: if you need one, ask an administrator; the namespace name can be freely chosen but must be unambiguous and is subject to approval === Namespaces === Through IMAP, or our webmails internally using IMAP, it is possible to partition the folder hierarchy into ''namespaces''. Traditionally you are using the root namespace for your private folders. Additional namespaces can be created and will appear among your own folders or separate, depending on your mail client's choice of representation. To avoid name clashes, we decided to prefix all additional namespace names with a '''#'''. Since 2011-05-14, the following extra namespaces are created and reserved: * #Shared, containing all folders other users decided to share with you * #MilkyPond, containing public MP/DC informational mailboxes you may subscribe at will === Folders Permissions === Using IMAP, it is possible to setup rights (read only, write allowed…) to your own folders in order to share them with other users, or group of users. Public folders are owned by no-one, and must be created by the administrators. Once your request is accepted we will delegate its administration to your care. It can then can be managed like shared folders. === Software Support === Client mail softwares support: * Horde: *: support namespaces, shared folders configurable via ''Options->Share Folders'' menu but no ACLs for public folders * RoundCube: *: support namespaces, shared and public folders configurable via ''Settings->Folders'', selecting a folder then using the ''Sharing'' tab * Icedove/Thunderbird: *: support namespaces, shared and public folders configurable via folder selection and ''Tools->Imap-ACL'' menu action Most other softwares have namespace support only, so you should be able to use shared/public folders you have rights on but not configure them yourself (tell us if you know more software supporting this feature). == Limitations == === Maximum Mail Size === Mail you send or receive are limited to '''10MB'''. If you need to transmit much bigger data, then a mail transport is not appropriate, you'd better use a file sharing method instead. === Quotas === Even if it would be nice to live without it, we had to establish quotas to force people sort their mails out once in a while and delete useless things instead of leaving an ever-growing mess behind. The default quota is '''512MB''' which is not that big but should match needs of most users. This said, you may ask us for more and there's no reason we would refuse a reasonable demand. == Technical Details == This service is made using: * [http://www.postfix.org/ Postfix] * [http://dovecot.org/ Dovecot] * [http://dspam.sourceforge.net DSPAM] * [http://johannes.sipsolutions.net/Projects/dovecot-antispam dovecot-antispam] * [https://projects.duckcorp.org/projects/spoolinger Spoolinger] * [http://www.horde.org/ Horde] * [http://www.squirrelmail.org/ SquirrelMail] * [http://www.roundcube.net/ RoundCube] 7e6885bb8aa03bf73224802e6d1910e6640b9e06 373 372 2012-02-11T14:39:08Z Duck 2 /* Default Rules */ wikitext text/x-wiki {{Template:Service | description = Available services: * multiple email addresses (mailboxes+aliases or redirections) based on the ''milkypond.org'' (or maybe ''duckcorp.org'') domain * roaming accounts to be able to send emails wherever you are If you want email addresses using you own domain(s), see the [[Services/MailHosting|mail hosting service]]. | prerequisite = | account = global-reg | ipv6 = true | security_notes = Access to the mail services are fully secured, and to your data, nevertheless most mail exchange on the Internet are not. Complete security can be achieved using signed and encrypted mail (see [[wikipedia:Pretty_Good_Privacy|OpenPGP]] and [[wikipedia:S/MIME|S/MIME]]) }} == Access == === Using a Mail Reader === You can retrieve your mails, in case of a real mailbox, using either: * IMAP+TLS (TCP 143) / IMAPS (TCP 993) on imap.duckcorp.org * or POP3+TLS (TCP 110) / POP3S (TCP 995) on pop.duckcorp.org The IMAP protocol is recommended over POP3, as it provides many interesting features. If you want to download all your mails absolutely at home, loosing the ability to read your mail from anywhere on the planet, you can do that with IMAP too (look at your mail client settings). You can use our servers to send mails out too via smtp.duckcorp.org using: * SMTP+TLS (TCP 25) / SMTPS (TCP 465) * and SASL authentication === Using a Web Interface === Several [https://webmail.duckcorp.org/ webmail interfaces] are available. == Antivirus and Antispam == Mails stored on our server are checked upon arrival for viruses and SPAMs. Mail redirected to a third party mailbox are not, not to mess with the strategy of the the final destination (which could arm learning greatly). Mails being viruses are suppressed automatically upon arrival. Once in a week, an extra antivirus check is done on all hosted mailboxes, to remove viruses not detected at the time it arrived (our antivirus database is updated daily), so you may see such mail disappear from your mailbox, don't fear. SPAMs are more difficult to detect, and it is an error-prone process, so we chose to use a learning software instead of using a global database. On the bright side of things, you would never loose mails and the software should be able to learn what is a SPAM from '''your''' point of view (which has proved to differ slightly between our users), but on the grey side you will have to teach him regularly to avoid errors. When your account is created, it acts like an empty headed body letting everything through, but after a few weeks of teaching it is able to recognize most of your habits and block a lot of annoying SPAM. === Web Interface === The web interface is an easy way to view your mail history, changes your settings, and more. It is available using this URL: https://spamfilter.duckcorp.org/ ==== User Settings ==== You can yourself setup a few parameters in the ''Preferences'' page of the [https://spamfilter.duckcorp.org/ web interface], mostly: * how the system should train: ** TEFT (''On every new message scanned by the filter''): useful to learn very quickly especially on a new mailbox or when you've got tons of spam on your addresses, but you need to train it regulary (daily is better) or it will learn wrong (very quickly too !) ** TOE (''Only when the filter makes a mistake''): slow learning, but if you don't have time for training very often or go on long holidays without internet access this mode will give you a stable behavior ** TUM (''Only with new data or if the filter makes a mistake''): trade-off between the two previous modes, learn quite fast and not too demanding, adapts better to new SPAMs then TOE * filter sensitivity: you can ask the system to be more or less aggressive * message handling: see [[#Delivery Mode|delivery mode]] below * ''Disable DSPAM filtering'': you may switch off filtering at your own risk We strongly recommend using TEFT with daily training for a few weeks then switching to TUM. If you need to go away for a long time, switching to TOE is recommended. Using the quarantine feature is also a safe choice, as the web interface is quite easy to use. === Delivery Mode === ==== Quarantine ==== With the ''message handling'' setting set to ''Quarantine the message'' (see [[#User Settings|user preferences]]), then your SPAMs will not go into your mailbox but stay in this stagging area. These mails are kept by the system until you decide their fate. Through the ''Quarantine'' page of the web interface, you can list these mails and: * free legitimate mails wrongly considered as SPAM by the system * delete real SPAMs if the system was right about them (freeing useful space) In this mode, you need to flush your quarantine once in a while. ==== Delivered with Special Header (recommended) ==== With the ''message handling'' setting set to ''Deliver the message normally with a X-DSPAM-Result header'', mails are delivered normally, but with a special field added to your mail headers (not always visible depending on your mail client and its configuration). This is quite handy if you prefer SPAMs arranged in a specific folder. You may use then the provided [#Mail Filtering |filtering system] to sort them properly, or configure your eMail client. ==== Delivered with Modified Subject (not recommended) ==== With the ''message handling'' setting set to ''Tag the Subject header with'', mails are delivered normally, but with a modified title to alert you this is a SPAM (which is a tad ugly). This mode is really not clean and not recommended, but it exist for historical purposes, so you might still use it if you really wish to. === Retraining === Teaching the system what is SPAM and HAM (non-SPAM) is called ''retraining''. ==== Retraining using the Special ''Junk'' Folder (default, recommended) ==== If you have of create a folder named ''Junk'', then it is automatically magic: * if you drop mail into it, it is automatically retrained as SPAM * if you move it out of it, it is automatically retrained as HAM * with time, certain old mails automatically expire, see below To use this folder properly, SPAMs '''must''' be delivered in the ''Junk'' folder automatically, so you can move them out in case of error. If using the default settings, you just need to subscribe to this folder in your mail software (this folder is always auto-created). If you are using different setting, you need to select the [[#Delivered with Special Header|delivery mode using a special header]], and use the provided [[#Mail Filtering|filtering system]] to drop them in the ''Junk'' folder ('''Do not use your mail software for this filtering, this is horribly inefficient and might alter the learning badly'''). Automatic expiration logic, based on delivery time (and not the mail timestamp): * deleted mails are purged after 1 day * read mails without an important flag are purge after 7 days * unread mails without an important flag are purge after 30 days If you use the ''incoming_spam'' [[#Global_Rules|global rule]], then SPAMs newly discovered by the system are flagged as important, which means these mails will never by purged until you review it and decide to delete them or mark them as not important. Custom rules might play with this flag and achieve an automatic selection. ==== Retraining via Web Interface ==== Use the [https://spamfilter.duckcorp.org/ web interface] to retrain from errors in the ''History'' page. If you are using the ''quarantine'', then freed mails will automatically be retrained as HAM. ==== Retraining via Mail ==== Resend SPAMs to [mailto:dc-spam@duckcorp.org dc-spam@duckcorp.org] and HAM (non-SPAM) to [mailto:dc-ham@duckcorp.org dc-ham@duckcorp.org]. {{warning}} PLEASE TAKE CARE to use the ''resend'' function of your mailer and never use ''forward'', which would result in '''yourself''' being considered as SPAN or HAM. == Mail Filtering == With your favourite mail client, you can probably filter your mails in proper folders already. Nevertheless, this can be aa annoying operation: * blocking you mail client for a long time if you have to process plenty of mails * downloading each mail information, and sometimes content (depending on your filters), is lenghty too, and cost much bandwidth * syncing filters across your machines (home desktop, laptop, office machine…) is a pain in the ass * processing only when you're online prevents triggering actions in a timely manner (automatic redirect, vacation messages…), and running a machine 24/7 with a mail client polling new mails every 30s is not a solution We provide a much better way to do this using the [[wikipedia:Sieve_(mail_filtering_language)|SIEVE]] filters. Shortly, SIEVE is a language dedicated to expressing mail filters (also called ''rules''). Our server is able to process your mails according to these filters as soon as they arrive. You then don't have to care about them anymore, and may use light mail clients or webmails when you're not on your machine with your favourite software. === Rules Configuration === You can express sort/reject/vacation/… filters using these rules, as the capabilities are very rich. Several softwares support managing SIEVE rules: * Icedove/Thunderbird: *: using the SIEVE extension (in ''xul-ext-sieve'' Debian package), it provides a rules editor (for power-users) * Horde (Ingo): *: provides an easy to use web interface *: this webmail has been made available [https://webdesk.duckcorp.org/ here] * Squirrelmail: *: coupled with the Avelsieve extension, provides an easy to use web interface *: this webmail has been made available [https://webmail-sm.duckcorp.org/ here] * Roundcube: *: coupled with the sieverules extension, provides an easy to use web interface *: this webmail has been made available [https://webmail-rc.duckcorp.org/ here] * sieve-connect: *: provides a CLI to upload/download/activate your rules files *: this tool is available on [[Services/Shell|shell hosts]] (tell us if you know more software supporting this feature) To push your filters on the server, a dedicated protocol exists: MANAGESIEVE (TCP 4190) on ''sieve.duckcorp.org''. Our webmails are already configured to use it, but it you use sieve-connect from our hosts or your own mail software, you'll need these parameters. You can read more info about SIEVE here: * supported SIEVE features on our server: http://pigeonhole.dovecot.org/ * http://www.fastmail.fm/docs/sieve/ * http://sieve.info/ === Default Rules === The default settings are to use the global ''incoming_spam'' rule and the [[#Delivered with Special Header|delivery using a special header]], in order to provide a simple default configuration for most users. All other mails will end-up in your ''Inbox'' folder and you may then sort them by yourself. If you create your own rules, the default rules won't apply anymore, so power-users can replace the default behavior completely to achieve what they really need. === Global Rules === Global rules are provided to ease configuration on specific filters. They can easily be included in your own configuration. Available rules: * ''incoming_spam'': *: SPAMs will automatically be delivered in the ''Junk'' folder and marked as ''important'' *: you need to use the [[#Delivered with Special Header|delivery using a special header]] for this rule to have any effect If you write your own custom rules, here is an example on how to use one of them: require ["include"]; include :global "&lt;rule-name&gt;"; == Fetching eMails from an External Mailbox == {{todo}} == Shared/Public Folders == You may need to share mails or messages with friends or people you do stuff with (in a project or association). Depending on your needs, two solutions are possible: * share some of your own private folders, thus called ''shared folders'' * manage a special folder hierarchy, called ''public folders'' (even if they may not be accessible to everyone) *: if you need one, ask an administrator; the namespace name can be freely chosen but must be unambiguous and is subject to approval === Namespaces === Through IMAP, or our webmails internally using IMAP, it is possible to partition the folder hierarchy into ''namespaces''. Traditionally you are using the root namespace for your private folders. Additional namespaces can be created and will appear among your own folders or separate, depending on your mail client's choice of representation. To avoid name clashes, we decided to prefix all additional namespace names with a '''#'''. Since 2011-05-14, the following extra namespaces are created and reserved: * #Shared, containing all folders other users decided to share with you * #MilkyPond, containing public MP/DC informational mailboxes you may subscribe at will === Folders Permissions === Using IMAP, it is possible to setup rights (read only, write allowed…) to your own folders in order to share them with other users, or group of users. Public folders are owned by no-one, and must be created by the administrators. Once your request is accepted we will delegate its administration to your care. It can then can be managed like shared folders. === Software Support === Client mail softwares support: * Horde: *: support namespaces, shared folders configurable via ''Options->Share Folders'' menu but no ACLs for public folders * RoundCube: *: support namespaces, shared and public folders configurable via ''Settings->Folders'', selecting a folder then using the ''Sharing'' tab * Icedove/Thunderbird: *: support namespaces, shared and public folders configurable via folder selection and ''Tools->Imap-ACL'' menu action Most other softwares have namespace support only, so you should be able to use shared/public folders you have rights on but not configure them yourself (tell us if you know more software supporting this feature). == Limitations == === Maximum Mail Size === Mail you send or receive are limited to '''10MB'''. If you need to transmit much bigger data, then a mail transport is not appropriate, you'd better use a file sharing method instead. === Quotas === Even if it would be nice to live without it, we had to establish quotas to force people sort their mails out once in a while and delete useless things instead of leaving an ever-growing mess behind. The default quota is '''512MB''' which is not that big but should match needs of most users. This said, you may ask us for more and there's no reason we would refuse a reasonable demand. == Technical Details == This service is made using: * [http://www.postfix.org/ Postfix] * [http://dovecot.org/ Dovecot] * [http://dspam.sourceforge.net DSPAM] * [http://johannes.sipsolutions.net/Projects/dovecot-antispam dovecot-antispam] * [https://projects.duckcorp.org/projects/spoolinger Spoolinger] * [http://www.horde.org/ Horde] * [http://www.squirrelmail.org/ SquirrelMail] * [http://www.roundcube.net/ RoundCube] bcd2807c954a595affb9ea84c91e38722622ead9 374 373 2012-02-11T14:40:06Z Duck 2 /* Default Rules */ wikitext text/x-wiki {{Template:Service | description = Available services: * multiple email addresses (mailboxes+aliases or redirections) based on the ''milkypond.org'' (or maybe ''duckcorp.org'') domain * roaming accounts to be able to send emails wherever you are If you want email addresses using you own domain(s), see the [[Services/MailHosting|mail hosting service]]. | prerequisite = | account = global-reg | ipv6 = true | security_notes = Access to the mail services are fully secured, and to your data, nevertheless most mail exchange on the Internet are not. Complete security can be achieved using signed and encrypted mail (see [[wikipedia:Pretty_Good_Privacy|OpenPGP]] and [[wikipedia:S/MIME|S/MIME]]) }} == Access == === Using a Mail Reader === You can retrieve your mails, in case of a real mailbox, using either: * IMAP+TLS (TCP 143) / IMAPS (TCP 993) on imap.duckcorp.org * or POP3+TLS (TCP 110) / POP3S (TCP 995) on pop.duckcorp.org The IMAP protocol is recommended over POP3, as it provides many interesting features. If you want to download all your mails absolutely at home, loosing the ability to read your mail from anywhere on the planet, you can do that with IMAP too (look at your mail client settings). You can use our servers to send mails out too via smtp.duckcorp.org using: * SMTP+TLS (TCP 25) / SMTPS (TCP 465) * and SASL authentication === Using a Web Interface === Several [https://webmail.duckcorp.org/ webmail interfaces] are available. == Antivirus and Antispam == Mails stored on our server are checked upon arrival for viruses and SPAMs. Mail redirected to a third party mailbox are not, not to mess with the strategy of the the final destination (which could arm learning greatly). Mails being viruses are suppressed automatically upon arrival. Once in a week, an extra antivirus check is done on all hosted mailboxes, to remove viruses not detected at the time it arrived (our antivirus database is updated daily), so you may see such mail disappear from your mailbox, don't fear. SPAMs are more difficult to detect, and it is an error-prone process, so we chose to use a learning software instead of using a global database. On the bright side of things, you would never loose mails and the software should be able to learn what is a SPAM from '''your''' point of view (which has proved to differ slightly between our users), but on the grey side you will have to teach him regularly to avoid errors. When your account is created, it acts like an empty headed body letting everything through, but after a few weeks of teaching it is able to recognize most of your habits and block a lot of annoying SPAM. === Web Interface === The web interface is an easy way to view your mail history, changes your settings, and more. It is available using this URL: https://spamfilter.duckcorp.org/ ==== User Settings ==== You can yourself setup a few parameters in the ''Preferences'' page of the [https://spamfilter.duckcorp.org/ web interface], mostly: * how the system should train: ** TEFT (''On every new message scanned by the filter''): useful to learn very quickly especially on a new mailbox or when you've got tons of spam on your addresses, but you need to train it regulary (daily is better) or it will learn wrong (very quickly too !) ** TOE (''Only when the filter makes a mistake''): slow learning, but if you don't have time for training very often or go on long holidays without internet access this mode will give you a stable behavior ** TUM (''Only with new data or if the filter makes a mistake''): trade-off between the two previous modes, learn quite fast and not too demanding, adapts better to new SPAMs then TOE * filter sensitivity: you can ask the system to be more or less aggressive * message handling: see [[#Delivery Mode|delivery mode]] below * ''Disable DSPAM filtering'': you may switch off filtering at your own risk We strongly recommend using TEFT with daily training for a few weeks then switching to TUM. If you need to go away for a long time, switching to TOE is recommended. Using the quarantine feature is also a safe choice, as the web interface is quite easy to use. === Delivery Mode === ==== Quarantine ==== With the ''message handling'' setting set to ''Quarantine the message'' (see [[#User Settings|user preferences]]), then your SPAMs will not go into your mailbox but stay in this stagging area. These mails are kept by the system until you decide their fate. Through the ''Quarantine'' page of the web interface, you can list these mails and: * free legitimate mails wrongly considered as SPAM by the system * delete real SPAMs if the system was right about them (freeing useful space) In this mode, you need to flush your quarantine once in a while. ==== Delivered with Special Header (recommended) ==== With the ''message handling'' setting set to ''Deliver the message normally with a X-DSPAM-Result header'', mails are delivered normally, but with a special field added to your mail headers (not always visible depending on your mail client and its configuration). This is quite handy if you prefer SPAMs arranged in a specific folder. You may use then the provided [#Mail Filtering |filtering system] to sort them properly, or configure your eMail client. ==== Delivered with Modified Subject (not recommended) ==== With the ''message handling'' setting set to ''Tag the Subject header with'', mails are delivered normally, but with a modified title to alert you this is a SPAM (which is a tad ugly). This mode is really not clean and not recommended, but it exist for historical purposes, so you might still use it if you really wish to. === Retraining === Teaching the system what is SPAM and HAM (non-SPAM) is called ''retraining''. ==== Retraining using the Special ''Junk'' Folder (default, recommended) ==== If you have of create a folder named ''Junk'', then it is automatically magic: * if you drop mail into it, it is automatically retrained as SPAM * if you move it out of it, it is automatically retrained as HAM * with time, certain old mails automatically expire, see below To use this folder properly, SPAMs '''must''' be delivered in the ''Junk'' folder automatically, so you can move them out in case of error. If using the default settings, you just need to subscribe to this folder in your mail software (this folder is always auto-created). If you are using different setting, you need to select the [[#Delivered with Special Header|delivery mode using a special header]], and use the provided [[#Mail Filtering|filtering system]] to drop them in the ''Junk'' folder ('''Do not use your mail software for this filtering, this is horribly inefficient and might alter the learning badly'''). Automatic expiration logic, based on delivery time (and not the mail timestamp): * deleted mails are purged after 1 day * read mails without an important flag are purge after 7 days * unread mails without an important flag are purge after 30 days If you use the ''incoming_spam'' [[#Global_Rules|global rule]], then SPAMs newly discovered by the system are flagged as important, which means these mails will never by purged until you review it and decide to delete them or mark them as not important. Custom rules might play with this flag and achieve an automatic selection. ==== Retraining via Web Interface ==== Use the [https://spamfilter.duckcorp.org/ web interface] to retrain from errors in the ''History'' page. If you are using the ''quarantine'', then freed mails will automatically be retrained as HAM. ==== Retraining via Mail ==== Resend SPAMs to [mailto:dc-spam@duckcorp.org dc-spam@duckcorp.org] and HAM (non-SPAM) to [mailto:dc-ham@duckcorp.org dc-ham@duckcorp.org]. {{warning}} PLEASE TAKE CARE to use the ''resend'' function of your mailer and never use ''forward'', which would result in '''yourself''' being considered as SPAN or HAM. == Mail Filtering == With your favourite mail client, you can probably filter your mails in proper folders already. Nevertheless, this can be aa annoying operation: * blocking you mail client for a long time if you have to process plenty of mails * downloading each mail information, and sometimes content (depending on your filters), is lenghty too, and cost much bandwidth * syncing filters across your machines (home desktop, laptop, office machine…) is a pain in the ass * processing only when you're online prevents triggering actions in a timely manner (automatic redirect, vacation messages…), and running a machine 24/7 with a mail client polling new mails every 30s is not a solution We provide a much better way to do this using the [[wikipedia:Sieve_(mail_filtering_language)|SIEVE]] filters. Shortly, SIEVE is a language dedicated to expressing mail filters (also called ''rules''). Our server is able to process your mails according to these filters as soon as they arrive. You then don't have to care about them anymore, and may use light mail clients or webmails when you're not on your machine with your favourite software. === Rules Configuration === You can express sort/reject/vacation/… filters using these rules, as the capabilities are very rich. Several softwares support managing SIEVE rules: * Icedove/Thunderbird: *: using the SIEVE extension (in ''xul-ext-sieve'' Debian package), it provides a rules editor (for power-users) * Horde (Ingo): *: provides an easy to use web interface *: this webmail has been made available [https://webdesk.duckcorp.org/ here] * Squirrelmail: *: coupled with the Avelsieve extension, provides an easy to use web interface *: this webmail has been made available [https://webmail-sm.duckcorp.org/ here] * Roundcube: *: coupled with the sieverules extension, provides an easy to use web interface *: this webmail has been made available [https://webmail-rc.duckcorp.org/ here] * sieve-connect: *: provides a CLI to upload/download/activate your rules files *: this tool is available on [[Services/Shell|shell hosts]] (tell us if you know more software supporting this feature) To push your filters on the server, a dedicated protocol exists: MANAGESIEVE (TCP 4190) on ''sieve.duckcorp.org''. Our webmails are already configured to use it, but it you use sieve-connect from our hosts or your own mail software, you'll need these parameters. You can read more info about SIEVE here: * supported SIEVE features on our server: http://pigeonhole.dovecot.org/ * http://www.fastmail.fm/docs/sieve/ * http://sieve.info/ === Default Rules === The default settings (since 2112-02-11) are to use the global ''incoming_spam'' rule and the [[#Delivered with Special Header|delivery using a special header]], in order to provide a simple default configuration for most users. All other mails will end-up in your ''Inbox'' folder and you may then sort them by yourself. If you create your own rules, the default rules won't apply anymore, so power-users can replace the default behavior completely to achieve what they really need. === Global Rules === Global rules are provided to ease configuration on specific filters. They can easily be included in your own configuration. Available rules: * ''incoming_spam'': *: SPAMs will automatically be delivered in the ''Junk'' folder and marked as ''important'' *: you need to use the [[#Delivered with Special Header|delivery using a special header]] for this rule to have any effect If you write your own custom rules, here is an example on how to use one of them: require ["include"]; include :global "&lt;rule-name&gt;"; == Fetching eMails from an External Mailbox == {{todo}} == Shared/Public Folders == You may need to share mails or messages with friends or people you do stuff with (in a project or association). Depending on your needs, two solutions are possible: * share some of your own private folders, thus called ''shared folders'' * manage a special folder hierarchy, called ''public folders'' (even if they may not be accessible to everyone) *: if you need one, ask an administrator; the namespace name can be freely chosen but must be unambiguous and is subject to approval === Namespaces === Through IMAP, or our webmails internally using IMAP, it is possible to partition the folder hierarchy into ''namespaces''. Traditionally you are using the root namespace for your private folders. Additional namespaces can be created and will appear among your own folders or separate, depending on your mail client's choice of representation. To avoid name clashes, we decided to prefix all additional namespace names with a '''#'''. Since 2011-05-14, the following extra namespaces are created and reserved: * #Shared, containing all folders other users decided to share with you * #MilkyPond, containing public MP/DC informational mailboxes you may subscribe at will === Folders Permissions === Using IMAP, it is possible to setup rights (read only, write allowed…) to your own folders in order to share them with other users, or group of users. Public folders are owned by no-one, and must be created by the administrators. Once your request is accepted we will delegate its administration to your care. It can then can be managed like shared folders. === Software Support === Client mail softwares support: * Horde: *: support namespaces, shared folders configurable via ''Options->Share Folders'' menu but no ACLs for public folders * RoundCube: *: support namespaces, shared and public folders configurable via ''Settings->Folders'', selecting a folder then using the ''Sharing'' tab * Icedove/Thunderbird: *: support namespaces, shared and public folders configurable via folder selection and ''Tools->Imap-ACL'' menu action Most other softwares have namespace support only, so you should be able to use shared/public folders you have rights on but not configure them yourself (tell us if you know more software supporting this feature). == Limitations == === Maximum Mail Size === Mail you send or receive are limited to '''10MB'''. If you need to transmit much bigger data, then a mail transport is not appropriate, you'd better use a file sharing method instead. === Quotas === Even if it would be nice to live without it, we had to establish quotas to force people sort their mails out once in a while and delete useless things instead of leaving an ever-growing mess behind. The default quota is '''512MB''' which is not that big but should match needs of most users. This said, you may ask us for more and there's no reason we would refuse a reasonable demand. == Technical Details == This service is made using: * [http://www.postfix.org/ Postfix] * [http://dovecot.org/ Dovecot] * [http://dspam.sourceforge.net DSPAM] * [http://johannes.sipsolutions.net/Projects/dovecot-antispam dovecot-antispam] * [https://projects.duckcorp.org/projects/spoolinger Spoolinger] * [http://www.horde.org/ Horde] * [http://www.squirrelmail.org/ SquirrelMail] * [http://www.roundcube.net/ RoundCube] 4bd8be843bc3ee6ed6b28c26e1795c2415302d97 375 374 2012-02-11T14:40:33Z Duck 2 /* Delivery Mode */ wikitext text/x-wiki {{Template:Service | description = Available services: * multiple email addresses (mailboxes+aliases or redirections) based on the ''milkypond.org'' (or maybe ''duckcorp.org'') domain * roaming accounts to be able to send emails wherever you are If you want email addresses using you own domain(s), see the [[Services/MailHosting|mail hosting service]]. | prerequisite = | account = global-reg | ipv6 = true | security_notes = Access to the mail services are fully secured, and to your data, nevertheless most mail exchange on the Internet are not. Complete security can be achieved using signed and encrypted mail (see [[wikipedia:Pretty_Good_Privacy|OpenPGP]] and [[wikipedia:S/MIME|S/MIME]]) }} == Access == === Using a Mail Reader === You can retrieve your mails, in case of a real mailbox, using either: * IMAP+TLS (TCP 143) / IMAPS (TCP 993) on imap.duckcorp.org * or POP3+TLS (TCP 110) / POP3S (TCP 995) on pop.duckcorp.org The IMAP protocol is recommended over POP3, as it provides many interesting features. If you want to download all your mails absolutely at home, loosing the ability to read your mail from anywhere on the planet, you can do that with IMAP too (look at your mail client settings). You can use our servers to send mails out too via smtp.duckcorp.org using: * SMTP+TLS (TCP 25) / SMTPS (TCP 465) * and SASL authentication === Using a Web Interface === Several [https://webmail.duckcorp.org/ webmail interfaces] are available. == Antivirus and Antispam == Mails stored on our server are checked upon arrival for viruses and SPAMs. Mail redirected to a third party mailbox are not, not to mess with the strategy of the the final destination (which could arm learning greatly). Mails being viruses are suppressed automatically upon arrival. Once in a week, an extra antivirus check is done on all hosted mailboxes, to remove viruses not detected at the time it arrived (our antivirus database is updated daily), so you may see such mail disappear from your mailbox, don't fear. SPAMs are more difficult to detect, and it is an error-prone process, so we chose to use a learning software instead of using a global database. On the bright side of things, you would never loose mails and the software should be able to learn what is a SPAM from '''your''' point of view (which has proved to differ slightly between our users), but on the grey side you will have to teach him regularly to avoid errors. When your account is created, it acts like an empty headed body letting everything through, but after a few weeks of teaching it is able to recognize most of your habits and block a lot of annoying SPAM. === Web Interface === The web interface is an easy way to view your mail history, changes your settings, and more. It is available using this URL: https://spamfilter.duckcorp.org/ ==== User Settings ==== You can yourself setup a few parameters in the ''Preferences'' page of the [https://spamfilter.duckcorp.org/ web interface], mostly: * how the system should train: ** TEFT (''On every new message scanned by the filter''): useful to learn very quickly especially on a new mailbox or when you've got tons of spam on your addresses, but you need to train it regulary (daily is better) or it will learn wrong (very quickly too !) ** TOE (''Only when the filter makes a mistake''): slow learning, but if you don't have time for training very often or go on long holidays without internet access this mode will give you a stable behavior ** TUM (''Only with new data or if the filter makes a mistake''): trade-off between the two previous modes, learn quite fast and not too demanding, adapts better to new SPAMs then TOE * filter sensitivity: you can ask the system to be more or less aggressive * message handling: see [[#Delivery Mode|delivery mode]] below * ''Disable DSPAM filtering'': you may switch off filtering at your own risk We strongly recommend using TEFT with daily training for a few weeks then switching to TUM. If you need to go away for a long time, switching to TOE is recommended. Using the quarantine feature is also a safe choice, as the web interface is quite easy to use. === Delivery Mode === ==== Quarantine ==== With the ''message handling'' setting set to ''Quarantine the message'' (see [[#User Settings|user preferences]]), then your SPAMs will not go into your mailbox but stay in this stagging area. These mails are kept by the system until you decide their fate. Through the ''Quarantine'' page of the web interface, you can list these mails and: * free legitimate mails wrongly considered as SPAM by the system * delete real SPAMs if the system was right about them (freeing useful space) In this mode, you need to flush your quarantine once in a while. ==== Delivered with Special Header (default, recommended) ==== With the ''message handling'' setting set to ''Deliver the message normally with a X-DSPAM-Result header'', mails are delivered normally, but with a special field added to your mail headers (not always visible depending on your mail client and its configuration). This is quite handy if you prefer SPAMs arranged in a specific folder. You may use then the provided [#Mail Filtering |filtering system] to sort them properly, or configure your eMail client. ==== Delivered with Modified Subject (not recommended) ==== With the ''message handling'' setting set to ''Tag the Subject header with'', mails are delivered normally, but with a modified title to alert you this is a SPAM (which is a tad ugly). This mode is really not clean and not recommended, but it exist for historical purposes, so you might still use it if you really wish to. === Retraining === Teaching the system what is SPAM and HAM (non-SPAM) is called ''retraining''. ==== Retraining using the Special ''Junk'' Folder (default, recommended) ==== If you have of create a folder named ''Junk'', then it is automatically magic: * if you drop mail into it, it is automatically retrained as SPAM * if you move it out of it, it is automatically retrained as HAM * with time, certain old mails automatically expire, see below To use this folder properly, SPAMs '''must''' be delivered in the ''Junk'' folder automatically, so you can move them out in case of error. If using the default settings, you just need to subscribe to this folder in your mail software (this folder is always auto-created). If you are using different setting, you need to select the [[#Delivered with Special Header|delivery mode using a special header]], and use the provided [[#Mail Filtering|filtering system]] to drop them in the ''Junk'' folder ('''Do not use your mail software for this filtering, this is horribly inefficient and might alter the learning badly'''). Automatic expiration logic, based on delivery time (and not the mail timestamp): * deleted mails are purged after 1 day * read mails without an important flag are purge after 7 days * unread mails without an important flag are purge after 30 days If you use the ''incoming_spam'' [[#Global_Rules|global rule]], then SPAMs newly discovered by the system are flagged as important, which means these mails will never by purged until you review it and decide to delete them or mark them as not important. Custom rules might play with this flag and achieve an automatic selection. ==== Retraining via Web Interface ==== Use the [https://spamfilter.duckcorp.org/ web interface] to retrain from errors in the ''History'' page. If you are using the ''quarantine'', then freed mails will automatically be retrained as HAM. ==== Retraining via Mail ==== Resend SPAMs to [mailto:dc-spam@duckcorp.org dc-spam@duckcorp.org] and HAM (non-SPAM) to [mailto:dc-ham@duckcorp.org dc-ham@duckcorp.org]. {{warning}} PLEASE TAKE CARE to use the ''resend'' function of your mailer and never use ''forward'', which would result in '''yourself''' being considered as SPAN or HAM. == Mail Filtering == With your favourite mail client, you can probably filter your mails in proper folders already. Nevertheless, this can be aa annoying operation: * blocking you mail client for a long time if you have to process plenty of mails * downloading each mail information, and sometimes content (depending on your filters), is lenghty too, and cost much bandwidth * syncing filters across your machines (home desktop, laptop, office machine…) is a pain in the ass * processing only when you're online prevents triggering actions in a timely manner (automatic redirect, vacation messages…), and running a machine 24/7 with a mail client polling new mails every 30s is not a solution We provide a much better way to do this using the [[wikipedia:Sieve_(mail_filtering_language)|SIEVE]] filters. Shortly, SIEVE is a language dedicated to expressing mail filters (also called ''rules''). Our server is able to process your mails according to these filters as soon as they arrive. You then don't have to care about them anymore, and may use light mail clients or webmails when you're not on your machine with your favourite software. === Rules Configuration === You can express sort/reject/vacation/… filters using these rules, as the capabilities are very rich. Several softwares support managing SIEVE rules: * Icedove/Thunderbird: *: using the SIEVE extension (in ''xul-ext-sieve'' Debian package), it provides a rules editor (for power-users) * Horde (Ingo): *: provides an easy to use web interface *: this webmail has been made available [https://webdesk.duckcorp.org/ here] * Squirrelmail: *: coupled with the Avelsieve extension, provides an easy to use web interface *: this webmail has been made available [https://webmail-sm.duckcorp.org/ here] * Roundcube: *: coupled with the sieverules extension, provides an easy to use web interface *: this webmail has been made available [https://webmail-rc.duckcorp.org/ here] * sieve-connect: *: provides a CLI to upload/download/activate your rules files *: this tool is available on [[Services/Shell|shell hosts]] (tell us if you know more software supporting this feature) To push your filters on the server, a dedicated protocol exists: MANAGESIEVE (TCP 4190) on ''sieve.duckcorp.org''. Our webmails are already configured to use it, but it you use sieve-connect from our hosts or your own mail software, you'll need these parameters. You can read more info about SIEVE here: * supported SIEVE features on our server: http://pigeonhole.dovecot.org/ * http://www.fastmail.fm/docs/sieve/ * http://sieve.info/ === Default Rules === The default settings (since 2112-02-11) are to use the global ''incoming_spam'' rule and the [[#Delivered with Special Header|delivery using a special header]], in order to provide a simple default configuration for most users. All other mails will end-up in your ''Inbox'' folder and you may then sort them by yourself. If you create your own rules, the default rules won't apply anymore, so power-users can replace the default behavior completely to achieve what they really need. === Global Rules === Global rules are provided to ease configuration on specific filters. They can easily be included in your own configuration. Available rules: * ''incoming_spam'': *: SPAMs will automatically be delivered in the ''Junk'' folder and marked as ''important'' *: you need to use the [[#Delivered with Special Header|delivery using a special header]] for this rule to have any effect If you write your own custom rules, here is an example on how to use one of them: require ["include"]; include :global "&lt;rule-name&gt;"; == Fetching eMails from an External Mailbox == {{todo}} == Shared/Public Folders == You may need to share mails or messages with friends or people you do stuff with (in a project or association). Depending on your needs, two solutions are possible: * share some of your own private folders, thus called ''shared folders'' * manage a special folder hierarchy, called ''public folders'' (even if they may not be accessible to everyone) *: if you need one, ask an administrator; the namespace name can be freely chosen but must be unambiguous and is subject to approval === Namespaces === Through IMAP, or our webmails internally using IMAP, it is possible to partition the folder hierarchy into ''namespaces''. Traditionally you are using the root namespace for your private folders. Additional namespaces can be created and will appear among your own folders or separate, depending on your mail client's choice of representation. To avoid name clashes, we decided to prefix all additional namespace names with a '''#'''. Since 2011-05-14, the following extra namespaces are created and reserved: * #Shared, containing all folders other users decided to share with you * #MilkyPond, containing public MP/DC informational mailboxes you may subscribe at will === Folders Permissions === Using IMAP, it is possible to setup rights (read only, write allowed…) to your own folders in order to share them with other users, or group of users. Public folders are owned by no-one, and must be created by the administrators. Once your request is accepted we will delegate its administration to your care. It can then can be managed like shared folders. === Software Support === Client mail softwares support: * Horde: *: support namespaces, shared folders configurable via ''Options->Share Folders'' menu but no ACLs for public folders * RoundCube: *: support namespaces, shared and public folders configurable via ''Settings->Folders'', selecting a folder then using the ''Sharing'' tab * Icedove/Thunderbird: *: support namespaces, shared and public folders configurable via folder selection and ''Tools->Imap-ACL'' menu action Most other softwares have namespace support only, so you should be able to use shared/public folders you have rights on but not configure them yourself (tell us if you know more software supporting this feature). == Limitations == === Maximum Mail Size === Mail you send or receive are limited to '''10MB'''. If you need to transmit much bigger data, then a mail transport is not appropriate, you'd better use a file sharing method instead. === Quotas === Even if it would be nice to live without it, we had to establish quotas to force people sort their mails out once in a while and delete useless things instead of leaving an ever-growing mess behind. The default quota is '''512MB''' which is not that big but should match needs of most users. This said, you may ask us for more and there's no reason we would refuse a reasonable demand. == Technical Details == This service is made using: * [http://www.postfix.org/ Postfix] * [http://dovecot.org/ Dovecot] * [http://dspam.sourceforge.net DSPAM] * [http://johannes.sipsolutions.net/Projects/dovecot-antispam dovecot-antispam] * [https://projects.duckcorp.org/projects/spoolinger Spoolinger] * [http://www.horde.org/ Horde] * [http://www.squirrelmail.org/ SquirrelMail] * [http://www.roundcube.net/ RoundCube] 588bb91809a18c9e9a280105b2dd806bca2e8220 0 65 368 2012-02-02T01:03:29Z Duck 2 Created page with "{{Template:Service | description = News feeds reader through a web interface. | prerequisite = | account = global | ipv6 = true | security_notes = This service is secure except i…" wikitext text/x-wiki {{Template:Service | description = News feeds reader through a web interface. | prerequisite = | account = global | ipv6 = true | security_notes = This service is secure except if you don't check the website certificate properly (like on Android, see below). }} == Access == === Using a Web Browser === You can connect to the web interface using the following URL: https://gossip.duckcorp.org/ On a Web Phone you'd better use this URL instead: https://gossip.duckcorp.org/mobile/ === Using the Android Application === You need the official ttrss application, see: http://tt-rss.org/redmine/projects/tt-rss-android/wiki (two other unofficial applications exist, but they don't work well) You need to connect once through your web browser to activate the web API, which is needed by the Android application: look in Preferences -> Advanced -> Enable external API. Then you can configure your application: * URL: https://gossip.duckcorp.org/ * Login/Password * Accept any SSL certificate: true (unfortunately managing certificates in Android is a nightmare :-/) * HTTP authentication Login/Password: repeat Login/Password === Sharing News === You can share interesting news: * by mail (but there is no link to your address book) * by URL: these ones are public, meaning there is no need to authenticate to use them, so you can give them away to anybody == Technical Details == This service is made using: * [http://tt-rss.org/ Tiny Tiny RSS] d2166ab824df12d512c7b6c3f8755379087493f7 405 368 2013-07-08T04:52:37Z Boutil 15 https://gossip.duckcorp.org/mobile/ gives a 404 error. wikitext text/x-wiki {{Template:Service | description = News feeds reader through a web interface. | prerequisite = | account = global | ipv6 = true | security_notes = This service is secure except if you don't check the website certificate properly (like on Android, see below). }} == Access == === Using a Web Browser === You can connect to the web interface using the following URL: https://gossip.duckcorp.org/ === Using the Android Application === You need the official ttrss application, see: http://tt-rss.org/redmine/projects/tt-rss-android/wiki (two other unofficial applications exist, but they don't work well) You need to connect once through your web browser to activate the web API, which is needed by the Android application: look in Preferences -> Advanced -> Enable external API. Then you can configure your application: * URL: https://gossip.duckcorp.org/ * Login/Password * Accept any SSL certificate: true (unfortunately managing certificates in Android is a nightmare :-/) * HTTP authentication Login/Password: repeat Login/Password === Sharing News === You can share interesting news: * by mail (but there is no link to your address book) * by URL: these ones are public, meaning there is no need to authenticate to use them, so you can give them away to anybody == Technical Details == This service is made using: * [http://tt-rss.org/ Tiny Tiny RSS] 26f1b71bc36f3b573ee9ba63658d114633135924 0 39 376 351 2012-02-17T15:56:00Z Duck 2 /* TODO */ wikitext text/x-wiki Here is a short overview of the services provided by DuckCorp. Our services are supervised and important data are [[Services/Backup|saved regularly]]. {{warning}} [[Services/Security|Notes about security !]] {| class="wikitable" style="text-align: center; width: 100%;" |+ Available Services |- ! Category !! colspan="2" | Service !! Access !! Description |- | rowspan="7" | Communication || rowspan="2" | Mail || [[Services/Mail|eMails]] || users || style="text-align: left;" | Mail boxes with anti-spam/anti-virus, filtering…, or mail redirections |- | [[Services/ML|Mailing-Lists]] || users || style="text-align: left;" | Distribution lists for mails |- | rowspan="3" | IRC || [[Services/IRC|IRC Network]] || public || style="text-align: left;" | MilkyPond Chat Network using a dedicated software or a Web-interface |- | [[Services/IRC-Bouncer|IRC Bouncer]] || users || style="text-align: left;" | IRC proxy (IRC server relaying IRC communications, keeping connections open and remembering logs) |- | [[Services/IRC-IM-GW|IRC to IM gateway]] || users || style="text-align: left;" | Communication to multiple instant messaging networks through a unified IRC-like interface |- | colspan="2" | [[Services/XMPP|XMPP (Jabber)]] || users || style="text-align: left;" | Global Chat Network (inter-communication between many [[wikipedia:Xmpp#History|well-known public IM services]]) |- | colspan="2" | [[Services/Tribioune|Triboune Libre]] || public || style="text-align: left;" | MilkyPond Web-chat system inspired by [http://linuxfr.org/board the famous one] on [http://linuxfr.org/ Linuxfr.org] |- | rowspan="5" | Sharing || colspan="2" | [[Services/Gallery|Media Gallery]] || public/users || style="text-align: left;" | Photo and video gallery |- | colspan="2" | [[Services/Wiki|Wiki]] || public/users || style="text-align: left;" | Technical knowledge, useful tips… |- | rowspan="3" | Generic || [[Services/FTP|File Repository]] || public/users || style="text-align: left;" | Generic file sharing system (using FTP) |- | [[Services/WebFileExchange|Downloads Links]] || public/users || style="text-align: left;" | Web-based generic file sharing |- | [[Services/SAFT|Shell Transfer]] || trusted || style="text-align: left;" | File transfer system using the SAFT protocol (shell access needed) |- | rowspan="3" | Utilities || colspan="2" | [[Services/WebFeeds|News WebReader]] || users || style="text-align: left;" | News feeds reader through a web interface |- | colspan="2" | [[Services/NTP|Time Server]] || public || style="text-align: left;" | System used to automatically setup time on your machines |- | colspan="2" | [[Services/Dico|Dictionary Server]] || public || style="text-align: left;" | Words searching system via a dedicated software (using the DICT protocol) or a Web-interface |- | rowspan="6" | Development || colspan="2" | [[Services/Projects|Project Management & Issue Tracking]] || public/users || style="text-align: left;" | |- | colspan="2" | [[Services/CodeReview|Code Review]] || public/users || style="text-align: left;" | |- | colspan="2" | [[Services/VCS|VCS]] || public/users || style="text-align: left;" | Code/configuration versioning tools (Git, SVN, Baz, Bzr…) |- | rowspan="2" | Databases || [[Services/SQL|SQL]] || users || style="text-align: left;" | SQL server (PostgreSQL or MySQL) |- | [[Services/LDAP|LDAP]] || users || style="text-align: left;" | LDAP server (OpenLDAP) |- | colspan="2" | [[Services/SoftwareRepository|Software Repository]] || public/users || style="text-align: left;" | Software repository, to provide custom packages (think Debian debs) or installation media (thinks DVDs) |- | rowspan="6" | Hosting || colspan="2" | [[Services/DNS|DNS]] || users || style="text-align: left;" | Domain Name System (NS1/NS2, DNSSEC…) |- | rowspan="2" | Mail || [[Services/MailHosting|Mail Domains]] || users || style="text-align: left;" | Mail hosting (MX1/MX2) |- | [[Services/MLHosting|Mailing-Lists]] || users || style="text-align: left;" | Distribution lists for mail domains |- | colspan="2" | [[Services/WebHosting|Web Sites/Applications]] || users || style="text-align: left;" | Web pages using HTML/XHTML, CSS, JS, and various server-side programming languages (SSI, PHP, Perl, Python, Ruby…), and statistics (analytics data/reports) |- | colspan="2" | [[Services/XMPPHosting|XMPP Domains]] || users || style="text-align: left;" | XMPP Node for a custom domain |- | colspan="2" | [[Services/Shell|Shell]] || trusted || style="text-align: left;" | Useful for website administration, development, run custom scripts, persistent applications for text-mode geeks… |- | rowspan="2" | Network || colspan="2" | [[Services/IPv6-Broker|IPv6 tunnels]] || users || style="text-align: left;" | Access to the IPv6 world through an IPv4 connection |- | colspan="2" | [[Services/NSTX|NSTX]] || users || style="text-align: left;" | Access to the Internet through a restricted WIFI connection (via an IP over DNS tunnel) |} == TODO == * in Services/Wiki: https://wiki.duckcorp.org/ * in Services/Shell: link to SAFT * in Services/XMPP: chitchat * in Services/WebFeeds: https://gossip.duckcorp.org/ * in Services/Projects: https://projects.duckcorp.org/ * in Services/VCS: https://rcs.duckcorp.org/ * portal.dc.o * Radio … 8d364ebfca06504aded0bbe45f2ae5a9c0df8b3c 384 376 2012-06-24T23:48:45Z Duck 2 wikitext text/x-wiki Here is a short overview of the services provided by DuckCorp. Our services are supervised and important data are [[Services/Backup|saved regularly]]. {{warning}} [[Services/Security|Notes about security !]] {| class="wikitable" style="text-align: center; width: 100%;" |+ Available Services |- ! Category !! colspan="2" | Service !! Access !! Description |- | rowspan="7" | Communication || rowspan="2" | Mail || [[Services/Mail|eMails]] || users || style="text-align: left;" | Mail boxes with anti-spam/anti-virus, filtering…, or mail redirections |- | [[Services/ML|Mailing-Lists]] || users || style="text-align: left;" | Distribution lists for mails |- | rowspan="3" | IRC || [[Services/IRC|IRC Network]] || public || style="text-align: left;" | MilkyPond Chat Network using a dedicated software or a Web-interface |- | [[Services/IRC-Bouncer|IRC Bouncer]] || users || style="text-align: left;" | IRC proxy (IRC server relaying IRC communications, keeping connections open and remembering logs) |- | [[Services/IRC-IM-GW|IRC to IM gateway]] || users || style="text-align: left;" | Communication to multiple instant messaging networks through a unified IRC-like interface |- | colspan="2" | [[Services/XMPP|XMPP (Jabber)]] || users || style="text-align: left;" | Global Chat Network (inter-communication between many [[wikipedia:Xmpp#History|well-known public IM services]]) |- | colspan="2" | [[Services/Tribioune|Triboune Libre]] || public || style="text-align: left;" | MilkyPond Web-chat system inspired by [http://linuxfr.org/board the famous one] on [http://linuxfr.org/ Linuxfr.org] |- | rowspan="5" | Sharing || colspan="2" | [[Services/Gallery|Media Gallery]] || public/users || style="text-align: left;" | Photo and video gallery |- | colspan="2" | [[Services/Wiki|Wiki]] || public/users || style="text-align: left;" | Technical knowledge, useful tips… |- | rowspan="3" | Generic || [[Services/FTP|File Repository]] || public/users || style="text-align: left;" | Generic file sharing system (using FTP) |- | [[Services/WebFileExchange|Downloads Links]] || public/users || style="text-align: left;" | Web-based generic file sharing |- | [[Services/SAFT|Shell Transfer]] || trusted || style="text-align: left;" | File transfer system using the SAFT protocol (shell access needed) |- | rowspan="3" | Utilities || colspan="2" | [[Services/WebFeeds|News WebReader]] || users || style="text-align: left;" | News feeds reader through a web interface |- | colspan="2" | [[Services/NTP|Time Server]] || public || style="text-align: left;" | System used to automatically setup time on your machines |- | colspan="2" | [[Services/Dico|Dictionary Server]] || public || style="text-align: left;" | Words searching system via a dedicated software (using the DICT protocol) or a Web-interface |- | rowspan="6" | Development || colspan="2" | [[Services/Projects|Project Management & Issue Tracking]] || public/users || style="text-align: left;" | Tool intended to help organize projects |- | colspan="2" | [[Services/CodeReview|Code Review]] || public/users || style="text-align: left;" | Tool intended to help improve software quality |- | colspan="2" | [[Services/VCS|VCS]] || public/users || style="text-align: left;" | Code/configuration versioning tools (Git, SVN, Baz, Bzr…) |- | rowspan="2" | Databases || [[Services/SQL|SQL]] || users || style="text-align: left;" | SQL server (PostgreSQL or MySQL) |- | [[Services/LDAP|LDAP]] || users || style="text-align: left;" | LDAP server (OpenLDAP) |- | colspan="2" | [[Services/SoftwareRepository|Software Repository]] || public/users || style="text-align: left;" | Software repository, to provide custom packages (think Debian debs) or installation media (thinks DVDs) |- | rowspan="6" | Hosting || colspan="2" | [[Services/DNS|DNS]] || users || style="text-align: left;" | Domain Name System (NS1/NS2, DNSSEC…) |- | rowspan="2" | Mail || [[Services/MailHosting|Mail Domains]] || users || style="text-align: left;" | Mail hosting (MX1/MX2) |- | [[Services/MLHosting|Mailing-Lists]] || users || style="text-align: left;" | Distribution lists for mail domains |- | colspan="2" | [[Services/WebHosting|Web Sites/Applications]] || users || style="text-align: left;" | Web pages using HTML/XHTML, CSS, JS, and various server-side programming languages (SSI, PHP, Perl, Python, Ruby…), and statistics (analytics data/reports) |- | colspan="2" | [[Services/XMPPHosting|XMPP Domains]] || users || style="text-align: left;" | XMPP Node for a custom domain |- | colspan="2" | [[Services/Shell|Shell]] || trusted || style="text-align: left;" | Useful for website administration, development, run custom scripts, persistent applications for text-mode geeks… |- | rowspan="2" | Network || colspan="2" | [[Services/IPv6-Broker|IPv6 tunnels]] || users || style="text-align: left;" | Access to the IPv6 world through an IPv4 connection |- | colspan="2" | [[Services/NSTX|NSTX]] || users || style="text-align: left;" | Access to the Internet through a restricted WIFI connection (via an IP over DNS tunnel) |} == TODO == * in Services/Wiki: https://wiki.duckcorp.org/ * in Services/Shell: link to SAFT * in Services/XMPP: chitchat * in Services/WebFeeds: https://gossip.duckcorp.org/ * in Services/VCS: https://rcs.duckcorp.org/ * portal.dc.o * Radio … ebd4cf58ee6af9a11d44fa97a7a79756fdb910a2 385 384 2012-08-19T17:31:34Z Duck 2 wikitext text/x-wiki Here is a short overview of the services provided by DuckCorp. Our services are supervised and important data are [[Services/Backup|saved regularly]]. {{warning}} [[Services/Security|Notes about security !]] {| class="wikitable" style="text-align: center; width: 100%;" |+ Available Services |- ! Category !! colspan="2" | Service !! Access !! Description |- | rowspan="8" | Communication || rowspan="2" | Mail || [[Services/Mail|eMails]] || users || style="text-align: left;" | Mail boxes with anti-spam/anti-virus, filtering…, or mail redirections |- | [[Services/ML|Mailing-Lists]] || users || style="text-align: left;" | Distribution lists for mails |- | rowspan="3" | IRC || [[Services/IRC|IRC Network]] || public || style="text-align: left;" | MilkyPond Chat Network using a dedicated software or a Web-interface |- | [[Services/IRC-Bouncer|IRC Bouncer]] || users || style="text-align: left;" | IRC proxy (IRC server relaying IRC communications, keeping connections open and remembering logs) |- | [[Services/IRC-IM-GW|IRC to IM gateway]] || users || style="text-align: left;" | Communication to multiple instant messaging networks through a unified IRC-like interface |- | rowspan="2" | XMPP (Jabber) || [[Services/XMPP|XMPP Network]] || users || style="text-align: left;" | Global Chat Network (inter-communication between many [[wikipedia:Xmpp#History|well-known public IM services]]) |- | [[Services/XMPP WebGW|XMPP WebChat]] || users || style="text-align: left;" | Social Platform |- | colspan="2" | [[Services/Tribioune|Triboune Libre]] || public || style="text-align: left;" | MilkyPond Web-chat system inspired by [http://linuxfr.org/board the famous one] on [http://linuxfr.org/ Linuxfr.org] |- | rowspan="5" | Sharing || colspan="2" | [[Services/Gallery|Media Gallery]] || public/users || style="text-align: left;" | Photo and video gallery |- | colspan="2" | [[Services/Wiki|Wiki]] || public/users || style="text-align: left;" | Technical knowledge, useful tips… |- | rowspan="3" | Generic || [[Services/FTP|File Repository]] || public/users || style="text-align: left;" | Generic file sharing system (using FTP) |- | [[Services/WebFileExchange|Downloads Links]] || public/users || style="text-align: left;" | Web-based generic file sharing |- | [[Services/SAFT|Shell Transfer]] || trusted || style="text-align: left;" | File transfer system using the SAFT protocol (shell access needed) |- | rowspan="3" | Utilities || colspan="2" | [[Services/WebFeeds|News WebReader]] || users || style="text-align: left;" | News feeds reader through a web interface |- | colspan="2" | [[Services/NTP|Time Server]] || public || style="text-align: left;" | System used to automatically setup time on your machines |- | colspan="2" | [[Services/Dico|Dictionary Server]] || public || style="text-align: left;" | Words searching system via a dedicated software (using the DICT protocol) or a Web-interface |- | rowspan="6" | Development || colspan="2" | [[Services/Projects|Project Management & Issue Tracking]] || public/users || style="text-align: left;" | Tool intended to help organize projects |- | colspan="2" | [[Services/CodeReview|Code Review]] || public/users || style="text-align: left;" | Tool intended to help improve software quality |- | colspan="2" | [[Services/VCS|VCS]] || public/users || style="text-align: left;" | Code/configuration versioning tools (Git, SVN, Baz, Bzr…) |- | rowspan="2" | Databases || [[Services/SQL|SQL]] || users || style="text-align: left;" | SQL server (PostgreSQL or MySQL) |- | [[Services/LDAP|LDAP]] || users || style="text-align: left;" | LDAP server (OpenLDAP) |- | colspan="2" | [[Services/SoftwareRepository|Software Repository]] || public/users || style="text-align: left;" | Software repository, to provide custom packages (think Debian debs) or installation media (thinks DVDs) |- | rowspan="6" | Hosting || colspan="2" | [[Services/DNS|DNS]] || users || style="text-align: left;" | Domain Name System (NS1/NS2, DNSSEC…) |- | rowspan="2" | Mail || [[Services/MailHosting|Mail Domains]] || users || style="text-align: left;" | Mail hosting (MX1/MX2) |- | [[Services/MLHosting|Mailing-Lists]] || users || style="text-align: left;" | Distribution lists for mail domains |- | colspan="2" | [[Services/WebHosting|Web Sites/Applications]] || users || style="text-align: left;" | Web pages using HTML/XHTML, CSS, JS, and various server-side programming languages (SSI, PHP, Perl, Python, Ruby…), and statistics (analytics data/reports) |- | colspan="2" | [[Services/XMPPHosting|XMPP Domains]] || users || style="text-align: left;" | XMPP Node for a custom domain |- | colspan="2" | [[Services/Shell|Shell]] || trusted || style="text-align: left;" | Useful for website administration, development, run custom scripts, persistent applications for text-mode geeks… |- | rowspan="2" | Network || colspan="2" | [[Services/IPv6-Broker|IPv6 tunnels]] || users || style="text-align: left;" | Access to the IPv6 world through an IPv4 connection |- | colspan="2" | [[Services/NSTX|NSTX]] || users || style="text-align: left;" | Access to the Internet through a restricted WIFI connection (via an IP over DNS tunnel) |} == TODO == * in Services/Wiki: https://wiki.duckcorp.org/ * in Services/Shell: link to SAFT * in Services/XMPP: chitchat * in Services/WebFeeds: https://gossip.duckcorp.org/ * in Services/VCS: https://rcs.duckcorp.org/ * portal.dc.o * Radio … c612d6c2258a43b2a0b378b69081aa0cc528b4ec 386 385 2012-08-19T17:49:12Z Duck 2 wikitext text/x-wiki Here is a short overview of the services provided by DuckCorp. Our services are supervised and important data are [[Services/Backup|saved regularly]]. {{warning}} [[Services/Security|Notes about security !]] {| class="wikitable" style="text-align: center; width: 100%;" |+ Available Services |- ! Category !! colspan="2" | Service !! Access !! Description |- | rowspan="8" | Communication || rowspan="2" | Mail || [[Services/Mail|eMails]] || users || style="text-align: left;" | Mail boxes with anti-spam/anti-virus, filtering…, or mail redirections |- | [[Services/ML|Mailing-Lists]] || users || style="text-align: left;" | Distribution lists for mails |- | rowspan="3" | IRC || [[Services/IRC|IRC Network]] || public || style="text-align: left;" | MilkyPond Chat Network using a dedicated software or a Web-interface |- | [[Services/IRC-Bouncer|IRC Bouncer]] || users || style="text-align: left;" | IRC proxy (IRC server relaying IRC communications, keeping connections open and remembering logs) |- | [[Services/IRC-IM-GW|IRC to IM gateway]] || users || style="text-align: left;" | Communication to multiple instant messaging networks through a unified IRC-like interface |- | rowspan="2" | XMPP (Jabber) || [[Services/XMPP|XMPP Network]] || users || style="text-align: left;" | Global Chat Network (inter-communication between many [[wikipedia:Xmpp#History|well-known public IM services]]) |- | [[Services/XMPP WebGW|XMPP WebChat]] || users || style="text-align: left;" | Social Platform |- | colspan="2" | [[Services/Tribioune|Triboune Libre]] || public || style="text-align: left;" | MilkyPond Web-chat system inspired by [http://linuxfr.org/board the famous one] on [http://linuxfr.org/ Linuxfr.org] |- | rowspan="5" | Sharing || colspan="2" | [[Services/Gallery|Media Gallery]] || public/users || style="text-align: left;" | Photo and video gallery |- | colspan="2" | [[Services/Wiki|Wiki]] || public/users || style="text-align: left;" | Documentation, technical knowledge, useful tips… |- | colspan="2" | [[Services/OwnCloud|OwnCloud]] || public/users || style="text-align: left;" | Personal data store (contacts, calendars, files…) with syncing/sharing capabilities |- | rowspan="2" | Generic || [[Services/FTP|File Repository]] || public/users || style="text-align: left;" | Generic file sharing system (using FTP) |- | [[Services/SAFT|Shell Transfer]] || trusted || style="text-align: left;" | File transfer system using the SAFT protocol (shell access needed) |- | rowspan="3" | Utilities || colspan="2" | [[Services/WebFeeds|News WebReader]] || users || style="text-align: left;" | News feeds reader through a web interface |- | colspan="2" | [[Services/NTP|Time Server]] || public || style="text-align: left;" | System used to automatically setup time on your machines |- | colspan="2" | [[Services/Dico|Dictionary Server]] || public || style="text-align: left;" | Words searching system via a dedicated software (using the DICT protocol) or a Web-interface |- | rowspan="6" | Development || colspan="2" | [[Services/Projects|Project Management & Issue Tracking]] || public/users || style="text-align: left;" | Tool intended to help organize projects |- | colspan="2" | [[Services/CodeReview|Code Review]] || public/users || style="text-align: left;" | Tool intended to help improve software quality |- | colspan="2" | [[Services/VCS|VCS]] || public/users || style="text-align: left;" | Code/configuration versioning tools (Git, SVN, Baz, Bzr…) |- | rowspan="2" | Databases || [[Services/SQL|SQL]] || users || style="text-align: left;" | SQL server (PostgreSQL or MySQL) |- | [[Services/LDAP|LDAP]] || users || style="text-align: left;" | LDAP server (OpenLDAP) |- | colspan="2" | [[Services/SoftwareRepository|Software Repository]] || public/users || style="text-align: left;" | Software repository, to provide custom packages (think Debian debs) or installation media (thinks DVDs) |- | rowspan="6" | Hosting || colspan="2" | [[Services/DNS|DNS]] || users || style="text-align: left;" | Domain Name System (NS1/NS2, DNSSEC…) |- | rowspan="2" | Mail || [[Services/MailHosting|Mail Domains]] || users || style="text-align: left;" | Mail hosting (MX1/MX2) |- | [[Services/MLHosting|Mailing-Lists]] || users || style="text-align: left;" | Distribution lists for mail domains |- | colspan="2" | [[Services/WebHosting|Web Sites/Applications]] || users || style="text-align: left;" | Web pages using HTML/XHTML, CSS, JS, and various server-side programming languages (SSI, PHP, Perl, Python, Ruby…), and statistics (analytics data/reports) |- | colspan="2" | [[Services/XMPPHosting|XMPP Domains]] || users || style="text-align: left;" | XMPP Node for a custom domain |- | colspan="2" | [[Services/Shell|Shell]] || trusted || style="text-align: left;" | Useful for website administration, development, run custom scripts, persistent applications for text-mode geeks… |- | rowspan="2" | Network || colspan="2" | [[Services/IPv6-Broker|IPv6 tunnels]] || users || style="text-align: left;" | Access to the IPv6 world through an IPv4 connection |- | colspan="2" | [[Services/NSTX|NSTX]] || users || style="text-align: left;" | Access to the Internet through a restricted WIFI connection (via an IP over DNS tunnel) |} == TODO == * in Services/Wiki: https://wiki.duckcorp.org/ * in Services/Shell: link to SAFT * in Services/XMPP: chitchat * in Services/WebFeeds: https://gossip.duckcorp.org/ * in Services/VCS: https://rcs.duckcorp.org/ * portal.dc.o * Radio … c4199c5ed96b678e90f41af0dc675d52ee1ee11c 400 386 2013-02-09T01:05:21Z Duck 2 wikitext text/x-wiki Here is a short overview of the services provided by DuckCorp. Our services are supervised and important data are [[Services/Backup|saved regularly]]. {{warning}} [[Services/Security|Notes about security !]] {| class="wikitable" style="text-align: center; width: 100%;" |+ Available Services |- ! Category !! colspan="2" | Service !! Access !! Description |- | rowspan="8" | Communication || rowspan="2" | Mail || [[Services/Mail|eMails]] || users || style="text-align: left;" | Mail boxes with anti-spam/anti-virus, filtering…, or mail redirections |- | [[Services/ML|Mailing-Lists]] || users || style="text-align: left;" | Distribution lists for mails |- | rowspan="3" | IRC || [[Services/IRC|IRC Network]] || public || style="text-align: left;" | MilkyPond Chat Network using a dedicated software or a Web-interface |- | [[Services/IRC-Bouncer|IRC Bouncer]] || users || style="text-align: left;" | IRC proxy (IRC server relaying IRC communications, keeping connections open and remembering logs) |- | [[Services/IRC-IM-GW|IRC to IM gateway]] || users || style="text-align: left;" | Communication to multiple instant messaging networks through a unified IRC-like interface |- | rowspan="2" | XMPP (Jabber) || [[Services/XMPP|XMPP Network]] || users || style="text-align: left;" | Global Chat Network (inter-communication between many [[wikipedia:Xmpp#History|well-known public IM services]]) |- | [[Services/XMPP WebGW|XMPP WebChat]] || users || style="text-align: left;" | Social Platform |- | colspan="2" | [[Services/Tribioune|Triboune Libre]] || public || style="text-align: left;" | MilkyPond Web-chat system inspired by [http://linuxfr.org/board the famous one] on [http://linuxfr.org/ Linuxfr.org] |- | rowspan="5" | Sharing || colspan="2" | [[Services/Gallery|Media Gallery]] || public/users || style="text-align: left;" | Photo and video gallery |- | colspan="2" | [[Services/Wiki|Wiki]] || public/users || style="text-align: left;" | Documentation, technical knowledge, useful tips… |- | colspan="2" | [[Services/OwnCloud|OwnCloud]] || public/users || style="text-align: left;" | Personal data store (contacts, calendars, files…) with syncing/sharing capabilities |- | rowspan="2" | Generic || [[Services/FTP|File Repository]] || public/users || style="text-align: left;" | Generic file sharing system (using FTP) |- | [[Services/SAFT|Shell Transfer]] || trusted || style="text-align: left;" | File transfer system using the SAFT protocol (shell access needed) |- | rowspan="3" | Utilities || colspan="2" | [[Services/WebFeeds|News WebReader]] || users || style="text-align: left;" | News feeds reader through a web interface |- | colspan="2" | [[Services/NTP|Time Server]] || public || style="text-align: left;" | System used to automatically setup time on your machines |- | colspan="2" | [[Services/Dico|Dictionary Server]] || public || style="text-align: left;" | Words searching system via a dedicated software (using the DICT protocol) or a Web-interface |- | rowspan="6" | Development || colspan="2" | [[Services/Projects|Project Management & Issue Tracking]] || public/users || style="text-align: left;" | Tool intended to help organize projects |- | colspan="2" | [[Services/CodeReview|Code Review]] || public/users || style="text-align: left;" | Tool intended to help improve software quality |- | colspan="2" | [[Services/VCS|VCS]] || public/users || style="text-align: left;" | Code/configuration versioning tools (Git, SVN, Baz, Bzr…) |- | rowspan="2" | Databases || [[Services/SQL|SQL]] || users || style="text-align: left;" | SQL server (PostgreSQL or MySQL) |- | [[Services/LDAP|LDAP]] || users || style="text-align: left;" | LDAP server (OpenLDAP) |- | colspan="2" | [[Services/SoftwareRepository|Software Repository]] || public/users || style="text-align: left;" | Software repository, to provide custom packages (think Debian debs) or installation media (thinks DVDs) |- | rowspan="6" | Hosting || colspan="2" | [[Services/DNS|DNS]] || users || style="text-align: left;" | Domain Name System (NS1/NS2, DNSSEC…) |- | rowspan="2" | Mail || [[Services/MailHosting|Mail Domains]] || users || style="text-align: left;" | Mail hosting (MX1/MX2) |- | [[Services/MLHosting|Mailing-Lists]] || users || style="text-align: left;" | Distribution lists for mail domains |- | colspan="2" | [[Services/WebHosting|Web Sites/Applications]] || users || style="text-align: left;" | Web pages using HTML/XHTML, CSS, JS, and various server-side programming languages (SSI, PHP, Perl, Python, Ruby…), and statistics (analytics data/reports) |- | colspan="2" | [[Services/XMPPHosting|XMPP Domains]] || users || style="text-align: left;" | XMPP Node for a custom domain |- | colspan="2" | [[Services/Shell|Shell]] || trusted || style="text-align: left;" | Useful for website administration, development, run custom scripts, persistent applications for text-mode geeks… |- | rowspan="2" | Network || colspan="2" | [[Services/IPv6-Broker|IPv6 tunnels]] || users || style="text-align: left;" | Access to the IPv6 world through an IPv4 connection |- | colspan="2" | [[Services/NSTX|NSTX]] || users || style="text-align: left;" | Access to the Internet through a restricted WIFI connection (via an IP over DNS tunnel) |} == TODO == * in Services/Wiki: https://wiki.duckcorp.org/ * in Services/Shell: link to SAFT * in Services/XMPP: chitchat * in Services/VCS: https://rcs.duckcorp.org/ * portal.dc.o * Radio … 2a4d4823e250a40bb1fd555a3061565ffddacef9 0 33 377 184 2012-05-09T11:08:47Z Duck 2 /* List of Previous Contributions */ wikitext text/x-wiki DuckCorp is built and maintained by volunteers, mostly with their own money. The services are totaly free of charge for all users, but you may wish to contribute to help us keep it working well and improve. == How to Contribute ? == You can help us with: * sponsoring: if you can host a machine and/or provide connectivity * equipements: see the list of possible improvements below * money: you can send us money which will be used in the association: ** by check (see the duckcorp.org whois for Duck's postal address, or ask him by mail or IRC) ** by Paypal to duck@duckcorp.org == What can you Contribute ? == Here are ideas on which to contribute: * [[DcExpenses#Regular_Expenses|regular expenses]] * [???] buy a new machine, to provide: VMs, more services redondancy, ... (needed hardware not yet evaluated, more on this later) * [~120€] add a battery backup unit for Toushirou's 3ware card (for more data security, as datacenters tends to be less and less reliable) * [??? (quite expensive)] change Orfeo's backplane to have 4 disks slot instead of 2, and add 2 new disks (in a new RAID 1 array), planned at least 120GB capacity (2.5″ 10000 RPM SAS, like the other ones) (can be bought anywhere, but proprietary braquets needed) == List of Previous Contributions == Only pure financial contributions are listed here; equipments and sponsored purchases are listed on the [[DcExpenses|DuckCorp expenses page]]. {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Amount !! Donnor !! Comments |- | 2011-01-10 || 500€ || AnonymousDonnor1 || |- | 2010-05-16 || 42€ || Chloé || |} Note: early contributions in the CoinNetwork project are not taken into account, as most information is lost. bc3d83da5c42fc6b9b56243582ea60b08aecf6a3 407 377 2013-09-22T12:42:25Z Duck 2 /* List of Previous Contributions */ wikitext text/x-wiki DuckCorp is built and maintained by volunteers, mostly with their own money. The services are totaly free of charge for all users, but you may wish to contribute to help us keep it working well and improve. == How to Contribute ? == You can help us with: * sponsoring: if you can host a machine and/or provide connectivity * equipements: see the list of possible improvements below * money: you can send us money which will be used in the association: ** by check (see the duckcorp.org whois for Duck's postal address, or ask him by mail or IRC) ** by Paypal to duck@duckcorp.org == What can you Contribute ? == Here are ideas on which to contribute: * [[DcExpenses#Regular_Expenses|regular expenses]] * [???] buy a new machine, to provide: VMs, more services redondancy, ... (needed hardware not yet evaluated, more on this later) * [~120€] add a battery backup unit for Toushirou's 3ware card (for more data security, as datacenters tends to be less and less reliable) * [??? (quite expensive)] change Orfeo's backplane to have 4 disks slot instead of 2, and add 2 new disks (in a new RAID 1 array), planned at least 120GB capacity (2.5″ 10000 RPM SAS, like the other ones) (can be bought anywhere, but proprietary braquets needed) == List of Previous Contributions == Only pure financial contributions are listed here; equipments and sponsored purchases are listed on the [[DcExpenses|DuckCorp expenses page]]. {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Amount !! Donnor !! Comments |- | 2013-09-22 || 100$ USD || Damien || via Paypal => 69€ |- | 2011-01-10 || 500€ || AnonymousDonnor1 || |- | 2010-05-16 || 42€ || Chloé || |} Note: early contributions in the CoinNetwork project are not taken into account, as most information is lost. 9916709c6ae091c87d3591757decc366f455e405 0 32 378 125 2012-05-09T11:10:32Z Duck 2 /* Improvement Expenses */ wikitext text/x-wiki Let's be transparent about money too. Pure financial contributions are not listed here, but in the [[DcDonation|donation page]]. == Regular Expenses == This does not account for external sponsorship, but contributions by members. {| class="wikitable" style="text-align: center; width: 100%;" ! Object !! Amount !! Sponsor !! Comments |- | DuckCorp DNS domain || ~15€/year || Duck |- | MilkyPond DNS domain || ~15€/year || Rtp |- | Toushirou's housing || 41.56€/month || Duck || collocation with Yok (considering network switch and APC powerswitch shared rack space) |} Note: this does not take into account the ADSL line used by Elwing and Daneel, coupled in the same offer providing the VM Thorfinn, as it is used privately. == Exceptional Expenses == Note: this does not take into account expenses before 2006 because most historical data were lost. Note: Elwing and Daneel are used privately. Elwing is not taken into account, as most services are not used for DC (and since begining of 2010 are moving progresively elsewhere), but Daneel is, as a big part of the backup is for DC's machines. === Improvement Expenses === {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Object !! Amount !! Sponsor !! Comments |- | 2012-05-09 || more memory for Toushirou (2*2GB) || ~60€ || Pilou || PC2-6400 |- | 2010-05-22 || replacement memory for Toushirou (2*2GB) || 105€ || Duck || PC2-5300/5400 2*2GB memory in a correct brand could not be found anymore, so we had to take PC2-6400 instead |- | 2007-10 || replacement server (Orfeo-NG) || 1210€ || Duck || Sun Fire X4100 |- | 2007-05 || new server (Toushirou) || 1709.08€ || Duck || Supermicro PDSMI+ / Core 2 Duo E6600 / 2GB PC5400 / 3ware 9550SX4LP / 4x HD SATA II 250GB |} === Failure Expenses === {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Object !! Amount !! Sponsor !! Comments |- | 2010-01-06 || spare disk || 73€ || Duck || avoided tragedy when both disks in Daneel died at one week interval |- | 2007-09-29 || replacement server (Daneel-ng) || 534.90€ || Duck || machine too old and previous disk died horribly |- | 2006-01 || 300GB HD for Daneel (backup) || || AnonymousDonnor1 || replaced since then |} === Other Expenses === {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Object !! Amount !! Sponsor !! Comments |- | 2010-06-29 || taxi || 26.20€ || Duck || Nerim bought Sivit, moving Toushirou to their new suite at Equinix PA3 (CBV->STD) |} 994652b7772391f76685e0f290d12bf8e9006052 379 378 2012-05-09T11:11:03Z Duck 2 /* Exceptional Expenses */ wikitext text/x-wiki Let's be transparent about money too. Pure financial contributions are not listed here, but in the [[DcDonation|donation page]]. == Regular Expenses == This does not account for external sponsorship, but contributions by members. {| class="wikitable" style="text-align: center; width: 100%;" ! Object !! Amount !! Sponsor !! Comments |- | DuckCorp DNS domain || ~15€/year || Duck |- | MilkyPond DNS domain || ~15€/year || Rtp |- | Toushirou's housing || 41.56€/month || Duck || collocation with Yok (considering network switch and APC powerswitch shared rack space) |} Note: this does not take into account the ADSL line used by Elwing and Daneel, coupled in the same offer providing the VM Thorfinn, as it is used privately. == Exceptional Expenses == Note: this does not take into account expenses before 2006 because most historical data were lost. Note: Elwing and Daneel are used privately. Elwing is not taken into account, as most services are not used for DC (and since begining of 2010 are moving progresively elsewhere), but Daneel is, as a big part of the backup is for DC's machines. === Improvement Expenses === {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Object !! Amount !! Sponsor !! Comments |- | 2012-05-09 || more memory for Toushirou (2*2GB) || ~60€ || Pilou || PC2-6400 |- | 2007-10 || replacement server (Orfeo-NG) || 1210€ || Duck || Sun Fire X4100 |- | 2007-05 || new server (Toushirou) || 1709.08€ || Duck || Supermicro PDSMI+ / Core 2 Duo E6600 / 2GB PC5400 / 3ware 9550SX4LP / 4x HD SATA II 250GB |} === Failure Expenses === {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Object !! Amount !! Sponsor !! Comments |- | 2010-05-22 || replacement memory for Toushirou (2*2GB) || 105€ || Duck || PC2-5300/5400 2*2GB memory in a correct brand could not be found anymore, so we had to take PC2-6400 instead |- | 2010-01-06 || spare disk || 73€ || Duck || avoided tragedy when both disks in Daneel died at one week interval |- | 2007-09-29 || replacement server (Daneel-ng) || 534.90€ || Duck || machine too old and previous disk died horribly |- | 2006-01 || 300GB HD for Daneel (backup) || || AnonymousDonnor1 || replaced since then |} === Other Expenses === {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Object !! Amount !! Sponsor !! Comments |- | 2010-06-29 || taxi || 26.20€ || Duck || Nerim bought Sivit, moving Toushirou to their new suite at Equinix PA3 (CBV->STD) |} 3ca0bb46aa94cf2aa1c7c7e160d374e784e998ac 380 379 2012-05-09T11:12:15Z Duck 2 /* Improvement Expenses */ wikitext text/x-wiki Let's be transparent about money too. Pure financial contributions are not listed here, but in the [[DcDonation|donation page]]. == Regular Expenses == This does not account for external sponsorship, but contributions by members. {| class="wikitable" style="text-align: center; width: 100%;" ! Object !! Amount !! Sponsor !! Comments |- | DuckCorp DNS domain || ~15€/year || Duck |- | MilkyPond DNS domain || ~15€/year || Rtp |- | Toushirou's housing || 41.56€/month || Duck || collocation with Yok (considering network switch and APC powerswitch shared rack space) |} Note: this does not take into account the ADSL line used by Elwing and Daneel, coupled in the same offer providing the VM Thorfinn, as it is used privately. == Exceptional Expenses == Note: this does not take into account expenses before 2006 because most historical data were lost. Note: Elwing and Daneel are used privately. Elwing is not taken into account, as most services are not used for DC (and since begining of 2010 are moving progresively elsewhere), but Daneel is, as a big part of the backup is for DC's machines. === Improvement Expenses === {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Object !! Amount !! Sponsor !! Comments |- | 2012-05-09 || more memory for Toushirou (2*2GB) || ~60€ || Pilou || PC2-6400 instead of PC2-5300/5400 (see replacement memory details) |- | 2007-10 || replacement server (Orfeo-NG) || 1210€ || Duck || Sun Fire X4100 |- | 2007-05 || new server (Toushirou) || 1709.08€ || Duck || Supermicro PDSMI+ / Core 2 Duo E6600 / 2GB PC5400 / 3ware 9550SX4LP / 4x HD SATA II 250GB |} === Failure Expenses === {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Object !! Amount !! Sponsor !! Comments |- | 2010-05-22 || replacement memory for Toushirou (2*2GB) || 105€ || Duck || PC2-5300/5400 2*2GB memory in a correct brand could not be found anymore, so we had to take PC2-6400 instead |- | 2010-01-06 || spare disk || 73€ || Duck || avoided tragedy when both disks in Daneel died at one week interval |- | 2007-09-29 || replacement server (Daneel-ng) || 534.90€ || Duck || machine too old and previous disk died horribly |- | 2006-01 || 300GB HD for Daneel (backup) || || AnonymousDonnor1 || replaced since then |} === Other Expenses === {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Object !! Amount !! Sponsor !! Comments |- | 2010-06-29 || taxi || 26.20€ || Duck || Nerim bought Sivit, moving Toushirou to their new suite at Equinix PA3 (CBV->STD) |} b536e969101fe14a9a17863141adbca9c25cd4ce 404 380 2013-06-13T15:36:02Z Duck 2 /* Regular Expenses */ wikitext text/x-wiki Let's be transparent about money too. Pure financial contributions are not listed here, but in the [[DcDonation|donation page]]. == Regular Expenses == This does not account for external sponsorship, but contributions by members. {| class="wikitable" style="text-align: center; width: 100%;" ! Object !! Amount !! Sponsor !! Comments |- | DuckCorp DNS domain || ~15€/year || Duck |- | MilkyPond DNS domain || ~15€/year || Rtp |- | Toushirou's housing || 41.56€/month || Duck || collocation with Sam (considering network switch and APC powerswitch shared rack space) |} Note: this does not take into account the ADSL line used by Elwing and Daneel, coupled in the same offer providing the VM Thorfinn, as it is used privately. == Exceptional Expenses == Note: this does not take into account expenses before 2006 because most historical data were lost. Note: Elwing and Daneel are used privately. Elwing is not taken into account, as most services are not used for DC (and since begining of 2010 are moving progresively elsewhere), but Daneel is, as a big part of the backup is for DC's machines. === Improvement Expenses === {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Object !! Amount !! Sponsor !! Comments |- | 2012-05-09 || more memory for Toushirou (2*2GB) || ~60€ || Pilou || PC2-6400 instead of PC2-5300/5400 (see replacement memory details) |- | 2007-10 || replacement server (Orfeo-NG) || 1210€ || Duck || Sun Fire X4100 |- | 2007-05 || new server (Toushirou) || 1709.08€ || Duck || Supermicro PDSMI+ / Core 2 Duo E6600 / 2GB PC5400 / 3ware 9550SX4LP / 4x HD SATA II 250GB |} === Failure Expenses === {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Object !! Amount !! Sponsor !! Comments |- | 2010-05-22 || replacement memory for Toushirou (2*2GB) || 105€ || Duck || PC2-5300/5400 2*2GB memory in a correct brand could not be found anymore, so we had to take PC2-6400 instead |- | 2010-01-06 || spare disk || 73€ || Duck || avoided tragedy when both disks in Daneel died at one week interval |- | 2007-09-29 || replacement server (Daneel-ng) || 534.90€ || Duck || machine too old and previous disk died horribly |- | 2006-01 || 300GB HD for Daneel (backup) || || AnonymousDonnor1 || replaced since then |} === Other Expenses === {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Object !! Amount !! Sponsor !! Comments |- | 2010-06-29 || taxi || 26.20€ || Duck || Nerim bought Sivit, moving Toushirou to their new suite at Equinix PA3 (CBV->STD) |} 4fc24eda6a424fd459caf1bfb28337ff76f653a7 0 66 381 2012-06-24T22:43:47Z Duck 2 Created page with "{{Template:Service | description = A project management and issue tracking software is a tool intended to help organize projects (not only computer science related projects), fro…" wikitext text/x-wiki {{Template:Service | description = A project management and issue tracking software is a tool intended to help organize projects (not only computer science related projects), from various aspects: scheduling, planning, communication, tracking, documentation… | prerequisite = You may need to ask a project administrator for membership to access certain projects and resources, but can already login with your global account. A few projects may be public, which means you (or outsiders) can access most information without authenticating (and maybe even add some). | account = global-reg | ipv6 = true | security_notes = This service is secure. }} == Access == Use the following URL and login: https://projects.duckcorp.org/ == Documentation == * [http://www.redmine.org/guide Help Page] * generic documentation on [[wikipedia:Project_management_software|Project management software]] == Technical Details == This service is made using: * [http://www.redmine.org/ Redmine] 4687ee91f56302aedb68af110e0d155965f4424f 0 67 382 2012-06-24T23:08:44Z Duck 2 Created page with "{{Template:Service | description = This service is an online dictionary, used both for definitions and translations, providing information from multiple sources | prerequisite = …" wikitext text/x-wiki {{Template:Service | description = This service is an online dictionary, used both for definitions and translations, providing information from multiple sources | prerequisite = | account = | ipv6 = false | security_notes = There is no big security concern except you can't be sure you're talking to our DICT server (no TLS support). }} == Access == === Web Interface === Use the following URL: http://dico.duckcorp.org/ === Command Line Interface === You need a DICT software to query the dictionary. On Debian you can install it easily using: apt-get install dico or (another compatible software): apt-get install dict With ''dico'' you can query for &lt;word&gt;: dico --host=dico.duckcorp.org &lt;word&gt; or with ''dict'': dict --host=dico.duckcorp.org &lt;word&gt; == Documentation == * generic documentation on [[wikipedia:Dict|DICT]] * [http://puszcza.gnu.org.ua/software/dico/manual/dico.html#SEC69 command line syntax for dico] == Technical Details == This service is made using: * [http://www.gnu.org/software/dico/ GNU Dico] * [http://www.djangoproject.com/ Django] d9b94b0de8e621bbcb13814363d145d8969a3f4d 0 54 383 333 2012-06-24T23:47:52Z Duck 2 wikitext text/x-wiki {{Template:Service | description = A code review software is a tool intended to help improve software quality. It is intended for software developers to help them receive feedback on their patches. | prerequisite = You need to ask an administrator for an account if you want to create or comment on review, but you don't need anything if you just want to watch existing ones. | account = global-reg | ipv6 = true | security_notes = This service is secure. }} == Access == Use the following URL and login: https://codereview.duckcorp.org/ == Documentation == * [http://code.google.com/p/rietveld/wiki/CodeReviewHelp Help Page] * generic documentation on [[wikipedia:Code_review|Code Review]] == Technical Details == This service is made using: * [http://code.google.com/p/rietveld/ Rietveld] * [http://www.djangoproject.com/ Django] c1194567a8f12a4cdf619e2a296c93651c1e4a63 0 53 387 332 2012-08-19T17:56:09Z Duck 2 wikitext text/x-wiki {{Template:Service | description = The file repository is a general-purpose file exchange method. You push files into it and they are kept until you remove them. You may also share them with a other people. | prerequisite = You need to ask an administrator for an account if you want to push your own files, but you don't need anything if you just want to retrieve files from the public folders. | account = global-reg | ipv6 = true | security_notes = This service is secure. }} {{warning}} Remember not to use this service to store illegal or non-free data. == Access == You need a FTP client software to access this service, for example: * on GNU/*: filezilla or lftp * on MacOS: CyberDuck * on Windows: filezilla Most browsers should also work for read access. The publics folders are available for read access using this URL: ftp://ftp.duckcorp.org/ If you want to push files, you need to authenticate with SSL/TLS using this URL: ftps://ftps.duckcorp.org/ You may also access files directly on Toushirou in ''/ftp/ftp.duckcorp.org/'' if you have a [[Services/Shell|shell access]]. == Folders == Summary of important folders for write access: * photos-perso-dc: upload zone for the [[Services/Gallery|gallery]] * private: restricted folders, for users or groups of users; ask an administrator if you need private folders * public: folders which can be read by everybody (accessible directly without authentication on ftp://ftp.duckcorp.org/) * repository: upload folders for the [[Services/SoftwareRepository|software repository]] facility * sendfile: arrival folders for the [[Services/SAFT|shell transfer]] service * sites: folders for hosted websites content == Documentation == * generic documentation on [[wikipedia:Ftp|FTP]] == Technical Details == This service is made using: * [http://proftpd.org/ ProFTPD] ecd359ded3252d0264d0f45d855fadc8de283405 0 68 388 2012-08-19T18:15:21Z Duck 2 Created page with "{{Template:Service | description = The OwnCloud service is a webservice used to access, sync, and share your personal data. Currently you can: * store files (and in-place view/ed…" wikitext text/x-wiki {{Template:Service | description = The OwnCloud service is a webservice used to access, sync, and share your personal data. Currently you can: * store files (and in-place view/edit of certain extension directly from the web interface) * manage your contacts * manage your calendars * <del>manage tasks</del> (deactivated because broken at the moment) * manage bookmarks (for web links) (it should be possible to sync with Firefox in the future) | prerequisite = | account = global-reg | ipv6 = true | security_notes = This service is secure but beware when sharing your data to other people. }} {{warning}} Remember not to use this service to store illegal or non-free data. == Access == === Web Interface === Use this URL in your browser: https://stuff.milkypond.org/ Then you can setup your contacts, calendars, and store files. === DAV Interface === You can use the DAV interface to sync your data from a desktop application or you mobile device. * Files ** Desktop: *** use XFCE/Gigolo or GNOME/Nautilus to create a remote drive *** use the [http://owncloud.org/support/sync-clients/ csync] utility to synchronize files ** Mobile Devices: *** Android: use the [http://owncloud.org/support/android/ Owncloud] app (available on [http://f-droid.org/ F-Droid]) to synchronize files * Contacts: ** Desktop: ** Mobile Devices: the [http://owncloud.org/support/android/ Owncloud] app should be able to do it in the future, but you may use the [http://dmfs.org/wiki/index.php?title=CardDAV-Sync CardDAV-Sync] app which is [http://dmfs.org/wiki/index.php?title=Open_source_status to be opensourced] * Calendars: ** Desktop: ** Mobile Devices: the [http://owncloud.org/support/android/ Owncloud] app should be able to do it in the future, but you may use the [http://dmfs.org/wiki/index.php?title=CalDAV-Sync CalDAV-Sync] app which is [http://dmfs.org/wiki/index.php?title=Open_source_status to be opensourced], or try [http://acal.me/wiki/Main_Page aCal] (available on [http://f-droid.org/ F-Droid]) which does not use the internal calendar and proved quite slow == Documentation == * ''OwnCloud'' section in the [http://owncloud.org/support/ Help Page] == Technical Details == This service is made using: * [http://owncloud.org/ OwnCloud] c86710b289fe689bedfaf769727a4ca634fb6f2b 389 388 2012-08-19T18:26:43Z Duck 2 wikitext text/x-wiki {{Template:Service | description = The OwnCloud service is a webservice used to access, sync, and share your personal data. Currently you can: * store files (and in-place view/edit of certain extension directly from the web interface) * manage your contacts * manage your calendars * <del>manage tasks</del> (deactivated because broken at the moment) * manage bookmarks (for web links) (it should be possible to sync with Firefox in the future) | prerequisite = | account = global-reg | ipv6 = true | security_notes = This service is secure but beware when sharing your data to other people. }} {{warning}} Remember not to use this service to store illegal or non-free data. == Access == === Web Interface === Use this URL in your browser: https://stuff.milkypond.org/ Then you can setup your contacts, calendars, and store files. === WebDAV Interface === You can use the [[wikipedia:WebDAV|WebDAV]] interface to sync your data from a desktop application or you mobile device. Applications can use the main address of the web interface (see above) with your credentials and should be able to discover you data, but sometimes they have limitations and you need to specify a full ugly link ; in this case you can find the link in the interface, either on the resource to access or in your personal settings page. * Files ** Desktop: *** use XFCE/Gigolo or GNOME/Nautilus to create a remote drive *** use the [http://owncloud.org/support/sync-clients/ csync] utility to synchronize files ** Mobile Devices: *** Android: use the [http://owncloud.org/support/android/ Owncloud] app (available on [http://f-droid.org/ F-Droid]) to synchronize files * Contacts: ** Desktop: ** Mobile Devices: the [http://owncloud.org/support/android/ Owncloud] app should be able to do it in the future, but you may use the [http://dmfs.org/wiki/index.php?title=CardDAV-Sync CardDAV-Sync] app which is [http://dmfs.org/wiki/index.php?title=Open_source_status to be opensourced] * Calendars: ** Desktop: ** Mobile Devices: the [http://owncloud.org/support/android/ Owncloud] app should be able to do it in the future, but you may use the [http://dmfs.org/wiki/index.php?title=CalDAV-Sync CalDAV-Sync] app which is [http://dmfs.org/wiki/index.php?title=Open_source_status to be opensourced], or try [http://acal.me/wiki/Main_Page aCal] (available on [http://f-droid.org/ F-Droid]) which does not use the internal calendar and proved quite slow == Documentation == * ''OwnCloud'' section in the [http://owncloud.org/support/ Help Page] == Technical Details == This service is made using: * [http://owncloud.org/ OwnCloud] 315be9ecf6eda33586788d9a4292737082512f31 390 389 2012-08-19T18:27:05Z Duck 2 wikitext text/x-wiki {{Template:Service | description = The OwnCloud service is a webservice used to access, sync, and share your personal data. Currently you can: * store files (and in-place view/edit of certain extension directly from the web interface) * manage your contacts * manage your calendars * <del>manage tasks</del> (deactivated because broken at the moment) * manage bookmarks (for web links) (it should be possible to sync with Firefox in the future) | prerequisite = | account = global | ipv6 = true | security_notes = This service is secure but beware when sharing your data to other people. }} {{warning}} Remember not to use this service to store illegal or non-free data. == Access == === Web Interface === Use this URL in your browser: https://stuff.milkypond.org/ Then you can setup your contacts, calendars, and store files. === WebDAV Interface === You can use the [[wikipedia:WebDAV|WebDAV]] interface to sync your data from a desktop application or you mobile device. Applications can use the main address of the web interface (see above) with your credentials and should be able to discover you data, but sometimes they have limitations and you need to specify a full ugly link ; in this case you can find the link in the interface, either on the resource to access or in your personal settings page. * Files ** Desktop: *** use XFCE/Gigolo or GNOME/Nautilus to create a remote drive *** use the [http://owncloud.org/support/sync-clients/ csync] utility to synchronize files ** Mobile Devices: *** Android: use the [http://owncloud.org/support/android/ Owncloud] app (available on [http://f-droid.org/ F-Droid]) to synchronize files * Contacts: ** Desktop: ** Mobile Devices: the [http://owncloud.org/support/android/ Owncloud] app should be able to do it in the future, but you may use the [http://dmfs.org/wiki/index.php?title=CardDAV-Sync CardDAV-Sync] app which is [http://dmfs.org/wiki/index.php?title=Open_source_status to be opensourced] * Calendars: ** Desktop: ** Mobile Devices: the [http://owncloud.org/support/android/ Owncloud] app should be able to do it in the future, but you may use the [http://dmfs.org/wiki/index.php?title=CalDAV-Sync CalDAV-Sync] app which is [http://dmfs.org/wiki/index.php?title=Open_source_status to be opensourced], or try [http://acal.me/wiki/Main_Page aCal] (available on [http://f-droid.org/ F-Droid]) which does not use the internal calendar and proved quite slow == Documentation == * ''OwnCloud'' section in the [http://owncloud.org/support/ Help Page] == Technical Details == This service is made using: * [http://owncloud.org/ OwnCloud] f417b9e007d2ba5ef39edcb7518e7ece9510f35b 391 390 2012-08-19T18:27:41Z Duck 2 wikitext text/x-wiki {{Template:Service | description = The OwnCloud service is a webservice used to access, sync, and share your personal data. Currently you can: * store your files (and in-place view/edit of certain extension directly from the web interface) * manage your contacts * manage your calendars * <del>manage your tasks</del> (deactivated because broken at the moment) * manage your bookmarks (for web links) (it should be possible to sync with Firefox in the future) | prerequisite = | account = global | ipv6 = true | security_notes = This service is secure but beware when sharing your data to other people. }} {{warning}} Remember not to use this service to store illegal or non-free data. == Access == === Web Interface === Use this URL in your browser: https://stuff.milkypond.org/ Then you can setup your contacts, calendars, and store files. === WebDAV Interface === You can use the [[wikipedia:WebDAV|WebDAV]] interface to sync your data from a desktop application or you mobile device. Applications can use the main address of the web interface (see above) with your credentials and should be able to discover you data, but sometimes they have limitations and you need to specify a full ugly link ; in this case you can find the link in the interface, either on the resource to access or in your personal settings page. * Files ** Desktop: *** use XFCE/Gigolo or GNOME/Nautilus to create a remote drive *** use the [http://owncloud.org/support/sync-clients/ csync] utility to synchronize files ** Mobile Devices: *** Android: use the [http://owncloud.org/support/android/ Owncloud] app (available on [http://f-droid.org/ F-Droid]) to synchronize files * Contacts: ** Desktop: ** Mobile Devices: the [http://owncloud.org/support/android/ Owncloud] app should be able to do it in the future, but you may use the [http://dmfs.org/wiki/index.php?title=CardDAV-Sync CardDAV-Sync] app which is [http://dmfs.org/wiki/index.php?title=Open_source_status to be opensourced] * Calendars: ** Desktop: ** Mobile Devices: the [http://owncloud.org/support/android/ Owncloud] app should be able to do it in the future, but you may use the [http://dmfs.org/wiki/index.php?title=CalDAV-Sync CalDAV-Sync] app which is [http://dmfs.org/wiki/index.php?title=Open_source_status to be opensourced], or try [http://acal.me/wiki/Main_Page aCal] (available on [http://f-droid.org/ F-Droid]) which does not use the internal calendar and proved quite slow == Documentation == * ''OwnCloud'' section in the [http://owncloud.org/support/ Help Page] == Technical Details == This service is made using: * [http://owncloud.org/ OwnCloud] 0b7fcb0d8166e3cd9ebce829a263ae338b89ed01 392 391 2012-08-19T18:27:55Z Duck 2 wikitext text/x-wiki {{Template:Service | description = The OwnCloud service is a webservice used to access, sync, and share your personal data. Currently you can: * store your files (and in-place view/edit of certain extensions directly from the web interface) * manage your contacts * manage your calendars * <del>manage your tasks</del> (deactivated because broken at the moment) * manage your bookmarks (for web links) (it should be possible to sync with Firefox in the future) | prerequisite = | account = global | ipv6 = true | security_notes = This service is secure but beware when sharing your data to other people. }} {{warning}} Remember not to use this service to store illegal or non-free data. == Access == === Web Interface === Use this URL in your browser: https://stuff.milkypond.org/ Then you can setup your contacts, calendars, and store files. === WebDAV Interface === You can use the [[wikipedia:WebDAV|WebDAV]] interface to sync your data from a desktop application or you mobile device. Applications can use the main address of the web interface (see above) with your credentials and should be able to discover you data, but sometimes they have limitations and you need to specify a full ugly link ; in this case you can find the link in the interface, either on the resource to access or in your personal settings page. * Files ** Desktop: *** use XFCE/Gigolo or GNOME/Nautilus to create a remote drive *** use the [http://owncloud.org/support/sync-clients/ csync] utility to synchronize files ** Mobile Devices: *** Android: use the [http://owncloud.org/support/android/ Owncloud] app (available on [http://f-droid.org/ F-Droid]) to synchronize files * Contacts: ** Desktop: ** Mobile Devices: the [http://owncloud.org/support/android/ Owncloud] app should be able to do it in the future, but you may use the [http://dmfs.org/wiki/index.php?title=CardDAV-Sync CardDAV-Sync] app which is [http://dmfs.org/wiki/index.php?title=Open_source_status to be opensourced] * Calendars: ** Desktop: ** Mobile Devices: the [http://owncloud.org/support/android/ Owncloud] app should be able to do it in the future, but you may use the [http://dmfs.org/wiki/index.php?title=CalDAV-Sync CalDAV-Sync] app which is [http://dmfs.org/wiki/index.php?title=Open_source_status to be opensourced], or try [http://acal.me/wiki/Main_Page aCal] (available on [http://f-droid.org/ F-Droid]) which does not use the internal calendar and proved quite slow == Documentation == * ''OwnCloud'' section in the [http://owncloud.org/support/ Help Page] == Technical Details == This service is made using: * [http://owncloud.org/ OwnCloud] a71e14daaa58ae2bbc24b18164f9e4180b97cf2d 393 392 2012-08-19T21:56:17Z Duck 2 /* WebDAV Interface */ wikitext text/x-wiki {{Template:Service | description = The OwnCloud service is a webservice used to access, sync, and share your personal data. Currently you can: * store your files (and in-place view/edit of certain extensions directly from the web interface) * manage your contacts * manage your calendars * <del>manage your tasks</del> (deactivated because broken at the moment) * manage your bookmarks (for web links) (it should be possible to sync with Firefox in the future) | prerequisite = | account = global | ipv6 = true | security_notes = This service is secure but beware when sharing your data to other people. }} {{warning}} Remember not to use this service to store illegal or non-free data. == Access == === Web Interface === Use this URL in your browser: https://stuff.milkypond.org/ Then you can setup your contacts, calendars, and store files. === WebDAV Interface === You can use the [[wikipedia:WebDAV|WebDAV]] interface to sync your data from a desktop application or you mobile device. Applications can use the main address of the web interface (see above) with your credentials and should be able to discover you data, but sometimes they have limitations and you need to specify a full ugly link ; in this case you can find the link in the interface, either on the resource to access or in your personal settings page. ==== Files ==== * Desktop: ** remote drive (synchrounous): use XFCE/Gigolo or GNOME/Nautilus ** synchronize (asynchronous): use the [http://owncloud.org/support/sync-clients/ csync] utility * Mobile Devices: ** Android: use the [http://owncloud.org/support/android/ Owncloud] app (available on [http://f-droid.org/ F-Droid]) to synchronize files ==== Contacts ==== * Desktop: * Mobile Devices: ** Android: the [http://owncloud.org/support/android/ Owncloud] app should be able to do it in the future, but you may use the [http://dmfs.org/wiki/index.php?title=CardDAV-Sync CardDAV-Sync] app which is [http://dmfs.org/wiki/index.php?title=Open_source_status to be opensourced] * Webmail: ** Webdesk (Horde): does not work ** old webmail (Squirrelmail): does not work ** newest webmail (RoundCube): works nicely with the newest webmail (RoundCube) (see in Settings->Preferences->CardDAV) ==== Calendars: ==== * Desktop: * Mobile Devices: ** Android: the [http://owncloud.org/support/android/ Owncloud] app should be able to do it in the future, but you may use the [http://dmfs.org/wiki/index.php?title=CalDAV-Sync CalDAV-Sync] app which is [http://dmfs.org/wiki/index.php?title=Open_source_status to be opensourced], or try [http://acal.me/wiki/Main_Page aCal] (available on [http://f-droid.org/ F-Droid]) which does not use the internal calendar and proved quite slow * Webmail: ** Webdesk (Horde): does not work ** old webmail (Squirrelmail): does not work ** newest webmail (RoundCube): should work but it does not seem to parse events properly even if there's no errors (see in Settings->Preferences->Calendar and the Provider field) == Documentation == * ''OwnCloud'' section in the [http://owncloud.org/support/ Help Page] == Technical Details == This service is made using: * [http://owncloud.org/ OwnCloud] 8b94076ee181df94912d11cdb2d9601cd55319cb 394 393 2012-08-19T22:02:40Z Duck 2 /* WebDAV Interface */ wikitext text/x-wiki {{Template:Service | description = The OwnCloud service is a webservice used to access, sync, and share your personal data. Currently you can: * store your files (and in-place view/edit of certain extensions directly from the web interface) * manage your contacts * manage your calendars * <del>manage your tasks</del> (deactivated because broken at the moment) * manage your bookmarks (for web links) (it should be possible to sync with Firefox in the future) | prerequisite = | account = global | ipv6 = true | security_notes = This service is secure but beware when sharing your data to other people. }} {{warning}} Remember not to use this service to store illegal or non-free data. == Access == === Web Interface === Use this URL in your browser: https://stuff.milkypond.org/ Then you can setup your contacts, calendars, and store files. === WebDAV Interface === You can use the [[wikipedia:WebDAV|WebDAV]] interface to sync your data from a desktop application or you mobile device. Applications can use the main address of the web interface (see above) with your credentials and should be able to discover you data, but sometimes they have limitations and you need to specify a full ugly link ; in this case you can find the link in the interface, either on the resource to access or in your personal settings page. ==== Files ==== * Desktop: ** remote drive (synchrounous): use XFCE/Gigolo or GNOME/Nautilus ** synchronize (asynchronous): use the [http://owncloud.org/support/sync-clients/ csync] utility * Mobile Devices: ** Android: use the [http://owncloud.org/support/android/ Owncloud] app (available on [http://f-droid.org/ F-Droid]) to synchronize files ==== Contacts ==== * Desktop: synchronize with GNOME/Evolution * Mobile Devices: ** Android: the [http://owncloud.org/support/android/ Owncloud] app should be able to do it in the future, but you may use the [http://dmfs.org/wiki/index.php?title=CardDAV-Sync CardDAV-Sync] app which is [http://dmfs.org/wiki/index.php?title=Open_source_status to be opensourced] * Webmail: ** Webdesk (Horde): does not work ** old webmail (Squirrelmail): does not work ** newest webmail (RoundCube): works nicely with the newest webmail (RoundCube) (see in Settings->Preferences->CardDAV) ==== Calendars: ==== * Desktop: synchronize with GNOME/Evolution * Mobile Devices: ** Android: the [http://owncloud.org/support/android/ Owncloud] app should be able to do it in the future, but you may use the [http://dmfs.org/wiki/index.php?title=CalDAV-Sync CalDAV-Sync] app which is [http://dmfs.org/wiki/index.php?title=Open_source_status to be opensourced], or try [http://acal.me/wiki/Main_Page aCal] (available on [http://f-droid.org/ F-Droid]) which does not use the internal calendar and proved quite slow * Webmail: ** Webdesk (Horde): does not work ** old webmail (Squirrelmail): does not work ** newest webmail (RoundCube): should work but it does not seem to parse events properly even if there's no errors (see in Settings->Preferences->Calendar and the Provider field) == Documentation == * ''OwnCloud'' section in the [http://owncloud.org/support/ Help Page] == Technical Details == This service is made using: * [http://owncloud.org/ OwnCloud] 4ba7778dc6dad8c8ea6dec80759f46ebbc9246ef 0 55 395 329 2012-09-04T23:05:33Z Duck 2 wikitext text/x-wiki {{Template:Service | description = [[wikipedia:Irc|IRC]] (Internet Relay Chat) is a chat system. We have our own internal network, formerly used to contact administrators and discuss with other users. Even is not advertise widely, external people may join the network, so you can invite your friend. | prerequisite = | account = | ipv6 = true | security_notes = Your messages are secured if you connect using the secure port(s), but you need to ensure the recipient uses a secure connection too ; this can be achieved using chanmode +S (see below). {{warning}} Unfortunately, due to a bug in the software (see {{dc-projects|233}}), the link between our servers is not yet fully secured, but you can work around this problem if you talk only to people connected to the same server as yourself. }} == Access == === Using an IRC Software === To connect you need and IRC client, like for example: * [http://irssi.org/ Irssi] * [http://www.pidgin.im Pidgin] * [http://weechat.org/ WeeChat] You need to configure these parameters: * host: irc.milkypond.org * port: ** 6680 (if you want a secure connection using SSL/TLS) ** 6667 or 6669 (because 6667 is sometimes filtered) No password is needed to connect. === Using a Web Interface === Use the following URL: https://irconweb.milkypond.org/ == Official Channels == * #MilkyPond: main channel used to meet with other users and friends and ask general questions * #DuckCorp: contact with DuckCorp Administrators and technical discussions * #News: news feeds on IRC (deprecated but still working) == Contacting IRC Administrators == In case of problems on IRC you can find connected administrators using this command (mind the idle time): /QUOTE STATS p Beware IRC Administrators may not be DuckCorp Administrators. == Features == === Commands === You can see available commands using this command: /QUOTE HELP You can get help about a particular command using this command: /QUOTE HELP &lt;command&gt; ==== Additional Commands for IRC Administrators ==== All special commands are listed in the Oper MOTD. === User Modes === You can see available channel modes using this command: /QUOTE HELP UMODE ==== Mode +g ==== (partial note from the ircd-ratbox documentation) When a client is set +g, that user will be in "Caller ID" mode. Any user that messages a +g client will receive a notice saying that they are in +g (server side ignore) mode. The target client (who is set +g) will also receive a notice saying that so and so messaged them, and that they are in +g mode. The target of the message will only receive one notification per minute, from any client, in order to help prevent flooding. The sender will '''not''' have the rate limit, and will receive a notice saying the target is in +g mode every time they send a message. Note that this behavior is similar to the way AWAY messages are done. There are numerous benefits for both opers and regular users, including the ability to stop spambot messages from ever reaching your client, stopping private message and CTCP floods, and being able to sit on IRC in privacy. One question that arises is how to message specific users, while blocking out everyone else. The command ACCEPT is your answer. To add a user to your accept list, issue the raw command: /QUOTE ACCEPT &lt;nick&gt;,&lt;nick&gt;,&lt;nick&gt;,… That user will now be able to send messages to your client until the association is broken. Associations break in one of the following situations: when an accepted user QUIT's (or is on the other side of a split), you QUIT, or the accepted user changes their nick. The reason why a remote user's nick change will remove them from your accept list is so that you cannot track a user after they changed their nick. Viewing the accept list is also very easy. Issue the raw command: /QUOTE ACCEPT * Removing a user from your accept list is also simple. Issue the command: /QUOTE ACCEPT -&lt;nick&gt; === Channel Modes === You can see available channel modes using this command: /QUOTE HELP CMODE These extra modes are also available: * +r - registered - Users must be registered with services to JOIN * +S - ssl only - Requires SSL/TLS connections to join === IRC Services === To help not loose your favorite nick or channel, the IRC Services can register them so you're still in control. It also helps manage channel with a variety of tools. Look at the user introduction manual in the documentation below. List of Services: * ALIS: search available channels * USERSERV: register an account List of Services available with an account (see USERSERV): * NICKSERV: register nicknames * CHANSERV: register and manage channels * MEMOSERV: send and receive memos from other registered users To get help on each service commands, use the following command: /QUOTE &lt;service&gt; HELP ==== Additional Services for IRC Administrators ==== (exact privileges depends on trust and delegation) * OPERSERV: superadmin commands * JUPESERV: manage "jupes" (fake connections to prevent unwanted links) * GLOBAL: messaging all users * BANSERV: managing global bans * OPERBOT: manage the OperBot * WATCHSERV: spy on service commands (only available via DCC) You also may be able to access services via DCC CHAT, which is handy when a flood occurs, using: /DCC CHAT operserv == Documentation == * [http://docs.ratbox.org/svc_userintro.shtml IRC Services Introduction] == Technical Details == This service is made using: * [http://www.ratbox.org/ ircd-ratbox] * [http://services.ratbox.org/ ratbox-services] e7a0dab69e42d2cc2594d4cb616ed5d80ccca182 0 50 396 338 2012-11-13T23:42:42Z Duck 2 /* Access */ wikitext text/x-wiki {{Template:Service | description = Remote [[wikipedia:Shell_(computing)|shell]] to a DuckCorp machine. | prerequisite = You need to ask an administrator for an account, but we need to know you well-enough to ensure you are trustable. This is '''not''' a VIP requirement, but such an access can be very dangerous and we don't know any other way to avoid a disaster, sorry. You also need to provide a RSA/DSA public key (see ''ssh-keygen''). | account = global-reg | ipv6 = true | security_notes = This service is secure. }} == Access == Via SSH with a RSA/DSA key on the following hosts: * thorfinn.duckcorp.org (prefered for lengthy sessions, like screens) * toushirou.duckcorp.org (mostly useful to manage Web/FTP data) == Available Resources == The following resources are available and will remain until we advertise a scheduled removal. If you miss something you can send us a request. === Locales === * en_GB.UTF-8 * en_US.UTF-8 * fr_FR.UTF-8 * ja_JP.EUC-JP * ja_JP.UTF-8 === Shells === * dash * bash * zsh * ksh * tcsh === Programs === * aspell * dict * emacs * irssi (with plugins) * latex (full TeXlive) * screen * sieve-connect * vim * w3m * weechat (with plugins) Additional tools: * [[Services/VCS|VCS tools]] == Technical Details == This service is made using: * [http://www.openssh.org/ OpenSSH] 081f47c1d931cf9da9bd90d629c34675a52928fc 397 396 2012-11-13T23:47:37Z Duck 2 /* Access */ wikitext text/x-wiki {{Template:Service | description = Remote [[wikipedia:Shell_(computing)|shell]] to a DuckCorp machine. | prerequisite = You need to ask an administrator for an account, but we need to know you well-enough to ensure you are trustable. This is '''not''' a VIP requirement, but such an access can be very dangerous and we don't know any other way to avoid a disaster, sorry. You also need to provide a RSA/DSA public key (see ''ssh-keygen''). | account = global-reg | ipv6 = true | security_notes = This service is secure. }} == Access == Via SSH with a RSA/DSA key on the following hosts: * thorfinn.duckcorp.org (prefered for lengthy sessions, like screens) * toushirou.duckcorp.org (mostly useful to manage Web/FTP data) Via SSH+[http://mosh.mit.edu/ Mosh], with the same hosts and conditions defined above. On Debian you can use the ''mosh'' package to get the client application and do ''mosh &lt;server&gt;''. On Android, the [http://dan.drown.org/android/mosh/ patched IrssiConnectbot from ddrown] is known to work as well. == Available Resources == The following resources are available and will remain until we advertise a scheduled removal. If you miss something you can send us a request. === Locales === * en_GB.UTF-8 * en_US.UTF-8 * fr_FR.UTF-8 * ja_JP.EUC-JP * ja_JP.UTF-8 === Shells === * dash * bash * zsh * ksh * tcsh === Programs === * aspell * dict * emacs * irssi (with plugins) * latex (full TeXlive) * screen * sieve-connect * vim * w3m * weechat (with plugins) Additional tools: * [[Services/VCS|VCS tools]] == Technical Details == This service is made using: * [http://www.openssh.org/ OpenSSH] 251f966689c8c1b6afcb328d1a52e8d0bf5afc7e 398 397 2012-11-13T23:48:52Z Duck 2 /* Locales */ wikitext text/x-wiki {{Template:Service | description = Remote [[wikipedia:Shell_(computing)|shell]] to a DuckCorp machine. | prerequisite = You need to ask an administrator for an account, but we need to know you well-enough to ensure you are trustable. This is '''not''' a VIP requirement, but such an access can be very dangerous and we don't know any other way to avoid a disaster, sorry. You also need to provide a RSA/DSA public key (see ''ssh-keygen''). | account = global-reg | ipv6 = true | security_notes = This service is secure. }} == Access == Via SSH with a RSA/DSA key on the following hosts: * thorfinn.duckcorp.org (prefered for lengthy sessions, like screens) * toushirou.duckcorp.org (mostly useful to manage Web/FTP data) Via SSH+[http://mosh.mit.edu/ Mosh], with the same hosts and conditions defined above. On Debian you can use the ''mosh'' package to get the client application and do ''mosh &lt;server&gt;''. On Android, the [http://dan.drown.org/android/mosh/ patched IrssiConnectbot from ddrown] is known to work as well. == Available Resources == The following resources are available and will remain until we advertise a scheduled removal. If you miss something you can send us a request. === Locales === {{warning}} warning for Mosh users: Mosh only supports UTF-8 locales * en_GB.UTF-8 * en_US.UTF-8 * fr_FR.UTF-8 * ja_JP.EUC-JP * ja_JP.UTF-8 === Shells === * dash * bash * zsh * ksh * tcsh === Programs === * aspell * dict * emacs * irssi (with plugins) * latex (full TeXlive) * screen * sieve-connect * vim * w3m * weechat (with plugins) Additional tools: * [[Services/VCS|VCS tools]] == Technical Details == This service is made using: * [http://www.openssh.org/ OpenSSH] 80677208bf3f5a58f749c01fb49bd57fc461d092 0 46 406 223 2013-08-22T08:53:53Z Arnau 8 /* TLS/SSL-based Services */ wikitext text/x-wiki == Introduction == '''All''' services containing sensitive information are protected using cryptography. Whenever possible, we add the necessary configuration to ensure unsecure usages are not possible, to protect your data. Nevertheless, a few things are needed on your side to improve security, that's why we are providing the following notes in order to help you configure your software in a secure fashion. == Areas of Security == === Mails from DC's Administrators === You should not trust mails pretenting to come from us. The only way to be sure a mail is from someone, is to agree on exchanging cryptographically-protected messages. On [[Admins|this page]] you'll find the list of DC's administrators from which you may receive mails (on the users's mailing-list for example). You could trust their GPG keys directly, but that would not be secure at all. The best way is to meet, live, in a [[wikipedia:Key_signing_party|key signing party]]. If a friend has already signed our key, and is not too far from you, you may also propagate your trust to our keys. Once done, you'll be sure what seems to come from us is really from us. === Talking to the Right Machine/Service === All remote services use an address on the internet, like ''superservice.duckcorp.org'', but if you are connected through an untrusted network (like if you're using a third-party's WIFI), you cannot be sure you'll be connecting to the right machine, and you may disclose important information like your credentials. ==== TLS/SSL-based Services ==== To ensure you're talking to the right server, and noone pretend to be a DC's server to tricks you, you need to install the following certificate ([[File:Duckcorp.crt]]): * either in your software configuration (for example, to validate HTTP site in your browser, clicking on the link should ask for installation, and you'll just need to confirm you trust it) ** For Firefox you must manually import the certificate ([http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=316436 #316436]): Preferences -> Advanced -> Certificates -> View Certificates -> Authorities -> Import. ** For Chromium too, you must manually import the certificate: Settings -> Show advanced settings -> Manage certificates -> Authorities -> Import. * or globally on your host by installing the certificate, as root: ** (method 1, prefered) in ''/usr/local/share/ca-certificates'', and running ''update-ca-certificates'' (the ''ca-certificates'' package needs to be installed) ** (method 2, not suitable for GNUTLS-based apps) in ''/etc/ssl/certs'', and running ''c_rehash'' (the ''openssl'' package needs to be installed) ==== Service Locator Security ==== One possible attack is to alter replies from the machine locator service (DNS) in order to redirect your communication to a nasty machine. Since November 2010, ''duckcorp.org'' and ''milkypond.org'' domains are cryptographically signed using the DNSSEC system, so you are now able to verify the address returned for the service is the right one. This system is not new, but has recently switched into production, so your operating system may not yet be properly configured to use this protection. Until it is pre-configured in most of them, you may configure it yourself using [[Services/DNS#How_to_test_my_zone_is_secured.3F|this procedure]]. {{warning}} Beware this protection solves certains security problems but is not sufficient to ensure you're talking to the right machine/service. Nevertheless it ensures: * the address of the machine/service is the right one * information related to the domain, list of mail servers, security information on hosts (SSHFP)… are not tampered Using this security plus certificate verification (see [[Services/Security#TLS.2FSSL-based_Services|section about TLS/SSL-based Security]]) would ensure full security. === Secure SSH Connections === In order not to be tricked connecting to a fake server, or to a rooted server (just in case), it is possible to check the SSH key of the server. As this verification is quite boring both for administrators and users, almost nobody on earth does it. Fortunately, it is possible to publish this information in the DNS and have OpenSSH check it for you automatically. To add this security, you can edit your system configuration (''/etc/ssh/ssh_config'') or your personal one (''~/.ssh/config''), and add the folowing: Host * VerifyHostKeyDNS ask Of course, the DNS replies may be altered, so if you want full security, read the [[Services/Security#Service_Locator_Security|section about Service Locator Security]]. ce6fda23b9758ada12bec6dcf9002006285d9b0b 0 31 408 228 2014-01-14T11:05:20Z Duck 2 wikitext text/x-wiki <fdp_graph> graph DcMap { label = "DuckCorp Architecture"; fontsize = 13; overlap = false; splines = true; edge [fontsize=10.0]; style = bold; node [fontsize=10.0]; labelloc = "t"; internet [label="Internet", fontsize=14, shape=tripleoctagon]; hivane [label="Hivane\nNetwork", fontsize=14, shape=house]; hivane -- internet [label="Hivane\nTransit", style=dashed]; subgraph cluster_hq { label = "DuckCorp HQ (DuckLand)"; color = green; labeljust = "l"; elwing [label="Elwing", URL="DcArchitecture/Elwing"]; daneel [label="Daneel", URL="DcArchitecture/Daneel"]; earendil [label="Eärendil\n(DOWN)", URL="DcArchitecture/Eärendil"]; modem_dc [label="ADSL Modem\n(Linksys ADSL2MUE)", shape=box]; sw_dc [label="Switch", shape=box]; sw_dc -- {elwing earendil daneel}; elwing -- {modem_dc}; subgraph cluster_hurdfr { label = "HurdFr (DuckLand part)"; URL = "http://www.hurdfr.org/"; color = darkviolet; labeljust = "l"; amroth [label="Amroth\n(DOWN)", URL="DcArchitecture/Amroth"]; } amroth -- sw_dc; } cluster_hq -- hivane [label="Nerim / Hivane\nADSL", style=dashed]; subgraph cluster_alionis { label = "Alionis Suite\n(Villebon Datacenter)"; URL = "http://maps.google.com/maps/ms?ie=UTF8&hl=en&msa=0&msid=105368272885926046620.0004600d15bf1a76aa1a9&t=h&z=15"; color = black; labeljust = "l"; orfeo [label="Orfeo", URL="DcArchitecture/Orfeo"]; } cluster_alionis -- hivane [label="Hivane / Alionis\nPeering", style=dashed]; subgraph cluster_frontier { label = "Frontier Housing"; color = orange; labeljust = "l"; jinta [label="Jinta\n(vserver)\n(DOWN)", URL="DcArchitecture/Jinta"]; } cluster_frontier -- internet [style=dashed]; subgraph cluster_nerim { label = "Nerim Suite\n(Equinix PA3 Datacenter)"; color = blue; labeljust = "l"; toushirou [label="Tōshirō", URL="DcArchitecture/Tōshirō"]; thorfinn [label="Thorfinn\n(Nerim Root VDS)", URL="DcArchitecture/Thorfinn"]; } cluster_nerim -- hivane [label="Nerim / Hivane\nPeering", style=dashed]; subgraph cluster_arnal { label = "Arnal's Lair"; color = violet; labeljust = "l"; korutopi [label="Korutopi\n(LXC)", URL="DcArchitecture/Korutopi"]; } cluster_arnal -- internet [style=dashed]; } <fdp_graph> 740de780527cb756457713afe4044b3eeffd7ee3 0 70 409 2014-01-25T19:07:26Z Duck 2 Created page with "{{Template:Service | description = Automatically find a changing (dynamic) IP address (home address for example) using this service. | prerequisite = | account = local | ipv6 ..." wikitext text/x-wiki {{Template:Service | description = Automatically find a changing (dynamic) IP address (home address for example) using this service. | prerequisite = | account = local | ipv6 = false | security_notes = This service is secured using keys. }} == Access == To use this service, ask for an account to an administrator. For each IP you need to track, you should be provided with: * HostID * AuthP lines * AuthQ lines === Configuration on Debian === Install the software: apt-get install dhis-client And add a block in your configuration file ''/etc/dhid.conf'' like this: == Technical Details == This service is made using: * [http://www.dhis.org/ DHIS] d68db3a64e5f89d02a15be5ab7ba9340d5c45f4e 410 409 2014-01-25T19:10:17Z Duck 2 wikitext text/x-wiki {{Template:Service | description = Automatically find a changing (dynamic) IP address (home address for example) using this service. | prerequisite = | account = local | ipv6 = false | security_notes = This service is secured using keys. }} == Access == To use this service, ask for an account to an administrator. For each IP you need to track, you should be provided with: * HostID * AuthP lines * AuthQ lines === Configuration on Debian === Install the software: apt-get install dhis-client And add a block in your configuration file ''/etc/dhid.conf'' like this: { HostID &lt;hostid&gt; ISAddr ddns.duckcorp.org Refresh 1200 AuthP &lt;auth-p-line-1&gt; AuthP &lt;auth-p-line-2&gt; AuthQ &lt;auth-q-line-1&gt; AuthQ &lt;auth-q-line-2&gt; } Restart the service: service dhis-client restart == Technical Details == This service is made using: * [http://www.dhis.org/ DHIS] 3d63dba5769c2c7348b1a06c032a69e3a9ee190b 411 410 2014-01-25T19:15:07Z Duck 2 /* Access */ wikitext text/x-wiki {{Template:Service | description = Automatically find a changing (dynamic) IP address (home address for example) using this service. | prerequisite = | account = local | ipv6 = false | security_notes = This service is secured using keys. }} == Access == To use this service, ask for an account to an administrator. For each IP you need to track, you should be provided with: * HostID * AuthP lines * AuthQ lines You also need to have the DHIS port opened, which is: UDP 58800. === Configuration on Debian === Install the software: apt-get install dhis-client And add a block in your configuration file ''/etc/dhid.conf'' like this: { HostID &lt;hostid&gt; ISAddr ddns.duckcorp.org Refresh 1200 AuthP &lt;auth-p-line-1&gt; AuthP &lt;auth-p-line-2&gt; AuthQ &lt;auth-q-line-1&gt; AuthQ &lt;auth-q-line-2&gt; } Restart the service: service dhis-client restart == Technical Details == This service is made using: * [http://www.dhis.org/ DHIS] 835ffa32e2641d46c44a2461fab50ee487ab8ec2 412 411 2014-01-25T19:43:59Z Duck 2 /* Configuration on Debian */ wikitext text/x-wiki {{Template:Service | description = Automatically find a changing (dynamic) IP address (home address for example) using this service. | prerequisite = | account = local | ipv6 = false | security_notes = This service is secured using keys. }} == Access == To use this service, ask for an account to an administrator. For each IP you need to track, you should be provided with: * HostID * AuthP lines * AuthQ lines You also need to have the DHIS port opened, which is: UDP 58800. === Configuration on Debian === Install the software: apt-get install dhis-client And add a block for each IP in your configuration file ''/etc/dhid.conf'' like this: { HostID &lt;hostid&gt; ISAddr ddns.duckcorp.org Refresh 1200 AuthP &lt;auth-p-line-1&gt; AuthP &lt;auth-p-line-2&gt; AuthQ &lt;auth-q-line-1&gt; AuthQ &lt;auth-q-line-2&gt; } Restart the service: service dhis-client restart == Technical Details == This service is made using: * [http://www.dhis.org/ DHIS] 80d3eb32895a5a007b6c421e735a26f38da3e38c 0 39 413 400 2014-01-29T02:53:03Z Duck 2 /* TODO */ wikitext text/x-wiki Here is a short overview of the services provided by DuckCorp. Our services are supervised and important data are [[Services/Backup|saved regularly]]. {{warning}} [[Services/Security|Notes about security !]] {| class="wikitable" style="text-align: center; width: 100%;" |+ Available Services |- ! Category !! colspan="2" | Service !! Access !! Description |- | rowspan="8" | Communication || rowspan="2" | Mail || [[Services/Mail|eMails]] || users || style="text-align: left;" | Mail boxes with anti-spam/anti-virus, filtering…, or mail redirections |- | [[Services/ML|Mailing-Lists]] || users || style="text-align: left;" | Distribution lists for mails |- | rowspan="3" | IRC || [[Services/IRC|IRC Network]] || public || style="text-align: left;" | MilkyPond Chat Network using a dedicated software or a Web-interface |- | [[Services/IRC-Bouncer|IRC Bouncer]] || users || style="text-align: left;" | IRC proxy (IRC server relaying IRC communications, keeping connections open and remembering logs) |- | [[Services/IRC-IM-GW|IRC to IM gateway]] || users || style="text-align: left;" | Communication to multiple instant messaging networks through a unified IRC-like interface |- | rowspan="2" | XMPP (Jabber) || [[Services/XMPP|XMPP Network]] || users || style="text-align: left;" | Global Chat Network (inter-communication between many [[wikipedia:Xmpp#History|well-known public IM services]]) |- | [[Services/XMPP WebGW|XMPP WebChat]] || users || style="text-align: left;" | Social Platform |- | colspan="2" | [[Services/Tribioune|Triboune Libre]] || public || style="text-align: left;" | MilkyPond Web-chat system inspired by [http://linuxfr.org/board the famous one] on [http://linuxfr.org/ Linuxfr.org] |- | rowspan="5" | Sharing || colspan="2" | [[Services/Gallery|Media Gallery]] || public/users || style="text-align: left;" | Photo and video gallery |- | colspan="2" | [[Services/Wiki|Wiki]] || public/users || style="text-align: left;" | Documentation, technical knowledge, useful tips… |- | colspan="2" | [[Services/OwnCloud|OwnCloud]] || public/users || style="text-align: left;" | Personal data store (contacts, calendars, files…) with syncing/sharing capabilities |- | rowspan="2" | Generic || [[Services/FTP|File Repository]] || public/users || style="text-align: left;" | Generic file sharing system (using FTP) |- | [[Services/SAFT|Shell Transfer]] || trusted || style="text-align: left;" | File transfer system using the SAFT protocol (shell access needed) |- | rowspan="3" | Utilities || colspan="2" | [[Services/WebFeeds|News WebReader]] || users || style="text-align: left;" | News feeds reader through a web interface |- | colspan="2" | [[Services/NTP|Time Server]] || public || style="text-align: left;" | System used to automatically setup time on your machines |- | colspan="2" | [[Services/Dico|Dictionary Server]] || public || style="text-align: left;" | Words searching system via a dedicated software (using the DICT protocol) or a Web-interface |- | rowspan="6" | Development || colspan="2" | [[Services/Projects|Project Management & Issue Tracking]] || public/users || style="text-align: left;" | Tool intended to help organize projects |- | colspan="2" | [[Services/CodeReview|Code Review]] || public/users || style="text-align: left;" | Tool intended to help improve software quality |- | colspan="2" | [[Services/VCS|VCS]] || public/users || style="text-align: left;" | Code/configuration versioning tools (Git, SVN, Baz, Bzr…) |- | rowspan="2" | Databases || [[Services/SQL|SQL]] || users || style="text-align: left;" | SQL server (PostgreSQL or MySQL) |- | [[Services/LDAP|LDAP]] || users || style="text-align: left;" | LDAP server (OpenLDAP) |- | colspan="2" | [[Services/SoftwareRepository|Software Repository]] || public/users || style="text-align: left;" | Software repository, to provide custom packages (think Debian debs) or installation media (thinks DVDs) |- | rowspan="6" | Hosting || colspan="2" | [[Services/DNS|DNS]] || users || style="text-align: left;" | Domain Name System (NS1/NS2, DNSSEC…) |- | rowspan="2" | Mail || [[Services/MailHosting|Mail Domains]] || users || style="text-align: left;" | Mail hosting (MX1/MX2) |- | [[Services/MLHosting|Mailing-Lists]] || users || style="text-align: left;" | Distribution lists for mail domains |- | colspan="2" | [[Services/WebHosting|Web Sites/Applications]] || users || style="text-align: left;" | Web pages using HTML/XHTML, CSS, JS, and various server-side programming languages (SSI, PHP, Perl, Python, Ruby…), and statistics (analytics data/reports) |- | colspan="2" | [[Services/XMPPHosting|XMPP Domains]] || users || style="text-align: left;" | XMPP Node for a custom domain |- | colspan="2" | [[Services/Shell|Shell]] || trusted || style="text-align: left;" | Useful for website administration, development, run custom scripts, persistent applications for text-mode geeks… |- | rowspan="2" | Network || colspan="2" | [[Services/IPv6-Broker|IPv6 tunnels]] || users || style="text-align: left;" | Access to the IPv6 world through an IPv4 connection |- | colspan="2" | [[Services/NSTX|NSTX]] || users || style="text-align: left;" | Access to the Internet through a restricted WIFI connection (via an IP over DNS tunnel) |} == TODO == * in Services/Wiki: https://wiki.duckcorp.org/ * in Services/Shell: link to SAFT * in Services/XMPP: chitchat * in Services/VCS: https://vcs.duckcorp.org/ * portal.dc.o * Radio … e567682a8bff0e20bfd3c21d5ac1f34fca913171 415 413 2014-02-02T15:29:20Z Duck 2 /* TODO */ wikitext text/x-wiki Here is a short overview of the services provided by DuckCorp. Our services are supervised and important data are [[Services/Backup|saved regularly]]. {{warning}} [[Services/Security|Notes about security !]] {| class="wikitable" style="text-align: center; width: 100%;" |+ Available Services |- ! Category !! colspan="2" | Service !! Access !! Description |- | rowspan="8" | Communication || rowspan="2" | Mail || [[Services/Mail|eMails]] || users || style="text-align: left;" | Mail boxes with anti-spam/anti-virus, filtering…, or mail redirections |- | [[Services/ML|Mailing-Lists]] || users || style="text-align: left;" | Distribution lists for mails |- | rowspan="3" | IRC || [[Services/IRC|IRC Network]] || public || style="text-align: left;" | MilkyPond Chat Network using a dedicated software or a Web-interface |- | [[Services/IRC-Bouncer|IRC Bouncer]] || users || style="text-align: left;" | IRC proxy (IRC server relaying IRC communications, keeping connections open and remembering logs) |- | [[Services/IRC-IM-GW|IRC to IM gateway]] || users || style="text-align: left;" | Communication to multiple instant messaging networks through a unified IRC-like interface |- | rowspan="2" | XMPP (Jabber) || [[Services/XMPP|XMPP Network]] || users || style="text-align: left;" | Global Chat Network (inter-communication between many [[wikipedia:Xmpp#History|well-known public IM services]]) |- | [[Services/XMPP WebGW|XMPP WebChat]] || users || style="text-align: left;" | Social Platform |- | colspan="2" | [[Services/Tribioune|Triboune Libre]] || public || style="text-align: left;" | MilkyPond Web-chat system inspired by [http://linuxfr.org/board the famous one] on [http://linuxfr.org/ Linuxfr.org] |- | rowspan="5" | Sharing || colspan="2" | [[Services/Gallery|Media Gallery]] || public/users || style="text-align: left;" | Photo and video gallery |- | colspan="2" | [[Services/Wiki|Wiki]] || public/users || style="text-align: left;" | Documentation, technical knowledge, useful tips… |- | colspan="2" | [[Services/OwnCloud|OwnCloud]] || public/users || style="text-align: left;" | Personal data store (contacts, calendars, files…) with syncing/sharing capabilities |- | rowspan="2" | Generic || [[Services/FTP|File Repository]] || public/users || style="text-align: left;" | Generic file sharing system (using FTP) |- | [[Services/SAFT|Shell Transfer]] || trusted || style="text-align: left;" | File transfer system using the SAFT protocol (shell access needed) |- | rowspan="3" | Utilities || colspan="2" | [[Services/WebFeeds|News WebReader]] || users || style="text-align: left;" | News feeds reader through a web interface |- | colspan="2" | [[Services/NTP|Time Server]] || public || style="text-align: left;" | System used to automatically setup time on your machines |- | colspan="2" | [[Services/Dico|Dictionary Server]] || public || style="text-align: left;" | Words searching system via a dedicated software (using the DICT protocol) or a Web-interface |- | rowspan="6" | Development || colspan="2" | [[Services/Projects|Project Management & Issue Tracking]] || public/users || style="text-align: left;" | Tool intended to help organize projects |- | colspan="2" | [[Services/CodeReview|Code Review]] || public/users || style="text-align: left;" | Tool intended to help improve software quality |- | colspan="2" | [[Services/VCS|VCS]] || public/users || style="text-align: left;" | Code/configuration versioning tools (Git, SVN, Baz, Bzr…) |- | rowspan="2" | Databases || [[Services/SQL|SQL]] || users || style="text-align: left;" | SQL server (PostgreSQL or MySQL) |- | [[Services/LDAP|LDAP]] || users || style="text-align: left;" | LDAP server (OpenLDAP) |- | colspan="2" | [[Services/SoftwareRepository|Software Repository]] || public/users || style="text-align: left;" | Software repository, to provide custom packages (think Debian debs) or installation media (thinks DVDs) |- | rowspan="6" | Hosting || colspan="2" | [[Services/DNS|DNS]] || users || style="text-align: left;" | Domain Name System (NS1/NS2, DNSSEC…) |- | rowspan="2" | Mail || [[Services/MailHosting|Mail Domains]] || users || style="text-align: left;" | Mail hosting (MX1/MX2) |- | [[Services/MLHosting|Mailing-Lists]] || users || style="text-align: left;" | Distribution lists for mail domains |- | colspan="2" | [[Services/WebHosting|Web Sites/Applications]] || users || style="text-align: left;" | Web pages using HTML/XHTML, CSS, JS, and various server-side programming languages (SSI, PHP, Perl, Python, Ruby…), and statistics (analytics data/reports) |- | colspan="2" | [[Services/XMPPHosting|XMPP Domains]] || users || style="text-align: left;" | XMPP Node for a custom domain |- | colspan="2" | [[Services/Shell|Shell]] || trusted || style="text-align: left;" | Useful for website administration, development, run custom scripts, persistent applications for text-mode geeks… |- | rowspan="2" | Network || colspan="2" | [[Services/IPv6-Broker|IPv6 tunnels]] || users || style="text-align: left;" | Access to the IPv6 world through an IPv4 connection |- | colspan="2" | [[Services/NSTX|NSTX]] || users || style="text-align: left;" | Access to the Internet through a restricted WIFI connection (via an IP over DNS tunnel) |} == TODO == * in Services/Wiki: https://wiki.duckcorp.org/ * in Services/Shell: link to SAFT * in Services/XMPP: chitchat * in Services/VCS: https://vcs.duckcorp.org/ * Radio … 9585f06940894cf4509e9bef9063c63b0ed3fa00 418 415 2014-02-13T01:10:54Z Duck 2 wikitext text/x-wiki Here is a short overview of the services provided by DuckCorp. Our services are supervised and important data are [[Services/Backup|saved regularly]]. {{warning}} [[Services/Security|Notes about security !]] {| class="wikitable" style="text-align: center; width: 100%;" |+ Available Services |- ! Category !! colspan="2" | Service !! Access !! Description |- | Entertainment || colspan="2" | [[Games/Minetest|Minetest]] || public/users || style="text-align: left;" | Minecraft-like game |- | rowspan="8" | Communication || rowspan="2" | Mail || [[Services/Mail|eMails]] || users || style="text-align: left;" | Mail boxes with anti-spam/anti-virus, filtering…, or mail redirections |- | [[Services/ML|Mailing-Lists]] || users || style="text-align: left;" | Distribution lists for mails |- | rowspan="3" | IRC || [[Services/IRC|IRC Network]] || public || style="text-align: left;" | MilkyPond Chat Network using a dedicated software or a Web-interface |- | [[Services/IRC-Bouncer|IRC Bouncer]] || users || style="text-align: left;" | IRC proxy (IRC server relaying IRC communications, keeping connections open and remembering logs) |- | [[Services/IRC-IM-GW|IRC to IM gateway]] || users || style="text-align: left;" | Communication to multiple instant messaging networks through a unified IRC-like interface |- | rowspan="2" | XMPP (Jabber) || [[Services/XMPP|XMPP Network]] || users || style="text-align: left;" | Global Chat Network (inter-communication between many [[wikipedia:Xmpp#History|well-known public IM services]]) |- | [[Services/XMPP WebGW|XMPP WebChat]] || users || style="text-align: left;" | Social Platform |- | colspan="2" | [[Services/Tribioune|Triboune Libre]] || public || style="text-align: left;" | MilkyPond Web-chat system inspired by [http://linuxfr.org/board the famous one] on [http://linuxfr.org/ Linuxfr.org] |- | rowspan="5" | Sharing || colspan="2" | [[Services/Gallery|Media Gallery]] || public/users || style="text-align: left;" | Photo and video gallery |- | colspan="2" | [[Services/Wiki|Wiki]] || public/users || style="text-align: left;" | Documentation, technical knowledge, useful tips… |- | colspan="2" | [[Services/OwnCloud|OwnCloud]] || public/users || style="text-align: left;" | Personal data store (contacts, calendars, files…) with syncing/sharing capabilities |- | rowspan="2" | Generic || [[Services/FTP|File Repository]] || public/users || style="text-align: left;" | Generic file sharing system (using FTP) |- | [[Services/SAFT|Shell Transfer]] || trusted || style="text-align: left;" | File transfer system using the SAFT protocol (shell access needed) |- | rowspan="3" | Utilities || colspan="2" | [[Services/WebFeeds|News WebReader]] || users || style="text-align: left;" | News feeds reader through a web interface |- | colspan="2" | [[Services/NTP|Time Server]] || public || style="text-align: left;" | System used to automatically setup time on your machines |- | colspan="2" | [[Services/Dico|Dictionary Server]] || public || style="text-align: left;" | Words searching system via a dedicated software (using the DICT protocol) or a Web-interface |- | rowspan="6" | Development || colspan="2" | [[Services/Projects|Project Management & Issue Tracking]] || public/users || style="text-align: left;" | Tool intended to help organize projects |- | colspan="2" | [[Services/CodeReview|Code Review]] || public/users || style="text-align: left;" | Tool intended to help improve software quality |- | colspan="2" | [[Services/VCS|VCS]] || public/users || style="text-align: left;" | Code/configuration versioning tools (Git, SVN, Baz, Bzr…) |- | rowspan="2" | Databases || [[Services/SQL|SQL]] || users || style="text-align: left;" | SQL server (PostgreSQL or MySQL) |- | [[Services/LDAP|LDAP]] || users || style="text-align: left;" | LDAP server (OpenLDAP) |- | colspan="2" | [[Services/SoftwareRepository|Software Repository]] || public/users || style="text-align: left;" | Software repository, to provide custom packages (think Debian debs) or installation media (thinks DVDs) |- | rowspan="6" | Hosting || colspan="2" | [[Services/DNS|DNS]] || users || style="text-align: left;" | Domain Name System (NS1/NS2, DNSSEC…) |- | rowspan="2" | Mail || [[Services/MailHosting|Mail Domains]] || users || style="text-align: left;" | Mail hosting (MX1/MX2) |- | [[Services/MLHosting|Mailing-Lists]] || users || style="text-align: left;" | Distribution lists for mail domains |- | colspan="2" | [[Services/WebHosting|Web Sites/Applications]] || users || style="text-align: left;" | Web pages using HTML/XHTML, CSS, JS, and various server-side programming languages (SSI, PHP, Perl, Python, Ruby…), and statistics (analytics data/reports) |- | colspan="2" | [[Services/XMPPHosting|XMPP Domains]] || users || style="text-align: left;" | XMPP Node for a custom domain |- | colspan="2" | [[Services/Shell|Shell]] || trusted || style="text-align: left;" | Useful for website administration, development, run custom scripts, persistent applications for text-mode geeks… |- | rowspan="2" | Network || colspan="2" | [[Services/IPv6-Broker|IPv6 tunnels]] || users || style="text-align: left;" | Access to the IPv6 world through an IPv4 connection |- | colspan="2" | [[Services/NSTX|NSTX]] || users || style="text-align: left;" | Access to the Internet through a restricted WIFI connection (via an IP over DNS tunnel) |} == TODO == * in Services/Wiki: https://wiki.duckcorp.org/ * in Services/Shell: link to SAFT * in Services/XMPP: chitchat * in Services/VCS: https://vcs.duckcorp.org/ * Radio … 3b3d7c5871388681a084cc2c975a290d62179e33 420 418 2014-02-13T01:30:21Z Duck 2 wikitext text/x-wiki Here is a short overview of the services provided by DuckCorp. Our services are supervised and important data are [[Services/Backup|saved regularly]]. {{warning}} [[Services/Security|Notes about security !]] {| class="wikitable" style="text-align: center; width: 100%;" |+ Available Services |- ! Category !! colspan="2" | Service !! Access !! Status !! Description |- | Entertainment || colspan="2" | [[Games/Minetest|Minetest]] || public/users || {{status_ok}} || style="text-align: left;" | Minecraft-like game |- | rowspan="8" | Communication || rowspan="2" | Mail || [[Services/Mail|eMails]] || users || {{status_ok}} || style="text-align: left;" | Mail boxes with anti-spam/anti-virus, filtering…, or mail redirections |- | [[Services/ML|Mailing-Lists]] || users || {{status_ok}} || style="text-align: left;" | Distribution lists for mails |- | rowspan="3" | IRC || [[Services/IRC|IRC Network]] || public || {{status_ok}} || style="text-align: left;" | MilkyPond Chat Network using a dedicated software or a Web-interface |- | [[Services/IRC-Bouncer|IRC Bouncer]] || users || {{status_ok}} || style="text-align: left;" | IRC proxy (IRC server relaying IRC communications, keeping connections open and remembering logs) |- | [[Services/IRC-IM-GW|IRC to IM gateway]] || users || {{status_ok}} || style="text-align: left;" | Communication to multiple instant messaging networks through a unified IRC-like interface |- | rowspan="2" | XMPP (Jabber) || [[Services/XMPP|XMPP Network]] || users || {{status_problems}} || style="text-align: left;" | Global Chat Network (inter-communication between many [[wikipedia:Xmpp#History|well-known public IM services]]) |- | [[Services/XMPP WebGW|XMPP WebChat]] || users || {{status_down}} || style="text-align: left;" | Social Platform |- | colspan="2" | [[Services/Tribioune|Triboune Libre]] || public || {{status_down}} || style="text-align: left;" | MilkyPond Web-chat system inspired by [http://linuxfr.org/board the famous one] on [http://linuxfr.org/ Linuxfr.org] |- | rowspan="5" | Sharing || colspan="2" | [[Services/Gallery|Media Gallery]] || public/users || {{status_ok}} || style="text-align: left;" | Photo and video gallery |- | colspan="2" | [[Services/Wiki|Wiki]] || public/users || {{status_ok}} || style="text-align: left;" | Documentation, technical knowledge, useful tips… |- | colspan="2" | [[Services/OwnCloud|OwnCloud]] || public/users || {{status_ok}} || style="text-align: left;" | Personal data store (contacts, calendars, files…) with syncing/sharing capabilities |- | rowspan="2" | Generic || [[Services/FTP|File Repository]] || public/users || {{status_ok}} || style="text-align: left;" | Generic file sharing system (using FTP) |- | [[Services/SAFT|Shell Transfer]] || trusted || {{status_ok}} || style="text-align: left;" | File transfer system using the SAFT protocol (shell access needed) |- | rowspan="3" | Utilities || colspan="2" | [[Services/WebFeeds|News WebReader]] || users || {{status_ok}} || style="text-align: left;" | News feeds reader through a web interface |- | colspan="2" | [[Services/NTP|Time Server]] || public || {{status_ok}} || style="text-align: left;" | System used to automatically setup time on your machines |- | colspan="2" | [[Services/Dico|Dictionary Server]] || public || {{status_ok}} || style="text-align: left;" | Words searching system via a dedicated software (using the DICT protocol) or a Web-interface |- | rowspan="6" | Development || colspan="2" | [[Services/Projects|Project Management & Issue Tracking]] || public/users || {{status_ok}} || style="text-align: left;" | Tool intended to help organize projects |- | colspan="2" | [[Services/CodeReview|Code Review]] || public/users || {{status_down}} || style="text-align: left;" | Tool intended to help improve software quality |- | colspan="2" | [[Services/VCS|VCS]] || public/users || {{status_ok}} || style="text-align: left;" | Code/configuration versioning tools (Git, SVN, Baz, Bzr…) |- | rowspan="2" | Databases || [[Services/SQL|SQL]] || users || {{status_ok}} || style="text-align: left;" | SQL server (PostgreSQL or MySQL) |- | [[Services/LDAP|LDAP]] || users || {{status_ok}} || style="text-align: left;" | LDAP server (OpenLDAP) |- | colspan="2" | [[Services/SoftwareRepository|Software Repository]] || public/users || {{status_ok}} || style="text-align: left;" | Software repository, to provide custom packages (think Debian debs) or installation media (thinks DVDs) |- | rowspan="6" | Hosting || colspan="2" | [[Services/DNS|DNS]] || users || {{status_ok}} || style="text-align: left;" | Domain Name System (NS1/NS2, DNSSEC…) |- | rowspan="2" | Mail || [[Services/MailHosting|Mail Domains]] || users || {{status_ok}} || style="text-align: left;" | Mail hosting (MX1/MX2) |- | [[Services/MLHosting|Mailing-Lists]] || users || {{status_ok}} || style="text-align: left;" | Distribution lists for mail domains |- | colspan="2" | [[Services/WebHosting|Web Sites/Applications]] || users || {{status_ok}} || style="text-align: left;" | Web pages using HTML/XHTML, CSS, JS, and various server-side programming languages (SSI, PHP, Perl, Python, Ruby…), and statistics (analytics data/reports) |- | colspan="2" | [[Services/XMPPHosting|XMPP Domains]] || users || {{status_ok}} || style="text-align: left;" | XMPP Node for a custom domain |- | colspan="2" | [[Services/Shell|Shell]] || trusted || {{status_ok}} || style="text-align: left;" | Useful for website administration, development, run custom scripts, persistent applications for text-mode geeks… |- | rowspan="2" | Network || colspan="2" | [[Services/IPv6-Broker|IPv6 tunnels]] || users || {{status_down}} || style="text-align: left;" | Access to the IPv6 world through an IPv4 connection |- | colspan="2" | [[Services/NSTX|NSTX]] || users || {{status_ok}} || style="text-align: left;" | Access to the Internet through a restricted WIFI connection (via an IP over DNS tunnel) |} == TODO == * in Services/Wiki: https://wiki.duckcorp.org/ * in Services/Shell: link to SAFT * in Services/XMPP: chitchat * in Services/VCS: https://vcs.duckcorp.org/ * Radio … b50887dd77ec9adc997ac0349e199daa3020e7fc 431 420 2014-03-10T14:06:03Z Duck 2 wikitext text/x-wiki Here is a short overview of the services provided by DuckCorp. Our services are supervised and important data are [[Services/Backup|saved regularly]]. {{warning}} [[Services/Security|Notes about security !]] {| class="wikitable" style="text-align: center; width: 100%;" |+ Available Services |- ! Category !! colspan="2" | Service !! Access !! Status !! Description |- | Entertainment || colspan="2" | [[Games/Minetest|Minetest]] || public/users || {{status_ok}} || style="text-align: left;" | Minecraft-like game |- | rowspan="8" | Communication || rowspan="2" | Mail || [[Services/Mail|eMails]] || users || {{status_ok}} || style="text-align: left;" | Mail boxes with anti-spam/anti-virus, filtering…, or mail redirections |- | [[Services/ML|Mailing-Lists]] || users || {{status_ok}} || style="text-align: left;" | Distribution lists for mails |- | rowspan="3" | IRC || [[Services/IRC|IRC Network]] || public || {{status_ok}} || style="text-align: left;" | MilkyPond Chat Network using a dedicated software or a Web-interface |- | [[Services/IRC-Bouncer|IRC Bouncer]] || users || {{status_ok}} || style="text-align: left;" | IRC proxy (IRC server relaying IRC communications, keeping connections open and remembering logs) |- | [[Services/IRC-IM-GW|IRC to IM gateway]] || users || {{status_ok}} || style="text-align: left;" | Communication to multiple instant messaging networks through a unified IRC-like interface |- | rowspan="2" | XMPP (Jabber) || [[Services/XMPP|XMPP Network]] || users || {{status_ok}} || style="text-align: left;" | Global Chat Network (inter-communication between many [[wikipedia:Xmpp#History|well-known public IM services]]) |- | [[Services/XMPP WebGW|XMPP WebChat]] || users || {{status_down}} || style="text-align: left;" | Social Platform |- | colspan="2" | [[Services/Tribioune|Triboune Libre]] || public || {{status_down}} || style="text-align: left;" | MilkyPond Web-chat system inspired by [http://linuxfr.org/board the famous one] on [http://linuxfr.org/ Linuxfr.org] |- | rowspan="5" | Sharing || colspan="2" | [[Services/Gallery|Media Gallery]] || public/users || {{status_ok}} || style="text-align: left;" | Photo and video gallery |- | colspan="2" | [[Services/Wiki|Wiki]] || public/users || {{status_ok}} || style="text-align: left;" | Documentation, technical knowledge, useful tips… |- | colspan="2" | [[Services/OwnCloud|OwnCloud]] || public/users || {{status_ok}} || style="text-align: left;" | Personal data store (contacts, calendars, files…) with syncing/sharing capabilities |- | rowspan="2" | Generic || [[Services/FTP|File Repository]] || public/users || {{status_ok}} || style="text-align: left;" | Generic file sharing system (using FTP) |- | [[Services/SAFT|Shell Transfer]] || trusted || {{status_ok}} || style="text-align: left;" | File transfer system using the SAFT protocol (shell access needed) |- | rowspan="3" | Utilities || colspan="2" | [[Services/WebFeeds|News WebReader]] || users || {{status_ok}} || style="text-align: left;" | News feeds reader through a web interface |- | colspan="2" | [[Services/NTP|Time Server]] || public || {{status_ok}} || style="text-align: left;" | System used to automatically setup time on your machines |- | colspan="2" | [[Services/Dico|Dictionary Server]] || public || {{status_ok}} || style="text-align: left;" | Words searching system via a dedicated software (using the DICT protocol) or a Web-interface |- | rowspan="6" | Development || colspan="2" | [[Services/Projects|Project Management & Issue Tracking]] || public/users || {{status_ok}} || style="text-align: left;" | Tool intended to help organize projects |- | colspan="2" | [[Services/CodeReview|Code Review]] || public/users || {{status_down}} || style="text-align: left;" | Tool intended to help improve software quality |- | colspan="2" | [[Services/VCS|VCS]] || public/users || {{status_ok}} || style="text-align: left;" | Code/configuration versioning tools (Git, SVN, Baz, Bzr…) |- | rowspan="2" | Databases || [[Services/SQL|SQL]] || users || {{status_ok}} || style="text-align: left;" | SQL server (PostgreSQL or MySQL) |- | [[Services/LDAP|LDAP]] || users || {{status_ok}} || style="text-align: left;" | LDAP server (OpenLDAP) |- | colspan="2" | [[Services/SoftwareRepository|Software Repository]] || public/users || {{status_ok}} || style="text-align: left;" | Software repository, to provide custom packages (think Debian debs) or installation media (thinks DVDs) |- | rowspan="6" | Hosting || colspan="2" | [[Services/DNS|DNS]] || users || {{status_ok}} || style="text-align: left;" | Domain Name System (NS1/NS2, DNSSEC…) |- | rowspan="2" | Mail || [[Services/MailHosting|Mail Domains]] || users || {{status_ok}} || style="text-align: left;" | Mail hosting (MX1/MX2) |- | [[Services/MLHosting|Mailing-Lists]] || users || {{status_ok}} || style="text-align: left;" | Distribution lists for mail domains |- | colspan="2" | [[Services/WebHosting|Web Sites/Applications]] || users || {{status_ok}} || style="text-align: left;" | Web pages using HTML/XHTML, CSS, JS, and various server-side programming languages (SSI, PHP, Perl, Python, Ruby…), and statistics (analytics data/reports) |- | colspan="2" | [[Services/XMPPHosting|XMPP Domains]] || users || {{status_ok}} || style="text-align: left;" | XMPP Node for a custom domain |- | colspan="2" | [[Services/Shell|Shell]] || trusted || {{status_ok}} || style="text-align: left;" | Useful for website administration, development, run custom scripts, persistent applications for text-mode geeks… |- | rowspan="2" | Network || colspan="2" | [[Services/IPv6-Broker|IPv6 tunnels]] || users || {{status_down}} || style="text-align: left;" | Access to the IPv6 world through an IPv4 connection |- | colspan="2" | [[Services/NSTX|NSTX]] || users || {{status_ok}} || style="text-align: left;" | Access to the Internet through a restricted WIFI connection (via an IP over DNS tunnel) |} == TODO == * in Services/Wiki: https://wiki.duckcorp.org/ * in Services/Shell: link to SAFT * in Services/XMPP: chitchat * in Services/VCS: https://vcs.duckcorp.org/ * Radio … 3dd457b845b0daf5e4c30a2a2b32cce594267593 461 431 2017-01-22T14:16:07Z Duck 2 wikitext text/x-wiki Here is a short overview of the services provided by DuckCorp. Our services are supervised and important data are [[Services/Backup|saved regularly]]. {{warning}} [[Services/Security|Notes about security !]] {| class="wikitable" style="text-align: center; width: 100%;" |+ Available Services |- ! Category !! colspan="2" | Service !! Access !! Status !! Description |- | Entertainment || colspan="2" | [[Games/Minetest|Minetest]] || public/users || {{status_ok}} || style="text-align: left;" | Minecraft-like game |- | rowspan="8" | Communication || rowspan="2" | Mail || [[Services/Mail|eMails]] || users || {{status_ok}} || style="text-align: left;" | Mail boxes with anti-spam/anti-virus, filtering…, or mail redirections |- | [[Services/ML|Mailing-Lists]] || users || {{status_ok}} || style="text-align: left;" | Distribution lists for mails |- | rowspan="3" | IRC || [[Services/IRC|IRC Network]] || public || {{status_ok}} || style="text-align: left;" | MilkyPond Chat Network using a dedicated software or a Web-interface |- | [[Services/IRC-Bouncer|IRC Bouncer]] || users || {{status_ok}} || style="text-align: left;" | IRC proxy (IRC server relaying IRC communications, keeping connections open and remembering logs) |- | [[Services/IRC-IM-GW|IRC to IM gateway]] || users || {{status_ok}} || style="text-align: left;" | Communication to multiple instant messaging networks through a unified IRC-like interface |- | rowspan="2" | XMPP (Jabber) || [[Services/XMPP|XMPP Network]] || users || {{status_ok}} || style="text-align: left;" | Global Chat Network (inter-communication between many [[wikipedia:Xmpp#History|well-known public IM services]]) |- | [[Services/XMPP WebGW|XMPP WebChat]] || users || {{status_down}} || style="text-align: left;" | Social Platform |- | colspan="2" | [[Services/Tribioune|Triboune Libre]] || public || {{status_down}} || style="text-align: left;" | MilkyPond Web-chat system inspired by [http://linuxfr.org/board the famous one] on [http://linuxfr.org/ Linuxfr.org] |- | rowspan="5" | Sharing || colspan="2" | [[Services/Gallery|Media Gallery]] || public/users || {{status_ok}} || style="text-align: left;" | Photo and video gallery |- | colspan="2" | [[Services/Wiki|Wiki]] || public/users || {{status_ok}} || style="text-align: left;" | Documentation, technical knowledge, useful tips… |- | colspan="2" | [[Services/OwnCloud|OwnCloud]] || public/users || {{status_ok}} || style="text-align: left;" | Personal data store (contacts, calendars, files…) with syncing/sharing capabilities |- | rowspan="2" | Generic || [[Services/FTP|File Repository]] || public/users || {{status_ok}} || style="text-align: left;" | Generic file sharing system (using FTP) |- | [[Services/SAFT|Shell Transfer]] || trusted || {{status_ok}} || style="text-align: left;" | File transfer system using the SAFT protocol (shell access needed) |- | rowspan="3" | Utilities || colspan="2" | [[Services/WebFeeds|News WebReader]] || users || {{status_ok}} || style="text-align: left;" | News feeds reader through a web interface |- | colspan="2" | [[Services/NTP|Time Server]] || public || {{status_ok}} || style="text-align: left;" | System used to automatically setup time on your machines |- | colspan="2" | [[Services/Dico|Dictionary Server]] || public || {{status_ok}} || style="text-align: left;" | Words searching system via a dedicated software (using the DICT protocol) or a Web-interface |- | rowspan="6" | Development || colspan="2" | [[Services/Projects|Project Management & Issue Tracking]] || public/users || {{status_ok}} || style="text-align: left;" | Tool intended to help organize projects |- | colspan="2" | [[Services/CodeReview|Code Review]] || public/users || {{status_down}} || style="text-align: left;" | Tool intended to help improve software quality |- | colspan="2" | [[Services/VCS|VCS]] || public/users || {{status_ok}} || style="text-align: left;" | Code/configuration versioning tools (Git, SVN, Baz, Bzr…) |- | rowspan="2" | Databases || [[Services/SQL|SQL]] || users || {{status_ok}} || style="text-align: left;" | SQL server (PostgreSQL or MySQL) |- | [[Services/LDAP|LDAP]] || users || {{status_ok}} || style="text-align: left;" | LDAP server (OpenLDAP) |- | colspan="2" | [[Services/SoftwareRepository|Software Repository]] || public/users || {{status_ok}} || style="text-align: left;" | Software repository, to provide custom packages (think Debian debs) or installation media (thinks DVDs) |- | rowspan="7" | Hosting || rowspan="2" | Hostnames Directory || [[Services/DNS|DNS]] || users || {{status_ok}} || style="text-align: left;" | Domain Name System (NS1/NS2, DNSSEC…) |- | [[Services/DDNS|Dynamic DNS]] || users || {{status_ok}} || style="text-align: left;" | Dynamic DNS entries, for places where IPs are dynamic and not under your control |- | rowspan="2" | Mail || [[Services/MailHosting|Mail Domains]] || users || {{status_ok}} || style="text-align: left;" | Mail hosting (MX1/MX2) |- | [[Services/MLHosting|Mailing-Lists]] || users || {{status_ok}} || style="text-align: left;" | Distribution lists for mail domains |- | colspan="2" | [[Services/WebHosting|Web Sites/Applications]] || users || {{status_ok}} || style="text-align: left;" | Web pages using HTML/XHTML, CSS, JS, and various server-side programming languages (SSI, PHP, Perl, Python, Ruby…), and statistics (analytics data/reports) |- | colspan="2" | [[Services/XMPPHosting|XMPP Domains]] || users || {{status_ok}} || style="text-align: left;" | XMPP Node for a custom domain |- | colspan="2" | [[Services/Shell|Shell]] || trusted || {{status_ok}} || style="text-align: left;" | Useful for website administration, development, run custom scripts, persistent applications for text-mode geeks… |- | rowspan="2" | Network || colspan="2" | [[Services/IPv6-Broker|IPv6 tunnels]] || users || {{status_down}} || style="text-align: left;" | Access to the IPv6 world through an IPv4 connection |- | colspan="2" | [[Services/NSTX|NSTX]] || users || {{status_ok}} || style="text-align: left;" | Access to the Internet through a restricted WIFI connection (via an IP over DNS tunnel) |} == TODO == * in Services/Wiki: https://wiki.duckcorp.org/ * in Services/Shell: link to SAFT * in Services/XMPP: chitchat * in Services/VCS: https://vcs.duckcorp.org/ * Radio … 401b64b861b569689acd36915eca97f49841af0f 462 461 2017-01-22T14:19:11Z Duck 2 /* TODO */ wikitext text/x-wiki Here is a short overview of the services provided by DuckCorp. Our services are supervised and important data are [[Services/Backup|saved regularly]]. {{warning}} [[Services/Security|Notes about security !]] {| class="wikitable" style="text-align: center; width: 100%;" |+ Available Services |- ! Category !! colspan="2" | Service !! Access !! Status !! Description |- | Entertainment || colspan="2" | [[Games/Minetest|Minetest]] || public/users || {{status_ok}} || style="text-align: left;" | Minecraft-like game |- | rowspan="8" | Communication || rowspan="2" | Mail || [[Services/Mail|eMails]] || users || {{status_ok}} || style="text-align: left;" | Mail boxes with anti-spam/anti-virus, filtering…, or mail redirections |- | [[Services/ML|Mailing-Lists]] || users || {{status_ok}} || style="text-align: left;" | Distribution lists for mails |- | rowspan="3" | IRC || [[Services/IRC|IRC Network]] || public || {{status_ok}} || style="text-align: left;" | MilkyPond Chat Network using a dedicated software or a Web-interface |- | [[Services/IRC-Bouncer|IRC Bouncer]] || users || {{status_ok}} || style="text-align: left;" | IRC proxy (IRC server relaying IRC communications, keeping connections open and remembering logs) |- | [[Services/IRC-IM-GW|IRC to IM gateway]] || users || {{status_ok}} || style="text-align: left;" | Communication to multiple instant messaging networks through a unified IRC-like interface |- | rowspan="2" | XMPP (Jabber) || [[Services/XMPP|XMPP Network]] || users || {{status_ok}} || style="text-align: left;" | Global Chat Network (inter-communication between many [[wikipedia:Xmpp#History|well-known public IM services]]) |- | [[Services/XMPP WebGW|XMPP WebChat]] || users || {{status_down}} || style="text-align: left;" | Social Platform |- | colspan="2" | [[Services/Tribioune|Triboune Libre]] || public || {{status_down}} || style="text-align: left;" | MilkyPond Web-chat system inspired by [http://linuxfr.org/board the famous one] on [http://linuxfr.org/ Linuxfr.org] |- | rowspan="5" | Sharing || colspan="2" | [[Services/Gallery|Media Gallery]] || public/users || {{status_ok}} || style="text-align: left;" | Photo and video gallery |- | colspan="2" | [[Services/Wiki|Wiki]] || public/users || {{status_ok}} || style="text-align: left;" | Documentation, technical knowledge, useful tips… |- | colspan="2" | [[Services/OwnCloud|OwnCloud]] || public/users || {{status_ok}} || style="text-align: left;" | Personal data store (contacts, calendars, files…) with syncing/sharing capabilities |- | rowspan="2" | Generic || [[Services/FTP|File Repository]] || public/users || {{status_ok}} || style="text-align: left;" | Generic file sharing system (using FTP) |- | [[Services/SAFT|Shell Transfer]] || trusted || {{status_ok}} || style="text-align: left;" | File transfer system using the SAFT protocol (shell access needed) |- | rowspan="3" | Utilities || colspan="2" | [[Services/WebFeeds|News WebReader]] || users || {{status_ok}} || style="text-align: left;" | News feeds reader through a web interface |- | colspan="2" | [[Services/NTP|Time Server]] || public || {{status_ok}} || style="text-align: left;" | System used to automatically setup time on your machines |- | colspan="2" | [[Services/Dico|Dictionary Server]] || public || {{status_ok}} || style="text-align: left;" | Words searching system via a dedicated software (using the DICT protocol) or a Web-interface |- | rowspan="6" | Development || colspan="2" | [[Services/Projects|Project Management & Issue Tracking]] || public/users || {{status_ok}} || style="text-align: left;" | Tool intended to help organize projects |- | colspan="2" | [[Services/CodeReview|Code Review]] || public/users || {{status_down}} || style="text-align: left;" | Tool intended to help improve software quality |- | colspan="2" | [[Services/VCS|VCS]] || public/users || {{status_ok}} || style="text-align: left;" | Code/configuration versioning tools (Git, SVN, Baz, Bzr…) |- | rowspan="2" | Databases || [[Services/SQL|SQL]] || users || {{status_ok}} || style="text-align: left;" | SQL server (PostgreSQL or MySQL) |- | [[Services/LDAP|LDAP]] || users || {{status_ok}} || style="text-align: left;" | LDAP server (OpenLDAP) |- | colspan="2" | [[Services/SoftwareRepository|Software Repository]] || public/users || {{status_ok}} || style="text-align: left;" | Software repository, to provide custom packages (think Debian debs) or installation media (thinks DVDs) |- | rowspan="7" | Hosting || rowspan="2" | Hostnames Directory || [[Services/DNS|DNS]] || users || {{status_ok}} || style="text-align: left;" | Domain Name System (NS1/NS2, DNSSEC…) |- | [[Services/DDNS|Dynamic DNS]] || users || {{status_ok}} || style="text-align: left;" | Dynamic DNS entries, for places where IPs are dynamic and not under your control |- | rowspan="2" | Mail || [[Services/MailHosting|Mail Domains]] || users || {{status_ok}} || style="text-align: left;" | Mail hosting (MX1/MX2) |- | [[Services/MLHosting|Mailing-Lists]] || users || {{status_ok}} || style="text-align: left;" | Distribution lists for mail domains |- | colspan="2" | [[Services/WebHosting|Web Sites/Applications]] || users || {{status_ok}} || style="text-align: left;" | Web pages using HTML/XHTML, CSS, JS, and various server-side programming languages (SSI, PHP, Perl, Python, Ruby…), and statistics (analytics data/reports) |- | colspan="2" | [[Services/XMPPHosting|XMPP Domains]] || users || {{status_ok}} || style="text-align: left;" | XMPP Node for a custom domain |- | colspan="2" | [[Services/Shell|Shell]] || trusted || {{status_ok}} || style="text-align: left;" | Useful for website administration, development, run custom scripts, persistent applications for text-mode geeks… |- | rowspan="2" | Network || colspan="2" | [[Services/IPv6-Broker|IPv6 tunnels]] || users || {{status_down}} || style="text-align: left;" | Access to the IPv6 world through an IPv4 connection |- | colspan="2" | [[Services/NSTX|NSTX]] || users || {{status_ok}} || style="text-align: left;" | Access to the Internet through a restricted WIFI connection (via an IP over DNS tunnel) |} == TODO == * in Services/Wiki: https://wiki.duckcorp.org/ * in Services/Shell: link to SAFT * in Services/VCS: https://vcs.duckcorp.org/ * Radio … 75ce22cf7206b82ddf0534143efa3b8f6118d836 0 50 414 398 2014-02-02T15:28:29Z Duck 2 /* Access */ wikitext text/x-wiki {{Template:Service | description = Remote [[wikipedia:Shell_(computing)|shell]] to a DuckCorp machine. | prerequisite = You need to ask an administrator for an account, but we need to know you well-enough to ensure you are trustable. This is '''not''' a VIP requirement, but such an access can be very dangerous and we don't know any other way to avoid a disaster, sorry. You also need to provide a RSA/DSA public key (see ''ssh-keygen''). | account = global-reg | ipv6 = true | security_notes = This service is secure. }} == Access == Via SSH with a RSA/DSA/ECDSA key on the following hosts: * thorfinn.duckcorp.org (prefered for lengthy sessions, like screens) * toushirou.duckcorp.org (mostly useful to manage Web/FTP data) Via SSH+[http://mosh.mit.edu/ Mosh], with the same hosts and conditions defined above. On Debian you can use the ''mosh'' package to get the client application and do ''mosh &lt;server&gt;''. On Android, the [http://dan.drown.org/android/mosh/ patched IrssiConnectbot from ddrown] is known to work as well. === Locked behind a firewall === If you are obliged to go through a firewall (at work for eg), you can try a few things to through and end-up on Toushirou (and can bounce on Thorfinn then). First, if you know there is a proxy, or direct access does not work, you may be able to find the firewall host and port in the browser configuration. If there is none, then the proxy may be transparent (hidden) and you can try a direct SSH access using ''portal.duckcorp.org'' on port ''443''. If it does not work, you can try using a tool to wrap SSH through the firewall. From a terminal the ''corkscrew'' (Debian has a package of the same name) tool car be used with the following SSH configuration (in ''~/.ssh/config''): Host portal.duckcorp.org ProxyCommand /usr/bin/corkscrew &lt;proxy-host&gt; &lt;proxy-port&gt; %h %p and connect with: ssh portal.duckcorp.org == Available Resources == The following resources are available and will remain until we advertise a scheduled removal. If you miss something you can send us a request. === Locales === {{warning}} warning for Mosh users: Mosh only supports UTF-8 locales * en_GB.UTF-8 * en_US.UTF-8 * fr_FR.UTF-8 * ja_JP.EUC-JP * ja_JP.UTF-8 === Shells === * dash * bash * zsh * ksh * tcsh === Programs === * aspell * dict * emacs * irssi (with plugins) * latex (full TeXlive) * screen * sieve-connect * vim * w3m * weechat (with plugins) Additional tools: * [[Services/VCS|VCS tools]] == Technical Details == This service is made using: * [http://www.openssh.org/ OpenSSH] fdf43821df275b764bab8dd2069c3b3530b6964a 432 414 2014-03-12T11:58:35Z Duck 2 /* Programs */ wikitext text/x-wiki {{Template:Service | description = Remote [[wikipedia:Shell_(computing)|shell]] to a DuckCorp machine. | prerequisite = You need to ask an administrator for an account, but we need to know you well-enough to ensure you are trustable. This is '''not''' a VIP requirement, but such an access can be very dangerous and we don't know any other way to avoid a disaster, sorry. You also need to provide a RSA/DSA public key (see ''ssh-keygen''). | account = global-reg | ipv6 = true | security_notes = This service is secure. }} == Access == Via SSH with a RSA/DSA/ECDSA key on the following hosts: * thorfinn.duckcorp.org (prefered for lengthy sessions, like screens) * toushirou.duckcorp.org (mostly useful to manage Web/FTP data) Via SSH+[http://mosh.mit.edu/ Mosh], with the same hosts and conditions defined above. On Debian you can use the ''mosh'' package to get the client application and do ''mosh &lt;server&gt;''. On Android, the [http://dan.drown.org/android/mosh/ patched IrssiConnectbot from ddrown] is known to work as well. === Locked behind a firewall === If you are obliged to go through a firewall (at work for eg), you can try a few things to through and end-up on Toushirou (and can bounce on Thorfinn then). First, if you know there is a proxy, or direct access does not work, you may be able to find the firewall host and port in the browser configuration. If there is none, then the proxy may be transparent (hidden) and you can try a direct SSH access using ''portal.duckcorp.org'' on port ''443''. If it does not work, you can try using a tool to wrap SSH through the firewall. From a terminal the ''corkscrew'' (Debian has a package of the same name) tool car be used with the following SSH configuration (in ''~/.ssh/config''): Host portal.duckcorp.org ProxyCommand /usr/bin/corkscrew &lt;proxy-host&gt; &lt;proxy-port&gt; %h %p and connect with: ssh portal.duckcorp.org == Available Resources == The following resources are available and will remain until we advertise a scheduled removal. If you miss something you can send us a request. === Locales === {{warning}} warning for Mosh users: Mosh only supports UTF-8 locales * en_GB.UTF-8 * en_US.UTF-8 * fr_FR.UTF-8 * ja_JP.EUC-JP * ja_JP.UTF-8 === Shells === * dash * bash * zsh * ksh * tcsh === Programs === * aspell (with same support as system locales) * dict * emacs * irssi (with plugins and scripts) * latex (full TeXlive) * rsync * screen * sieve-connect * unison * vim * w3m * weechat (with plugins and scripts) Additional tools: * [[Services/VCS|VCS tools]] == Technical Details == This service is made using: * [http://www.openssh.org/ OpenSSH] f2dc16239684a4ae4af63549cec58b57d3755b4c 433 432 2014-03-12T11:59:13Z Duck 2 /* Locales */ wikitext text/x-wiki {{Template:Service | description = Remote [[wikipedia:Shell_(computing)|shell]] to a DuckCorp machine. | prerequisite = You need to ask an administrator for an account, but we need to know you well-enough to ensure you are trustable. This is '''not''' a VIP requirement, but such an access can be very dangerous and we don't know any other way to avoid a disaster, sorry. You also need to provide a RSA/DSA public key (see ''ssh-keygen''). | account = global-reg | ipv6 = true | security_notes = This service is secure. }} == Access == Via SSH with a RSA/DSA/ECDSA key on the following hosts: * thorfinn.duckcorp.org (prefered for lengthy sessions, like screens) * toushirou.duckcorp.org (mostly useful to manage Web/FTP data) Via SSH+[http://mosh.mit.edu/ Mosh], with the same hosts and conditions defined above. On Debian you can use the ''mosh'' package to get the client application and do ''mosh &lt;server&gt;''. On Android, the [http://dan.drown.org/android/mosh/ patched IrssiConnectbot from ddrown] is known to work as well. === Locked behind a firewall === If you are obliged to go through a firewall (at work for eg), you can try a few things to through and end-up on Toushirou (and can bounce on Thorfinn then). First, if you know there is a proxy, or direct access does not work, you may be able to find the firewall host and port in the browser configuration. If there is none, then the proxy may be transparent (hidden) and you can try a direct SSH access using ''portal.duckcorp.org'' on port ''443''. If it does not work, you can try using a tool to wrap SSH through the firewall. From a terminal the ''corkscrew'' (Debian has a package of the same name) tool car be used with the following SSH configuration (in ''~/.ssh/config''): Host portal.duckcorp.org ProxyCommand /usr/bin/corkscrew &lt;proxy-host&gt; &lt;proxy-port&gt; %h %p and connect with: ssh portal.duckcorp.org == Available Resources == The following resources are available and will remain until we advertise a scheduled removal. If you miss something you can send us a request. === Locales === {{warning}} warning for Mosh users: Mosh only supports UTF-8 locales * br_FR.UTF-8 * en_GB.UTF-8 * en_US.UTF-8 * fr_FR.UTF-8 * ja_JP.EUC-JP * ja_JP.UTF-8 === Shells === * dash * bash * zsh * ksh * tcsh === Programs === * aspell (with same support as system locales) * dict * emacs * irssi (with plugins and scripts) * latex (full TeXlive) * rsync * screen * sieve-connect * unison * vim * w3m * weechat (with plugins and scripts) Additional tools: * [[Services/VCS|VCS tools]] == Technical Details == This service is made using: * [http://www.openssh.org/ OpenSSH] cc20548dd6fc8c996abc551e51c49cca40ee648d 434 433 2014-03-12T12:01:37Z Duck 2 /* Technical Details */ wikitext text/x-wiki {{Template:Service | description = Remote [[wikipedia:Shell_(computing)|shell]] to a DuckCorp machine. | prerequisite = You need to ask an administrator for an account, but we need to know you well-enough to ensure you are trustable. This is '''not''' a VIP requirement, but such an access can be very dangerous and we don't know any other way to avoid a disaster, sorry. You also need to provide a RSA/DSA public key (see ''ssh-keygen''). | account = global-reg | ipv6 = true | security_notes = This service is secure. }} == Access == Via SSH with a RSA/DSA/ECDSA key on the following hosts: * thorfinn.duckcorp.org (prefered for lengthy sessions, like screens) * toushirou.duckcorp.org (mostly useful to manage Web/FTP data) Via SSH+[http://mosh.mit.edu/ Mosh], with the same hosts and conditions defined above. On Debian you can use the ''mosh'' package to get the client application and do ''mosh &lt;server&gt;''. On Android, the [http://dan.drown.org/android/mosh/ patched IrssiConnectbot from ddrown] is known to work as well. === Locked behind a firewall === If you are obliged to go through a firewall (at work for eg), you can try a few things to through and end-up on Toushirou (and can bounce on Thorfinn then). First, if you know there is a proxy, or direct access does not work, you may be able to find the firewall host and port in the browser configuration. If there is none, then the proxy may be transparent (hidden) and you can try a direct SSH access using ''portal.duckcorp.org'' on port ''443''. If it does not work, you can try using a tool to wrap SSH through the firewall. From a terminal the ''corkscrew'' (Debian has a package of the same name) tool car be used with the following SSH configuration (in ''~/.ssh/config''): Host portal.duckcorp.org ProxyCommand /usr/bin/corkscrew &lt;proxy-host&gt; &lt;proxy-port&gt; %h %p and connect with: ssh portal.duckcorp.org == Available Resources == The following resources are available and will remain until we advertise a scheduled removal. If you miss something you can send us a request. === Locales === {{warning}} warning for Mosh users: Mosh only supports UTF-8 locales * br_FR.UTF-8 * en_GB.UTF-8 * en_US.UTF-8 * fr_FR.UTF-8 * ja_JP.EUC-JP * ja_JP.UTF-8 === Shells === * dash * bash * zsh * ksh * tcsh === Programs === * aspell (with same support as system locales) * dict * emacs * irssi (with plugins and scripts) * latex (full TeXlive) * rsync * screen * sieve-connect * unison * vim * w3m * weechat (with plugins and scripts) Additional tools: * [[Services/VCS|VCS tools]] == Technical Details == This service is made using: * [http://www.openssh.org/ OpenSSH] * [http://mosh.mit.edu/ MOSH] ae0e180b396a3bf36db74411ce93fd9ab87bde43 435 434 2014-03-12T12:02:16Z Duck 2 /* Technical Details */ wikitext text/x-wiki {{Template:Service | description = Remote [[wikipedia:Shell_(computing)|shell]] to a DuckCorp machine. | prerequisite = You need to ask an administrator for an account, but we need to know you well-enough to ensure you are trustable. This is '''not''' a VIP requirement, but such an access can be very dangerous and we don't know any other way to avoid a disaster, sorry. You also need to provide a RSA/DSA public key (see ''ssh-keygen''). | account = global-reg | ipv6 = true | security_notes = This service is secure. }} == Access == Via SSH with a RSA/DSA/ECDSA key on the following hosts: * thorfinn.duckcorp.org (prefered for lengthy sessions, like screens) * toushirou.duckcorp.org (mostly useful to manage Web/FTP data) Via SSH+[http://mosh.mit.edu/ Mosh], with the same hosts and conditions defined above. On Debian you can use the ''mosh'' package to get the client application and do ''mosh &lt;server&gt;''. On Android, the [http://dan.drown.org/android/mosh/ patched IrssiConnectbot from ddrown] is known to work as well. === Locked behind a firewall === If you are obliged to go through a firewall (at work for eg), you can try a few things to through and end-up on Toushirou (and can bounce on Thorfinn then). First, if you know there is a proxy, or direct access does not work, you may be able to find the firewall host and port in the browser configuration. If there is none, then the proxy may be transparent (hidden) and you can try a direct SSH access using ''portal.duckcorp.org'' on port ''443''. If it does not work, you can try using a tool to wrap SSH through the firewall. From a terminal the ''corkscrew'' (Debian has a package of the same name) tool car be used with the following SSH configuration (in ''~/.ssh/config''): Host portal.duckcorp.org ProxyCommand /usr/bin/corkscrew &lt;proxy-host&gt; &lt;proxy-port&gt; %h %p and connect with: ssh portal.duckcorp.org == Available Resources == The following resources are available and will remain until we advertise a scheduled removal. If you miss something you can send us a request. === Locales === {{warning}} warning for Mosh users: Mosh only supports UTF-8 locales * br_FR.UTF-8 * en_GB.UTF-8 * en_US.UTF-8 * fr_FR.UTF-8 * ja_JP.EUC-JP * ja_JP.UTF-8 === Shells === * dash * bash * zsh * ksh * tcsh === Programs === * aspell (with same support as system locales) * dict * emacs * irssi (with plugins and scripts) * latex (full TeXlive) * rsync * screen * sieve-connect * unison * vim * w3m * weechat (with plugins and scripts) Additional tools: * [[Services/VCS|VCS tools]] == Technical Details == This service is made using: * [http://www.openssh.org/ OpenSSH] * [http://mosh.mit.edu/ Mosh] e03dbef9460cd06c97e783961c9a15ffbe424d25 436 435 2014-03-12T12:11:24Z Duck 2 /* Programs */ wikitext text/x-wiki {{Template:Service | description = Remote [[wikipedia:Shell_(computing)|shell]] to a DuckCorp machine. | prerequisite = You need to ask an administrator for an account, but we need to know you well-enough to ensure you are trustable. This is '''not''' a VIP requirement, but such an access can be very dangerous and we don't know any other way to avoid a disaster, sorry. You also need to provide a RSA/DSA public key (see ''ssh-keygen''). | account = global-reg | ipv6 = true | security_notes = This service is secure. }} == Access == Via SSH with a RSA/DSA/ECDSA key on the following hosts: * thorfinn.duckcorp.org (prefered for lengthy sessions, like screens) * toushirou.duckcorp.org (mostly useful to manage Web/FTP data) Via SSH+[http://mosh.mit.edu/ Mosh], with the same hosts and conditions defined above. On Debian you can use the ''mosh'' package to get the client application and do ''mosh &lt;server&gt;''. On Android, the [http://dan.drown.org/android/mosh/ patched IrssiConnectbot from ddrown] is known to work as well. === Locked behind a firewall === If you are obliged to go through a firewall (at work for eg), you can try a few things to through and end-up on Toushirou (and can bounce on Thorfinn then). First, if you know there is a proxy, or direct access does not work, you may be able to find the firewall host and port in the browser configuration. If there is none, then the proxy may be transparent (hidden) and you can try a direct SSH access using ''portal.duckcorp.org'' on port ''443''. If it does not work, you can try using a tool to wrap SSH through the firewall. From a terminal the ''corkscrew'' (Debian has a package of the same name) tool car be used with the following SSH configuration (in ''~/.ssh/config''): Host portal.duckcorp.org ProxyCommand /usr/bin/corkscrew &lt;proxy-host&gt; &lt;proxy-port&gt; %h %p and connect with: ssh portal.duckcorp.org == Available Resources == The following resources are available and will remain until we advertise a scheduled removal. If you miss something you can send us a request. === Locales === {{warning}} warning for Mosh users: Mosh only supports UTF-8 locales * br_FR.UTF-8 * en_GB.UTF-8 * en_US.UTF-8 * fr_FR.UTF-8 * ja_JP.EUC-JP * ja_JP.UTF-8 === Shells === * dash * bash * zsh * ksh * tcsh === Programs === * aspell (with same support as system locales) * dict * emacs * irssi (with plugins and scripts) * latex (full TeXlive) * p7zip * rsync * screen * sieve-connect * unar * unison * vim * w3m * weechat (with plugins and scripts) Additional tools: * [[Services/VCS|VCS tools]] == Technical Details == This service is made using: * [http://www.openssh.org/ OpenSSH] * [http://mosh.mit.edu/ Mosh] a0f365cf65063e87bff9e773adaa17bb3a2a667d 437 436 2014-03-12T12:25:39Z Duck 2 /* Programs */ wikitext text/x-wiki {{Template:Service | description = Remote [[wikipedia:Shell_(computing)|shell]] to a DuckCorp machine. | prerequisite = You need to ask an administrator for an account, but we need to know you well-enough to ensure you are trustable. This is '''not''' a VIP requirement, but such an access can be very dangerous and we don't know any other way to avoid a disaster, sorry. You also need to provide a RSA/DSA public key (see ''ssh-keygen''). | account = global-reg | ipv6 = true | security_notes = This service is secure. }} == Access == Via SSH with a RSA/DSA/ECDSA key on the following hosts: * thorfinn.duckcorp.org (prefered for lengthy sessions, like screens) * toushirou.duckcorp.org (mostly useful to manage Web/FTP data) Via SSH+[http://mosh.mit.edu/ Mosh], with the same hosts and conditions defined above. On Debian you can use the ''mosh'' package to get the client application and do ''mosh &lt;server&gt;''. On Android, the [http://dan.drown.org/android/mosh/ patched IrssiConnectbot from ddrown] is known to work as well. === Locked behind a firewall === If you are obliged to go through a firewall (at work for eg), you can try a few things to through and end-up on Toushirou (and can bounce on Thorfinn then). First, if you know there is a proxy, or direct access does not work, you may be able to find the firewall host and port in the browser configuration. If there is none, then the proxy may be transparent (hidden) and you can try a direct SSH access using ''portal.duckcorp.org'' on port ''443''. If it does not work, you can try using a tool to wrap SSH through the firewall. From a terminal the ''corkscrew'' (Debian has a package of the same name) tool car be used with the following SSH configuration (in ''~/.ssh/config''): Host portal.duckcorp.org ProxyCommand /usr/bin/corkscrew &lt;proxy-host&gt; &lt;proxy-port&gt; %h %p and connect with: ssh portal.duckcorp.org == Available Resources == The following resources are available and will remain until we advertise a scheduled removal. If you miss something you can send us a request. === Locales === {{warning}} warning for Mosh users: Mosh only supports UTF-8 locales * br_FR.UTF-8 * en_GB.UTF-8 * en_US.UTF-8 * fr_FR.UTF-8 * ja_JP.EUC-JP * ja_JP.UTF-8 === Shells === * dash * bash * zsh * ksh * tcsh === Programs === * aspell (with same support as system locales) * dict * emacs * graphviz * irssi (with plugins and scripts) * latex (full TeXlive) * p7zip * rsync * screen * sieve-connect * unar * unison * vim * w3m * weechat (with plugins and scripts) Additional tools: * [[Services/VCS|VCS tools]] == Technical Details == This service is made using: * [http://www.openssh.org/ OpenSSH] * [http://mosh.mit.edu/ Mosh] 29b9d4a2188a75b28e8b64bdcd3fad557038e2c2 438 437 2014-03-12T12:35:34Z Duck 2 /* Programs */ wikitext text/x-wiki {{Template:Service | description = Remote [[wikipedia:Shell_(computing)|shell]] to a DuckCorp machine. | prerequisite = You need to ask an administrator for an account, but we need to know you well-enough to ensure you are trustable. This is '''not''' a VIP requirement, but such an access can be very dangerous and we don't know any other way to avoid a disaster, sorry. You also need to provide a RSA/DSA public key (see ''ssh-keygen''). | account = global-reg | ipv6 = true | security_notes = This service is secure. }} == Access == Via SSH with a RSA/DSA/ECDSA key on the following hosts: * thorfinn.duckcorp.org (prefered for lengthy sessions, like screens) * toushirou.duckcorp.org (mostly useful to manage Web/FTP data) Via SSH+[http://mosh.mit.edu/ Mosh], with the same hosts and conditions defined above. On Debian you can use the ''mosh'' package to get the client application and do ''mosh &lt;server&gt;''. On Android, the [http://dan.drown.org/android/mosh/ patched IrssiConnectbot from ddrown] is known to work as well. === Locked behind a firewall === If you are obliged to go through a firewall (at work for eg), you can try a few things to through and end-up on Toushirou (and can bounce on Thorfinn then). First, if you know there is a proxy, or direct access does not work, you may be able to find the firewall host and port in the browser configuration. If there is none, then the proxy may be transparent (hidden) and you can try a direct SSH access using ''portal.duckcorp.org'' on port ''443''. If it does not work, you can try using a tool to wrap SSH through the firewall. From a terminal the ''corkscrew'' (Debian has a package of the same name) tool car be used with the following SSH configuration (in ''~/.ssh/config''): Host portal.duckcorp.org ProxyCommand /usr/bin/corkscrew &lt;proxy-host&gt; &lt;proxy-port&gt; %h %p and connect with: ssh portal.duckcorp.org == Available Resources == The following resources are available and will remain until we advertise a scheduled removal. If you miss something you can send us a request. === Locales === {{warning}} warning for Mosh users: Mosh only supports UTF-8 locales * br_FR.UTF-8 * en_GB.UTF-8 * en_US.UTF-8 * fr_FR.UTF-8 * ja_JP.EUC-JP * ja_JP.UTF-8 === Shells === * dash * bash * zsh * ksh * tcsh === Programs === * aspell (with same support as system locales) * dict * emacs * graphviz * imagemagick * irssi (with plugins and scripts) * latex (full TeXlive) * p7zip * rsync * screen * sieve-connect * unar * unison * vim * w3m * weechat (with plugins and scripts) Additional tools: * [[Services/VCS|VCS tools]] == Technical Details == This service is made using: * [http://www.openssh.org/ OpenSSH] * [http://mosh.mit.edu/ Mosh] 5d2836c775ef8be9b25bcb8521fb100ed80a6afd 0 68 416 394 2014-02-13T00:30:59Z Duck 2 wikitext text/x-wiki {{Template:Service | description = The OwnCloud service is a webservice used to access, sync, and share your personal data. Currently you can: * store your files (and in-place view/edit of certain extensions directly from the web interface) * manage your contacts * manage your calendars * <del>manage your tasks</del> (deactivated because broken at the moment) * manage your web bookmarks (with Firefox Sync) | prerequisite = | account = global | ipv6 = true | security_notes = This service is secure but beware when sharing your data to other people. }} {{warning}} Remember not to use this service to store illegal or non-free data. == Access == === Web Interface === Use this URL in your browser: https://stuff.milkypond.org/ Then you can setup your contacts, calendars, and store files. === WebDAV Interface === You can use the [[wikipedia:WebDAV|WebDAV]] interface to sync your data from a desktop application or you mobile device. Applications can use the main address of the web interface (see above) with your credentials and should be able to discover you data, but sometimes they have limitations and you need to specify a full ugly link ; in this case you can find the link in the interface, either on the resource to access or in your personal settings page. ==== Files ==== * Desktop: ** remote drive (synchrounous): use XFCE/Gigolo or GNOME/Nautilus ** synchronize (asynchronous): use the [http://owncloud.org/support/sync-clients/ csync] utility * Mobile Devices: ** Android: use the [http://owncloud.org/support/android/ Owncloud] app (available on [http://f-droid.org/ F-Droid]) to synchronize files ==== Contacts ==== * Desktop: synchronize with GNOME/Evolution * Mobile Devices: ** Android: the [http://owncloud.org/support/android/ Owncloud] app should be able to do it in the future, but you may use the [http://dmfs.org/wiki/index.php?title=CardDAV-Sync CardDAV-Sync] app which is [http://dmfs.org/wiki/index.php?title=Open_source_status to be opensourced] * Webmail: ** Webdesk (Horde): does not work ** old webmail (Squirrelmail): does not work ** newest webmail (RoundCube): works nicely with the newest webmail (RoundCube) (see in Settings->Preferences->CardDAV) ==== Calendars: ==== * Desktop: synchronize with GNOME/Evolution * Mobile Devices: ** Android: the [http://owncloud.org/support/android/ Owncloud] app should be able to do it in the future, but you may use the [http://dmfs.org/wiki/index.php?title=CalDAV-Sync CalDAV-Sync] app which is [http://dmfs.org/wiki/index.php?title=Open_source_status to be opensourced], or try [http://acal.me/wiki/Main_Page aCal] (available on [http://f-droid.org/ F-Droid]) which does not use the internal calendar and proved quite slow * Webmail: ** Webdesk (Horde): does not work ** old webmail (Squirrelmail): does not work ** newest webmail (RoundCube): should work but it does not seem to parse events properly even if there's no errors (see in Settings->Preferences->Calendar and the Provider field) == Documentation == * ''OwnCloud'' section in the [http://owncloud.org/support/ Help Page] == Technical Details == This service is made using: * [http://owncloud.org/ OwnCloud] 7e7e3e9f054c304c0588e01324c92d0019836cb6 417 416 2014-02-13T00:51:20Z Duck 2 /* Files */ wikitext text/x-wiki {{Template:Service | description = The OwnCloud service is a webservice used to access, sync, and share your personal data. Currently you can: * store your files (and in-place view/edit of certain extensions directly from the web interface) * manage your contacts * manage your calendars * <del>manage your tasks</del> (deactivated because broken at the moment) * manage your web bookmarks (with Firefox Sync) | prerequisite = | account = global | ipv6 = true | security_notes = This service is secure but beware when sharing your data to other people. }} {{warning}} Remember not to use this service to store illegal or non-free data. == Access == === Web Interface === Use this URL in your browser: https://stuff.milkypond.org/ Then you can setup your contacts, calendars, and store files. === WebDAV Interface === You can use the [[wikipedia:WebDAV|WebDAV]] interface to sync your data from a desktop application or you mobile device. Applications can use the main address of the web interface (see above) with your credentials and should be able to discover you data, but sometimes they have limitations and you need to specify a full ugly link ; in this case you can find the link in the interface, either on the resource to access or in your personal settings page. ==== Files ==== * Desktop: ** remote drive (synchrounous): use XFCE/Gigolo or GNOME/Nautilus ** synchronize (asynchronous): use the [http://doc.owncloud.org/desktop/ sync] utility (''owncloud-client'' package on Debian) * Mobile Devices: ** Android: use the [http://owncloud.org/support/android/ Owncloud] app (available on [http://f-droid.org/ F-Droid]) to synchronize files ==== Contacts ==== * Desktop: synchronize with GNOME/Evolution * Mobile Devices: ** Android: the [http://owncloud.org/support/android/ Owncloud] app should be able to do it in the future, but you may use the [http://dmfs.org/wiki/index.php?title=CardDAV-Sync CardDAV-Sync] app which is [http://dmfs.org/wiki/index.php?title=Open_source_status to be opensourced] * Webmail: ** Webdesk (Horde): does not work ** old webmail (Squirrelmail): does not work ** newest webmail (RoundCube): works nicely with the newest webmail (RoundCube) (see in Settings->Preferences->CardDAV) ==== Calendars: ==== * Desktop: synchronize with GNOME/Evolution * Mobile Devices: ** Android: the [http://owncloud.org/support/android/ Owncloud] app should be able to do it in the future, but you may use the [http://dmfs.org/wiki/index.php?title=CalDAV-Sync CalDAV-Sync] app which is [http://dmfs.org/wiki/index.php?title=Open_source_status to be opensourced], or try [http://acal.me/wiki/Main_Page aCal] (available on [http://f-droid.org/ F-Droid]) which does not use the internal calendar and proved quite slow * Webmail: ** Webdesk (Horde): does not work ** old webmail (Squirrelmail): does not work ** newest webmail (RoundCube): should work but it does not seem to parse events properly even if there's no errors (see in Settings->Preferences->Calendar and the Provider field) == Documentation == * ''OwnCloud'' section in the [http://owncloud.org/support/ Help Page] == Technical Details == This service is made using: * [http://owncloud.org/ OwnCloud] cbb0073957b8161fe03a6eee61235ea912a0e199 446 417 2014-07-29T14:18:28Z Duck 2 /* WebDAV Interface */ wikitext text/x-wiki {{Template:Service | description = The OwnCloud service is a webservice used to access, sync, and share your personal data. Currently you can: * store your files (and in-place view/edit of certain extensions directly from the web interface) * manage your contacts * manage your calendars * <del>manage your tasks</del> (deactivated because broken at the moment) * manage your web bookmarks (with Firefox Sync) | prerequisite = | account = global | ipv6 = true | security_notes = This service is secure but beware when sharing your data to other people. }} {{warning}} Remember not to use this service to store illegal or non-free data. == Access == === Web Interface === Use this URL in your browser: https://stuff.milkypond.org/ Then you can setup your contacts, calendars, and store files. === WebDAV Interface === You can use the [[wikipedia:WebDAV|WebDAV]] interface to sync your data from a desktop application or you mobile device. Applications can use the main address of the web interface (see above) with your credentials and should be able to discover you data, but sometimes they have limitations and you need to specify a full ugly link ; in this case you can find the link in the interface, either on the resource to access or in your personal settings page. ==== Files ==== * Desktop: ** remote drive (synchrounous): use XFCE/Gigolo or GNOME/Nautilus ** synchronize (asynchronous): use the [http://doc.owncloud.org/desktop/ sync] utility (''owncloud-client'' package on Debian) * Mobile Devices: ** Android: use the [http://owncloud.org/support/android/ Owncloud] app (available on [http://f-droid.org/ F-Droid]) to synchronize files ==== Contacts ==== * Desktop: synchronize with GNOME/Evolution * Mobile Devices: ** Android: the [http://owncloud.org/support/android/ Owncloud] app should be able to do it in the future, but you may use the [http://dmfs.org/wiki/index.php?title=CardDAV-Sync CardDAV-Sync] app which is [http://dmfs.org/wiki/index.php?title=Open_source_status to be opensourced] * Webmail: ** Webdesk (Horde): does not work ** old webmail (Squirrelmail): does not work ** newest webmail (RoundCube): works nicely with the newest webmail (RoundCube) (see in Settings->Preferences->CardDAV) ==== Calendars ==== * Desktop: synchronize with GNOME/Evolution * Mobile Devices: ** Android: the [http://owncloud.org/support/android/ Owncloud] app should be able to do it in the future, but you may use the [http://dmfs.org/wiki/index.php?title=CalDAV-Sync CalDAV-Sync] app which is [http://dmfs.org/wiki/index.php?title=Open_source_status to be opensourced], or try [http://acal.me/wiki/Main_Page aCal] (available on [http://f-droid.org/ F-Droid]) which does not use the internal calendar and proved quite slow * Webmail: ** Webdesk (Horde): does not work ** old webmail (Squirrelmail): does not work ** newest webmail (RoundCube): should work but it does not seem to parse events properly even if there's no errors (see in Settings->Preferences->Calendar and the Provider field) ==== Tasks ==== It may be provided by your calendar application. * Desktop: ??? * Mobile Devices: ** Android: the [https://github.com/dmfs/tasks Task] app works well (available on [http://f-droid.org/ F-Droid]) ** Webdesk (Horde): ??? ** old webmail (Squirrelmail): ??? ** newest webmail (RoundCube): ??? == Documentation == * ''OwnCloud'' section in the [http://owncloud.org/support/ Help Page] == Technical Details == This service is made using: * [http://owncloud.org/ OwnCloud] 14ac50abbcde46b01a4103d9bf0a894fe8433752 0 71 419 2014-02-13T01:18:02Z Duck 2 Created page with "{{Template:Service | description = Minecraft-like game, which is an old-looking building game | prerequisite = | account = local | ipv6 = false | security_notes = This service..." wikitext text/x-wiki {{Template:Service | description = Minecraft-like game, which is an old-looking building game | prerequisite = | account = local | ipv6 = false | security_notes = This service does not contain sensitive data. }} == Access == Install the Minetest client, like this on Debian: apt-get install minetest Launch the game and connect to a server using: * hostname: minetest.duckcorp.org * port: UDP 30000 (default) * password: sevenofnine and the username you like. In game you can then change your personal password in the menu (press ESC). == Documentation == * [http://wiki.minetest.net/Main_Page Community Wiki] == Technical Details == This service is made using: * [http://www.minetest.net/ Minetest] 984ef340fa52cf3a801548742e57eeeffdb6721e 0 30 421 187 2014-03-03T14:04:56Z Duck 2 /* Admins */ wikitext text/x-wiki == The DuckCorp Story == DuckCorp was born in 2000, from Duck's will to construct something more personal out of the CoinNetwork student house's LAN. At that time, it was merely a simple website, advertising a few personal projects. Later, several machines, gathered with various parts from people willing to dispose of them, used the 'duckcorp.org' domain name and provided services for CoinNetwork; this was the begining of the DC's sponsoring mission. Duck then met Rtp, and they began sharing about system administration topics. As they were willing to administrate CoinNetwork better, they began working on the infrastructure and tools together. Rtp created RtpNet, and received the magical SSH key to be a full DC administrator (so did Duck for Rtpnet indeed). They developed a software prototype aimed at managing the most important services of a distributed web of servers (LMS, LDAP Management System), which helped reducing the daily burden of CoinNetwork's administration a lot. After a while working hand in hand, they both found a job and moved to a new home, still helping each other when possible. Currently, RtpNet and DuckCorp have different goals, and follow their own path. On the way, DC found friendly sponsors (in order of appearance): * Nerim (first Orfeo's housing, IPv6 block, indirect sponsor via Hivane) * Hivane (global connectivity, secondary NS and MX) * Sivit (special accomodations for Toushirou's housing and connectivity) (now Nerim again, as it was acquired recently) * Alionis (Orfeo's housing) Thanks a lot pals :-). == The MilkyPond Project == MP is an historical share of an IRC network between DC and RN when they both stopped working on the CoinNetwork project. They were willing to cooperate but with the important changes that occurred in their lives, only IRC was kept as a communication link. With time going, DC began recreating services, with the main server Orfeo being kindly sponsored by Nerim, which was used by RN and later by other associations or individuals. Nothing much is done in the name of MP until 2007, besides adding a Jabber server. In early 2007, RN hired a server, Lechat (Dédibox), and was willing to participate more in the share. At the end of the year, T1R joined to help improving the IRC Network. In September 2007, RN was not able to provide services anymore, as it was too much of a burden. Nevertheless, it is still sponsoring the ''milkypond.org'' domain since then. == Key Dates == * 2000-05-22: DuckCorp is created * 2003-04-25: IANA PEN 16829 * 2003-07-09: RtpNet is created * ~2003-10-20: RSA key exchanged between DC and RN (date is from the exif info, but Photoshop is in the way) * 2004-06-12: MilkyPond is created (after DC and RN stopped working on the CoinNetwork project) * 2005-04/05: Orfeo RAM upgraded (512Mo->1.5Go) (blocked to ~800Mo [[Media:Orfeo.duckcorp.org-memory-day.png|until highmem in kernel]]) * 2005-05: IPv6 Ready (using a tunnel) * 2005-11-17: the users' mailing-list started * 2005-11: major mail system improvements (SMTP auth, improved antispam, webdesk) * 2005-12-08: Orfeo moved from the Nerim's Ivry datacenter to the Nerim suite in the LDCOM Courbevoie datacenter * 2006-01 to 2006-06: Orfeo problems due to an [http://xfs.org/index.php/XFS_FAQ#Q:_What_is_the_issue_with_directory_corruption_in_Linux_2.6.17.3F XFS bug] * 2007-04: IPv6 Ready (native IPv6) * 2007-07: Tōshirō bought and being prepared * 2007-08-08: Nerim's boss shutdown Orfeo violently; quickly repaired and setup behind a mere ADSL (helped by Nerim friends), but BLACKOUT for most services * 2007-08-13: Tōshirō installed in the Sivit suite of the Redbus datacenter, services progressively back online * 2007-09: LDAP infrastructure (again) * 2007-12: Orfeo-NG bough and installed in Alionis suite in EQX (Equinix) datacenter * 2007-12: T1R enters MilkyPond (for the IRC network) * 2008-07: VCS rework, Portal (Restricted Access Helper), Projects Manager (Redmine) * 2009-03: Banya bot (mail gateway for DNS modification, part of the CyborgHood project) * 2009-09: Orfeo moved to [http://www.alionis.net/infra/VBO.html Alionis VBO datacenter] * 2010-03: Thorfinn acquired (Nerim VDS) * 2010-04-24: stratum 2 NTP server [http://support.ntp.org/bin/view/Servers/NtpDuckCorpOrg publicly advertised] and in the [http://www.pool.ntp.org/user/DuckCorp pool] * 2010-05-22: 10th Anniversary !!! * 2010-05-29: 10th Anniversary party with users/sponsors/friends * 2010-10: DNS TSIG and DNSSEC == Admins == * Arnau [~2004-12 to now] (fallback admin since 2010-04-27, more active since early 2014) * Duck [begining to now] (leader) * Finger [2006-07-05 to 2008-02-04] (assistant) * Mmenal [~2004-12 to ~2006-07] * Rtp [2003-10 to 2007-07-15] == Evolution == No real traces were kept, so old numbers are mere rough guess. * 2000 -> 2004 ** more than 60 users served in the [[Media:Coinnetwork resal 2001-2002.png|CoinNetwork LAN]], nearly no external services besides a basic website and IRC ** services targeted for the CoinNetwork LAN * 2004 -> 2007 ** a few users (probably around 20) and 2 entities (RtpNet and [http://www.hurdfr.org/ HurdFr]) hosted ** more Internet-oriented services (complete mail software suite, MLs, Web hosting, DBs, RCS, ...) * 2007 -> 2010 ** more users (nearly 70 users in 2010, a few not very active) and 2 more entity hosted ([http://thebrain.lautre.net/ TheBrain] and [http://www.andesi.org/ Andesi]) ** more services (Jabber, user-friendly antispam, LDAP, IPv6, ...) == Photos == Look at the [http://photos.duckcorp.org/v/duckcorp/ gallery]. ef430929a74dd12ec058471a8be1dc89ff9c9a1d 422 421 2014-03-03T14:20:06Z Duck 2 /* Key Dates */ wikitext text/x-wiki == The DuckCorp Story == DuckCorp was born in 2000, from Duck's will to construct something more personal out of the CoinNetwork student house's LAN. At that time, it was merely a simple website, advertising a few personal projects. Later, several machines, gathered with various parts from people willing to dispose of them, used the 'duckcorp.org' domain name and provided services for CoinNetwork; this was the begining of the DC's sponsoring mission. Duck then met Rtp, and they began sharing about system administration topics. As they were willing to administrate CoinNetwork better, they began working on the infrastructure and tools together. Rtp created RtpNet, and received the magical SSH key to be a full DC administrator (so did Duck for Rtpnet indeed). They developed a software prototype aimed at managing the most important services of a distributed web of servers (LMS, LDAP Management System), which helped reducing the daily burden of CoinNetwork's administration a lot. After a while working hand in hand, they both found a job and moved to a new home, still helping each other when possible. Currently, RtpNet and DuckCorp have different goals, and follow their own path. On the way, DC found friendly sponsors (in order of appearance): * Nerim (first Orfeo's housing, IPv6 block, indirect sponsor via Hivane) * Hivane (global connectivity, secondary NS and MX) * Sivit (special accomodations for Toushirou's housing and connectivity) (now Nerim again, as it was acquired recently) * Alionis (Orfeo's housing) Thanks a lot pals :-). == The MilkyPond Project == MP is an historical share of an IRC network between DC and RN when they both stopped working on the CoinNetwork project. They were willing to cooperate but with the important changes that occurred in their lives, only IRC was kept as a communication link. With time going, DC began recreating services, with the main server Orfeo being kindly sponsored by Nerim, which was used by RN and later by other associations or individuals. Nothing much is done in the name of MP until 2007, besides adding a Jabber server. In early 2007, RN hired a server, Lechat (Dédibox), and was willing to participate more in the share. At the end of the year, T1R joined to help improving the IRC Network. In September 2007, RN was not able to provide services anymore, as it was too much of a burden. Nevertheless, it is still sponsoring the ''milkypond.org'' domain since then. == Key Dates == * 2000-05-22: DuckCorp is created * 2003-04-25: IANA PEN 16829 * 2003-07-09: RtpNet is created * ~2003-10-20: RSA key exchanged between DC and RN (date is from the exif info, but Photoshop is in the way) * 2004-06-12: MilkyPond is created (after DC and RN stopped working on the CoinNetwork project) * 2005-04/05: Orfeo RAM upgraded (512Mo->1.5Go) (blocked to ~800Mo [[Media:Orfeo.duckcorp.org-memory-day.png|until highmem in kernel]]) * 2005-05: IPv6 Ready (using a tunnel) * 2005-11-17: the users' mailing-list started * 2005-11: major mail system improvements (SMTP auth, improved antispam, webdesk) * 2005-12-08: Orfeo moved from the Nerim's Ivry datacenter to the Nerim suite in the LDCOM Courbevoie datacenter * 2006-01 to 2006-06: Orfeo problems due to an [http://xfs.org/index.php/XFS_FAQ#Q:_What_is_the_issue_with_directory_corruption_in_Linux_2.6.17.3F XFS bug] * 2007-04: IPv6 Ready (native IPv6) * 2007-07: Tōshirō bought and being prepared * 2007-08-08: Nerim's boss shutdown Orfeo violently; quickly repaired and setup behind a mere ADSL (helped by Nerim friends), but BLACKOUT for most services * 2007-08-13: Tōshirō installed in the Sivit suite of the Redbus datacenter, services progressively back online * 2007-09: LDAP infrastructure (again) * 2007-12: Orfeo-NG bough and installed in Alionis suite in EQX (Equinix) datacenter * 2007-12: T1R enters MilkyPond (for the IRC network) * 2008-07: VCS rework, Portal (Restricted Access Helper), Projects Manager (Redmine) * 2009-03: Banya bot (mail gateway for DNS modification, part of the CyborgHood project) * 2009-09: Orfeo moved to [http://www.alionis.net/infra/VBO.html Alionis VBO datacenter] * 2010-03: Thorfinn acquired (Nerim VDS) * 2010-04-24: stratum 2 NTP server [http://support.ntp.org/bin/view/Servers/NtpDuckCorpOrg publicly advertised] and in the [http://www.pool.ntp.org/user/DuckCorp pool] * 2010-05-22: 10th Anniversary !!! * 2010-05-29: 10th Anniversary party with users/sponsors/friends * 2010-10: DNS TSIG and DNSSEC * 2010-11: Toushirou at Gbps (with a reboot to work around a firmware bug) * 2010-12: power outage at VBO, kernel bug preventing Orfeo to restart (IPMI-related) * 2010-12: Jinta (VM provided by mm), replacing T1R secondary IRC server * 2011-01: problems with backup and capacity * 2011-05: improved IMAP and SIEVE support, shared and public folders * 2011-06: launch of the '''Ducklings Volunteer Activities''' == Admins == * Arnau [~2004-12 to now] (fallback admin since 2010-04-27, more active since early 2014) * Duck [begining to now] (leader) * Finger [2006-07-05 to 2008-02-04] (assistant) * Mmenal [~2004-12 to ~2006-07] * Rtp [2003-10 to 2007-07-15] == Evolution == No real traces were kept, so old numbers are mere rough guess. * 2000 -> 2004 ** more than 60 users served in the [[Media:Coinnetwork resal 2001-2002.png|CoinNetwork LAN]], nearly no external services besides a basic website and IRC ** services targeted for the CoinNetwork LAN * 2004 -> 2007 ** a few users (probably around 20) and 2 entities (RtpNet and [http://www.hurdfr.org/ HurdFr]) hosted ** more Internet-oriented services (complete mail software suite, MLs, Web hosting, DBs, RCS, ...) * 2007 -> 2010 ** more users (nearly 70 users in 2010, a few not very active) and 2 more entity hosted ([http://thebrain.lautre.net/ TheBrain] and [http://www.andesi.org/ Andesi]) ** more services (Jabber, user-friendly antispam, LDAP, IPv6, ...) == Photos == Look at the [http://photos.duckcorp.org/v/duckcorp/ gallery]. bebb21b36d6637b17980a57b9a0cf15b602570a6 423 422 2014-03-03T14:31:39Z Duck 2 /* Key Dates */ wikitext text/x-wiki == The DuckCorp Story == DuckCorp was born in 2000, from Duck's will to construct something more personal out of the CoinNetwork student house's LAN. At that time, it was merely a simple website, advertising a few personal projects. Later, several machines, gathered with various parts from people willing to dispose of them, used the 'duckcorp.org' domain name and provided services for CoinNetwork; this was the begining of the DC's sponsoring mission. Duck then met Rtp, and they began sharing about system administration topics. As they were willing to administrate CoinNetwork better, they began working on the infrastructure and tools together. Rtp created RtpNet, and received the magical SSH key to be a full DC administrator (so did Duck for Rtpnet indeed). They developed a software prototype aimed at managing the most important services of a distributed web of servers (LMS, LDAP Management System), which helped reducing the daily burden of CoinNetwork's administration a lot. After a while working hand in hand, they both found a job and moved to a new home, still helping each other when possible. Currently, RtpNet and DuckCorp have different goals, and follow their own path. On the way, DC found friendly sponsors (in order of appearance): * Nerim (first Orfeo's housing, IPv6 block, indirect sponsor via Hivane) * Hivane (global connectivity, secondary NS and MX) * Sivit (special accomodations for Toushirou's housing and connectivity) (now Nerim again, as it was acquired recently) * Alionis (Orfeo's housing) Thanks a lot pals :-). == The MilkyPond Project == MP is an historical share of an IRC network between DC and RN when they both stopped working on the CoinNetwork project. They were willing to cooperate but with the important changes that occurred in their lives, only IRC was kept as a communication link. With time going, DC began recreating services, with the main server Orfeo being kindly sponsored by Nerim, which was used by RN and later by other associations or individuals. Nothing much is done in the name of MP until 2007, besides adding a Jabber server. In early 2007, RN hired a server, Lechat (Dédibox), and was willing to participate more in the share. At the end of the year, T1R joined to help improving the IRC Network. In September 2007, RN was not able to provide services anymore, as it was too much of a burden. Nevertheless, it is still sponsoring the ''milkypond.org'' domain since then. == Key Dates == * 2000-05-22: DuckCorp is created * 2003-04-25: IANA PEN 16829 * 2003-07-09: RtpNet is created * ~2003-10-20: RSA key exchanged between DC and RN (date is from the exif info, but Photoshop is in the way) * 2004-06-12: MilkyPond is created (after DC and RN stopped working on the CoinNetwork project) * 2005-04/05: Orfeo RAM upgraded (512Mo->1.5Go) (blocked to ~800Mo [[Media:Orfeo.duckcorp.org-memory-day.png|until highmem in kernel]]) * 2005-05: IPv6 Ready (using a tunnel) * 2005-11-17: the users' mailing-list started * 2005-11: major mail system improvements (SMTP auth, improved antispam, webdesk) * 2005-12-08: Orfeo moved from the Nerim's Ivry datacenter to the Nerim suite in the LDCOM Courbevoie datacenter * 2006-01 to 2006-06: Orfeo problems due to an [http://xfs.org/index.php/XFS_FAQ#Q:_What_is_the_issue_with_directory_corruption_in_Linux_2.6.17.3F XFS bug] * 2007-04: IPv6 Ready (native IPv6) * 2007-07: Tōshirō bought and being prepared * 2007-08-08: Nerim's boss shutdown Orfeo violently; quickly repaired and setup behind a mere ADSL (helped by Nerim friends), but BLACKOUT for most services * 2007-08-13: Tōshirō installed in the Sivit suite of the Redbus datacenter, services progressively back online * 2007-09: LDAP infrastructure (again) * 2007-12: Orfeo-NG bough and installed in Alionis suite in EQX (Equinix) datacenter * 2007-12: T1R enters MilkyPond (for the IRC network) * 2008-07: VCS rework, Portal (Restricted Access Helper), Projects Manager (Redmine) * 2009-03: Banya bot (mail gateway for DNS modification, part of the CyborgHood project) * 2009-09: Orfeo moved to [http://www.alionis.net/infra/VBO.html Alionis VBO datacenter] * 2010-03: Thorfinn acquired (Nerim VDS) * 2010-04-24: stratum 2 NTP server [http://support.ntp.org/bin/view/Servers/NtpDuckCorpOrg publicly advertised] and in the [http://www.pool.ntp.org/user/DuckCorp pool] * 2010-05-22: 10th Anniversary !!! * 2010-05-29: 10th Anniversary party with users/sponsors/friends * 2010-10: DNS TSIG and DNSSEC * 2010-11: Toushirou at Gbps (with a reboot to work around a firmware bug) * 2010-12: power outage at VBO, kernel bug preventing Orfeo to restart (IPMI-related) * 2010-12: Jinta (VM provided by mm), replacing T1R secondary IRC server * 2011-01: problems with backup and capacity * 2011-05: improved IMAP and SIEVE support, shared and public folders * 2011-06: launch of the '''Ducklings Volunteer Activities''' * 2011-08: new web service: news feeds (tt-rss), IRC on web replacement, XMPP on web, file sharing (Jyraphe), new web stats (Piwik) * 2011-10: Jinta is dow for good * 2012-01: Korutopi is born (backups) * 2012-02: handly mail retraining through IMAP * 2012-08: ** short electrical outage affecting Orfeo ** file sharing replace by a "cloud" oriented broader software (Owncloud) * 2012-11: XMPP problems -ejabberd cluster bugs) * 2012-12: ** Daneel is dead ** MOSH support == Admins == * Arnau [~2004-12 to now] (fallback admin since 2010-04-27, more active since early 2014) * Duck [begining to now] (leader) * Finger [2006-07-05 to 2008-02-04] (assistant) * Mmenal [~2004-12 to ~2006-07] * Rtp [2003-10 to 2007-07-15] == Evolution == No real traces were kept, so old numbers are mere rough guess. * 2000 -> 2004 ** more than 60 users served in the [[Media:Coinnetwork resal 2001-2002.png|CoinNetwork LAN]], nearly no external services besides a basic website and IRC ** services targeted for the CoinNetwork LAN * 2004 -> 2007 ** a few users (probably around 20) and 2 entities (RtpNet and [http://www.hurdfr.org/ HurdFr]) hosted ** more Internet-oriented services (complete mail software suite, MLs, Web hosting, DBs, RCS, ...) * 2007 -> 2010 ** more users (nearly 70 users in 2010, a few not very active) and 2 more entity hosted ([http://thebrain.lautre.net/ TheBrain] and [http://www.andesi.org/ Andesi]) ** more services (Jabber, user-friendly antispam, LDAP, IPv6, ...) == Photos == Look at the [http://photos.duckcorp.org/v/duckcorp/ gallery]. 89a63df75b007607930a804e04fdf2600be2a69d 424 423 2014-03-03T14:34:04Z Duck 2 /* Key Dates */ wikitext text/x-wiki == The DuckCorp Story == DuckCorp was born in 2000, from Duck's will to construct something more personal out of the CoinNetwork student house's LAN. At that time, it was merely a simple website, advertising a few personal projects. Later, several machines, gathered with various parts from people willing to dispose of them, used the 'duckcorp.org' domain name and provided services for CoinNetwork; this was the begining of the DC's sponsoring mission. Duck then met Rtp, and they began sharing about system administration topics. As they were willing to administrate CoinNetwork better, they began working on the infrastructure and tools together. Rtp created RtpNet, and received the magical SSH key to be a full DC administrator (so did Duck for Rtpnet indeed). They developed a software prototype aimed at managing the most important services of a distributed web of servers (LMS, LDAP Management System), which helped reducing the daily burden of CoinNetwork's administration a lot. After a while working hand in hand, they both found a job and moved to a new home, still helping each other when possible. Currently, RtpNet and DuckCorp have different goals, and follow their own path. On the way, DC found friendly sponsors (in order of appearance): * Nerim (first Orfeo's housing, IPv6 block, indirect sponsor via Hivane) * Hivane (global connectivity, secondary NS and MX) * Sivit (special accomodations for Toushirou's housing and connectivity) (now Nerim again, as it was acquired recently) * Alionis (Orfeo's housing) Thanks a lot pals :-). == The MilkyPond Project == MP is an historical share of an IRC network between DC and RN when they both stopped working on the CoinNetwork project. They were willing to cooperate but with the important changes that occurred in their lives, only IRC was kept as a communication link. With time going, DC began recreating services, with the main server Orfeo being kindly sponsored by Nerim, which was used by RN and later by other associations or individuals. Nothing much is done in the name of MP until 2007, besides adding a Jabber server. In early 2007, RN hired a server, Lechat (Dédibox), and was willing to participate more in the share. At the end of the year, T1R joined to help improving the IRC Network. In September 2007, RN was not able to provide services anymore, as it was too much of a burden. Nevertheless, it is still sponsoring the ''milkypond.org'' domain since then. == Key Dates == * 2000-05-22: DuckCorp is created * 2003-04-25: IANA PEN 16829 * 2003-07-09: RtpNet is created * ~2003-10-20: RSA key exchanged between DC and RN (date is from the exif info, but Photoshop is in the way) * 2004-06-12: MilkyPond is created (after DC and RN stopped working on the CoinNetwork project) * 2005-04/05: Orfeo RAM upgraded (512Mo->1.5Go) (blocked to ~800Mo [[Media:Orfeo.duckcorp.org-memory-day.png|until highmem in kernel]]) * 2005-05: IPv6 Ready (using a tunnel) * 2005-11: ** the users' mailing-list started ** major mail system improvements (SMTP auth, improved antispam, webdesk) * 2005-12-08: Orfeo moved from the Nerim's Ivry datacenter to the Nerim suite in the LDCOM Courbevoie datacenter * 2006-01 to 2006-06: Orfeo problems due to an [http://xfs.org/index.php/XFS_FAQ#Q:_What_is_the_issue_with_directory_corruption_in_Linux_2.6.17.3F XFS bug] * 2007-04: IPv6 Ready (native IPv6) * 2007-07: Tōshirō bought and being prepared * 2007-08-08: Nerim's boss shutdown Orfeo violently; quickly repaired and setup behind a mere ADSL (helped by Nerim friends), but BLACKOUT for most services * 2007-08-13: Tōshirō installed in the Sivit suite of the Redbus datacenter, services progressively back online * 2007-09: LDAP infrastructure (again) * 2007-12: ** Orfeo-NG bough and installed in Alionis suite in EQX (Equinix) datacenter ** T1R enters MilkyPond (for the IRC network) * 2008-07: VCS rework, Portal (Restricted Access Helper), Projects Manager (Redmine) * 2009-03: Banya bot (mail gateway for DNS modification, part of the CyborgHood project) * 2009-09: Orfeo moved to [http://www.alionis.net/infra/VBO.html Alionis VBO datacenter] * 2010-03: Thorfinn acquired (Nerim VDS) * 2010-04-24: stratum 2 NTP server [http://support.ntp.org/bin/view/Servers/NtpDuckCorpOrg publicly advertised] and in the [http://www.pool.ntp.org/user/DuckCorp pool] * 2010-05-22: 10th Anniversary !!! * 2010-05-29: 10th Anniversary party with users/sponsors/friends * 2010-10: DNS TSIG and DNSSEC * 2010-11: Toushirou at Gbps (with a reboot to work around a firmware bug) * 2010-12: ** power outage at VBO, kernel bug preventing Orfeo to restart (IPMI-related) ** Jinta (VM provided by mm), replacing T1R secondary IRC server * 2011-01: problems with backup and capacity * 2011-05: improved IMAP and SIEVE support, shared and public folders * 2011-06: launch of the [https://projects.duckcorp.org/projects/dc-ducklings-volunteer-activities Ducklings Volunteer Activities] * 2011-08: new web service: news feeds (tt-rss), IRC on web replacement, XMPP on web, file sharing (Jyraphe), new web stats (Piwik) * 2011-10: Jinta is dow for good * 2012-01: Korutopi is born (backups) * 2012-02: handly mail retraining through IMAP * 2012-08: ** short electrical outage affecting Orfeo ** file sharing replace by a "cloud" oriented broader software (Owncloud) * 2012-11: XMPP problems -ejabberd cluster bugs) * 2012-12: ** Daneel is dead ** MOSH support == Admins == * Arnau [~2004-12 to now] (fallback admin since 2010-04-27, more active since early 2014) * Duck [begining to now] (leader) * Finger [2006-07-05 to 2008-02-04] (assistant) * Mmenal [~2004-12 to ~2006-07] * Rtp [2003-10 to 2007-07-15] == Evolution == No real traces were kept, so old numbers are mere rough guess. * 2000 -> 2004 ** more than 60 users served in the [[Media:Coinnetwork resal 2001-2002.png|CoinNetwork LAN]], nearly no external services besides a basic website and IRC ** services targeted for the CoinNetwork LAN * 2004 -> 2007 ** a few users (probably around 20) and 2 entities (RtpNet and [http://www.hurdfr.org/ HurdFr]) hosted ** more Internet-oriented services (complete mail software suite, MLs, Web hosting, DBs, RCS, ...) * 2007 -> 2010 ** more users (nearly 70 users in 2010, a few not very active) and 2 more entity hosted ([http://thebrain.lautre.net/ TheBrain] and [http://www.andesi.org/ Andesi]) ** more services (Jabber, user-friendly antispam, LDAP, IPv6, ...) == Photos == Look at the [http://photos.duckcorp.org/v/duckcorp/ gallery]. b2708c6b6f161c5a87214d51fc459c949fa1228e 425 424 2014-03-03T14:47:04Z Duck 2 /* Key Dates */ wikitext text/x-wiki == The DuckCorp Story == DuckCorp was born in 2000, from Duck's will to construct something more personal out of the CoinNetwork student house's LAN. At that time, it was merely a simple website, advertising a few personal projects. Later, several machines, gathered with various parts from people willing to dispose of them, used the 'duckcorp.org' domain name and provided services for CoinNetwork; this was the begining of the DC's sponsoring mission. Duck then met Rtp, and they began sharing about system administration topics. As they were willing to administrate CoinNetwork better, they began working on the infrastructure and tools together. Rtp created RtpNet, and received the magical SSH key to be a full DC administrator (so did Duck for Rtpnet indeed). They developed a software prototype aimed at managing the most important services of a distributed web of servers (LMS, LDAP Management System), which helped reducing the daily burden of CoinNetwork's administration a lot. After a while working hand in hand, they both found a job and moved to a new home, still helping each other when possible. Currently, RtpNet and DuckCorp have different goals, and follow their own path. On the way, DC found friendly sponsors (in order of appearance): * Nerim (first Orfeo's housing, IPv6 block, indirect sponsor via Hivane) * Hivane (global connectivity, secondary NS and MX) * Sivit (special accomodations for Toushirou's housing and connectivity) (now Nerim again, as it was acquired recently) * Alionis (Orfeo's housing) Thanks a lot pals :-). == The MilkyPond Project == MP is an historical share of an IRC network between DC and RN when they both stopped working on the CoinNetwork project. They were willing to cooperate but with the important changes that occurred in their lives, only IRC was kept as a communication link. With time going, DC began recreating services, with the main server Orfeo being kindly sponsored by Nerim, which was used by RN and later by other associations or individuals. Nothing much is done in the name of MP until 2007, besides adding a Jabber server. In early 2007, RN hired a server, Lechat (Dédibox), and was willing to participate more in the share. At the end of the year, T1R joined to help improving the IRC Network. In September 2007, RN was not able to provide services anymore, as it was too much of a burden. Nevertheless, it is still sponsoring the ''milkypond.org'' domain since then. == Key Dates == * 2000-05-22: DuckCorp is created * 2003-04-25: IANA PEN 16829 * 2003-07-09: RtpNet is created * ~2003-10-20: RSA key exchanged between DC and RN (date is from the exif info, but Photoshop is in the way) * 2004-06-12: MilkyPond is created (after DC and RN stopped working on the CoinNetwork project) * 2005-04/05: Orfeo RAM upgraded (512Mo->1.5Go) (blocked to ~800Mo [[Media:Orfeo.duckcorp.org-memory-day.png|until highmem in kernel]]) * 2005-05: IPv6 Ready (using a tunnel) * 2005-11: ** the users' mailing-list started ** major mail system improvements (SMTP auth, improved antispam, webdesk) * 2005-12-08: Orfeo moved from the Nerim's Ivry datacenter to the Nerim suite in the LDCOM Courbevoie datacenter * 2006-01 to 2006-06: Orfeo problems due to an [http://xfs.org/index.php/XFS_FAQ#Q:_What_is_the_issue_with_directory_corruption_in_Linux_2.6.17.3F XFS bug] * 2007-04: IPv6 Ready (native IPv6) * 2007-07: Tōshirō bought and being prepared * 2007-08-08: Nerim's boss shutdown Orfeo violently; quickly repaired and setup behind a mere ADSL (helped by Nerim friends), but BLACKOUT for most services * 2007-08-13: Tōshirō installed in the Sivit suite of the Redbus datacenter, services progressively back online * 2007-09: LDAP infrastructure (again) * 2007-12: ** Orfeo-NG bough and installed in Alionis suite in EQX (Equinix) datacenter ** T1R enters MilkyPond (for the IRC network) * 2008-07: VCS rework, Portal (Restricted Access Helper), Projects Manager (Redmine) * 2009-03: Banya bot (mail gateway for DNS modification, part of the CyborgHood project) * 2009-09: Orfeo moved to [http://www.alionis.net/infra/VBO.html Alionis VBO datacenter] * 2010-03: Thorfinn acquired (Nerim VDS) * 2010-04-24: stratum 2 NTP server [http://support.ntp.org/bin/view/Servers/NtpDuckCorpOrg publicly advertised] and in the [http://www.pool.ntp.org/user/DuckCorp pool] * 2010-05-22: 10th Anniversary !!! * 2010-05-29: 10th Anniversary party with users/sponsors/friends * 2010-10: DNS TSIG and DNSSEC * 2010-11: Toushirou reached Gbps (with a reboot to work around a firmware bug) * 2010-12: ** power outage at VBO, kernel bug preventing Orfeo to restart (IPMI-related) ** Jinta (VM provided by mm), replacing T1R secondary IRC server * 2011-01: problems with backup and capacity * 2011-05: improved IMAP and SIEVE support, shared and public folders * 2011-06: launch of the [https://projects.duckcorp.org/projects/dc-ducklings-volunteer-activities Ducklings Volunteer Activities] * 2011-08: new web service: news feeds (tt-rss), IRC on web replacement, XMPP on web, file sharing (Jyraphe), new web stats (Piwik) * 2011-10: Jinta is dow for good * 2012-01: Korutopi is born (backups) * 2012-02: handly mail retraining through IMAP * 2012-08: ** short electrical outage affecting Orfeo ** file sharing replace by a "cloud" oriented broader software (Owncloud) * 2012-11: XMPP problems -ejabberd cluster bugs) * 2012-12: ** Daneel is dead ** MOSH support * 2013-06: * Nerim's sponsoring is over => many things to change and end of the IPv6 broker service * [http://www.minetest.net/ Minetest] server * 2013-10: ** Thorfinn moving from the legacy Nerim Root infrastructure to the Sivit/Nerim virtualization plateform ** Orfeo reached Gbps * 2013-01 to 2012-02, lots of maintenance and consolidation: ** web hosting major upgrade ** Daneel is back alive (so do supervision) ** Toushirou's having bad load problems ** new XMPP server (replacing the wonky ejabberd cluster) ** new blog plateform * 2013-03: ** Thorfinn moving at Hivane ** Jinta revival (Hivane VM) in order to unload Toushirou == Admins == * Arnau [~2004-12 to now] (fallback admin since 2010-04-27, more active since early 2014) * Duck [begining to now] (leader) * Finger [2006-07-05 to 2008-02-04] (assistant) * Mmenal [~2004-12 to ~2006-07] * Rtp [2003-10 to 2007-07-15] == Evolution == No real traces were kept, so old numbers are mere rough guess. * 2000 -> 2004 ** more than 60 users served in the [[Media:Coinnetwork resal 2001-2002.png|CoinNetwork LAN]], nearly no external services besides a basic website and IRC ** services targeted for the CoinNetwork LAN * 2004 -> 2007 ** a few users (probably around 20) and 2 entities (RtpNet and [http://www.hurdfr.org/ HurdFr]) hosted ** more Internet-oriented services (complete mail software suite, MLs, Web hosting, DBs, RCS, ...) * 2007 -> 2010 ** more users (nearly 70 users in 2010, a few not very active) and 2 more entity hosted ([http://thebrain.lautre.net/ TheBrain] and [http://www.andesi.org/ Andesi]) ** more services (Jabber, user-friendly antispam, LDAP, IPv6, ...) == Photos == Look at the [http://photos.duckcorp.org/v/duckcorp/ gallery]. f9ebe7d5c91b0ac369c18d5f004ce55ed8920cce 426 425 2014-03-03T14:47:32Z Duck 2 /* Key Dates */ wikitext text/x-wiki == The DuckCorp Story == DuckCorp was born in 2000, from Duck's will to construct something more personal out of the CoinNetwork student house's LAN. At that time, it was merely a simple website, advertising a few personal projects. Later, several machines, gathered with various parts from people willing to dispose of them, used the 'duckcorp.org' domain name and provided services for CoinNetwork; this was the begining of the DC's sponsoring mission. Duck then met Rtp, and they began sharing about system administration topics. As they were willing to administrate CoinNetwork better, they began working on the infrastructure and tools together. Rtp created RtpNet, and received the magical SSH key to be a full DC administrator (so did Duck for Rtpnet indeed). They developed a software prototype aimed at managing the most important services of a distributed web of servers (LMS, LDAP Management System), which helped reducing the daily burden of CoinNetwork's administration a lot. After a while working hand in hand, they both found a job and moved to a new home, still helping each other when possible. Currently, RtpNet and DuckCorp have different goals, and follow their own path. On the way, DC found friendly sponsors (in order of appearance): * Nerim (first Orfeo's housing, IPv6 block, indirect sponsor via Hivane) * Hivane (global connectivity, secondary NS and MX) * Sivit (special accomodations for Toushirou's housing and connectivity) (now Nerim again, as it was acquired recently) * Alionis (Orfeo's housing) Thanks a lot pals :-). == The MilkyPond Project == MP is an historical share of an IRC network between DC and RN when they both stopped working on the CoinNetwork project. They were willing to cooperate but with the important changes that occurred in their lives, only IRC was kept as a communication link. With time going, DC began recreating services, with the main server Orfeo being kindly sponsored by Nerim, which was used by RN and later by other associations or individuals. Nothing much is done in the name of MP until 2007, besides adding a Jabber server. In early 2007, RN hired a server, Lechat (Dédibox), and was willing to participate more in the share. At the end of the year, T1R joined to help improving the IRC Network. In September 2007, RN was not able to provide services anymore, as it was too much of a burden. Nevertheless, it is still sponsoring the ''milkypond.org'' domain since then. == Key Dates == * 2000-05-22: DuckCorp is created * 2003-04-25: IANA PEN 16829 * 2003-07-09: RtpNet is created * ~2003-10-20: RSA key exchanged between DC and RN (date is from the exif info, but Photoshop is in the way) * 2004-06-12: MilkyPond is created (after DC and RN stopped working on the CoinNetwork project) * 2005-04/05: Orfeo RAM upgraded (512Mo->1.5Go) (blocked to ~800Mo [[Media:Orfeo.duckcorp.org-memory-day.png|until highmem in kernel]]) * 2005-05: IPv6 Ready (using a tunnel) * 2005-11: ** the users' mailing-list started ** major mail system improvements (SMTP auth, improved antispam, webdesk) * 2005-12-08: Orfeo moved from the Nerim's Ivry datacenter to the Nerim suite in the LDCOM Courbevoie datacenter * 2006-01 to 2006-06: Orfeo problems due to an [http://xfs.org/index.php/XFS_FAQ#Q:_What_is_the_issue_with_directory_corruption_in_Linux_2.6.17.3F XFS bug] * 2007-04: IPv6 Ready (native IPv6) * 2007-07: Tōshirō bought and being prepared * 2007-08-08: Nerim's boss shutdown Orfeo violently; quickly repaired and setup behind a mere ADSL (helped by Nerim friends), but BLACKOUT for most services * 2007-08-13: Tōshirō installed in the Sivit suite of the Redbus datacenter, services progressively back online * 2007-09: LDAP infrastructure (again) * 2007-12: ** Orfeo-NG bough and installed in Alionis suite in EQX (Equinix) datacenter ** T1R enters MilkyPond (for the IRC network) * 2008-07: VCS rework, Portal (Restricted Access Helper), Projects Manager (Redmine) * 2009-03: Banya bot (mail gateway for DNS modification, part of the CyborgHood project) * 2009-09: Orfeo moved to [http://www.alionis.net/infra/VBO.html Alionis VBO datacenter] * 2010-03: Thorfinn acquired (Nerim VDS) * 2010-04-24: stratum 2 NTP server [http://support.ntp.org/bin/view/Servers/NtpDuckCorpOrg publicly advertised] and in the [http://www.pool.ntp.org/user/DuckCorp pool] * 2010-05-22: 10th Anniversary !!! * 2010-05-29: 10th Anniversary party with users/sponsors/friends * 2010-10: DNS TSIG and DNSSEC * 2010-11: Toushirou reached Gbps (with a reboot to work around a firmware bug) * 2010-12: ** power outage at VBO, kernel bug preventing Orfeo to restart (IPMI-related) ** Jinta (VM provided by mm), replacing T1R secondary IRC server * 2011-01: problems with backup and capacity * 2011-05: improved IMAP and SIEVE support, shared and public folders * 2011-06: launch of the [https://projects.duckcorp.org/projects/dc-ducklings-volunteer-activities Ducklings Volunteer Activities] * 2011-08: new web service: news feeds (tt-rss), IRC on web replacement, XMPP on web, file sharing (Jyraphe), new web stats (Piwik) * 2011-10: Jinta is dow for good * 2012-01: Korutopi is born (backups) * 2012-02: handly mail retraining through IMAP * 2012-08: ** short electrical outage affecting Orfeo ** file sharing replace by a "cloud" oriented broader software (Owncloud) * 2012-11: XMPP problems -ejabberd cluster bugs) * 2012-12: ** Daneel is dead ** MOSH support * 2013-06: ** Nerim's sponsoring is over => many things to change and end of the IPv6 broker service ** [http://www.minetest.net/ Minetest] server * 2013-10: ** Thorfinn moving from the legacy Nerim Root infrastructure to the Sivit/Nerim virtualization plateform ** Orfeo reached Gbps * 2013-01 to 2012-02, lots of maintenance and consolidation: ** web hosting major upgrade ** Daneel is back alive (so do supervision) ** Toushirou's having bad load problems ** new XMPP server (replacing the wonky ejabberd cluster) ** new blog plateform * 2013-03: ** Thorfinn moving at Hivane ** Jinta revival (Hivane VM) in order to unload Toushirou == Admins == * Arnau [~2004-12 to now] (fallback admin since 2010-04-27, more active since early 2014) * Duck [begining to now] (leader) * Finger [2006-07-05 to 2008-02-04] (assistant) * Mmenal [~2004-12 to ~2006-07] * Rtp [2003-10 to 2007-07-15] == Evolution == No real traces were kept, so old numbers are mere rough guess. * 2000 -> 2004 ** more than 60 users served in the [[Media:Coinnetwork resal 2001-2002.png|CoinNetwork LAN]], nearly no external services besides a basic website and IRC ** services targeted for the CoinNetwork LAN * 2004 -> 2007 ** a few users (probably around 20) and 2 entities (RtpNet and [http://www.hurdfr.org/ HurdFr]) hosted ** more Internet-oriented services (complete mail software suite, MLs, Web hosting, DBs, RCS, ...) * 2007 -> 2010 ** more users (nearly 70 users in 2010, a few not very active) and 2 more entity hosted ([http://thebrain.lautre.net/ TheBrain] and [http://www.andesi.org/ Andesi]) ** more services (Jabber, user-friendly antispam, LDAP, IPv6, ...) == Photos == Look at the [http://photos.duckcorp.org/v/duckcorp/ gallery]. 1a25ced8f973c232f06c3b98a945abeec80c217b 427 426 2014-03-03T14:48:22Z Duck 2 /* Admins */ wikitext text/x-wiki == The DuckCorp Story == DuckCorp was born in 2000, from Duck's will to construct something more personal out of the CoinNetwork student house's LAN. At that time, it was merely a simple website, advertising a few personal projects. Later, several machines, gathered with various parts from people willing to dispose of them, used the 'duckcorp.org' domain name and provided services for CoinNetwork; this was the begining of the DC's sponsoring mission. Duck then met Rtp, and they began sharing about system administration topics. As they were willing to administrate CoinNetwork better, they began working on the infrastructure and tools together. Rtp created RtpNet, and received the magical SSH key to be a full DC administrator (so did Duck for Rtpnet indeed). They developed a software prototype aimed at managing the most important services of a distributed web of servers (LMS, LDAP Management System), which helped reducing the daily burden of CoinNetwork's administration a lot. After a while working hand in hand, they both found a job and moved to a new home, still helping each other when possible. Currently, RtpNet and DuckCorp have different goals, and follow their own path. On the way, DC found friendly sponsors (in order of appearance): * Nerim (first Orfeo's housing, IPv6 block, indirect sponsor via Hivane) * Hivane (global connectivity, secondary NS and MX) * Sivit (special accomodations for Toushirou's housing and connectivity) (now Nerim again, as it was acquired recently) * Alionis (Orfeo's housing) Thanks a lot pals :-). == The MilkyPond Project == MP is an historical share of an IRC network between DC and RN when they both stopped working on the CoinNetwork project. They were willing to cooperate but with the important changes that occurred in their lives, only IRC was kept as a communication link. With time going, DC began recreating services, with the main server Orfeo being kindly sponsored by Nerim, which was used by RN and later by other associations or individuals. Nothing much is done in the name of MP until 2007, besides adding a Jabber server. In early 2007, RN hired a server, Lechat (Dédibox), and was willing to participate more in the share. At the end of the year, T1R joined to help improving the IRC Network. In September 2007, RN was not able to provide services anymore, as it was too much of a burden. Nevertheless, it is still sponsoring the ''milkypond.org'' domain since then. == Key Dates == * 2000-05-22: DuckCorp is created * 2003-04-25: IANA PEN 16829 * 2003-07-09: RtpNet is created * ~2003-10-20: RSA key exchanged between DC and RN (date is from the exif info, but Photoshop is in the way) * 2004-06-12: MilkyPond is created (after DC and RN stopped working on the CoinNetwork project) * 2005-04/05: Orfeo RAM upgraded (512Mo->1.5Go) (blocked to ~800Mo [[Media:Orfeo.duckcorp.org-memory-day.png|until highmem in kernel]]) * 2005-05: IPv6 Ready (using a tunnel) * 2005-11: ** the users' mailing-list started ** major mail system improvements (SMTP auth, improved antispam, webdesk) * 2005-12-08: Orfeo moved from the Nerim's Ivry datacenter to the Nerim suite in the LDCOM Courbevoie datacenter * 2006-01 to 2006-06: Orfeo problems due to an [http://xfs.org/index.php/XFS_FAQ#Q:_What_is_the_issue_with_directory_corruption_in_Linux_2.6.17.3F XFS bug] * 2007-04: IPv6 Ready (native IPv6) * 2007-07: Tōshirō bought and being prepared * 2007-08-08: Nerim's boss shutdown Orfeo violently; quickly repaired and setup behind a mere ADSL (helped by Nerim friends), but BLACKOUT for most services * 2007-08-13: Tōshirō installed in the Sivit suite of the Redbus datacenter, services progressively back online * 2007-09: LDAP infrastructure (again) * 2007-12: ** Orfeo-NG bough and installed in Alionis suite in EQX (Equinix) datacenter ** T1R enters MilkyPond (for the IRC network) * 2008-07: VCS rework, Portal (Restricted Access Helper), Projects Manager (Redmine) * 2009-03: Banya bot (mail gateway for DNS modification, part of the CyborgHood project) * 2009-09: Orfeo moved to [http://www.alionis.net/infra/VBO.html Alionis VBO datacenter] * 2010-03: Thorfinn acquired (Nerim VDS) * 2010-04-24: stratum 2 NTP server [http://support.ntp.org/bin/view/Servers/NtpDuckCorpOrg publicly advertised] and in the [http://www.pool.ntp.org/user/DuckCorp pool] * 2010-05-22: 10th Anniversary !!! * 2010-05-29: 10th Anniversary party with users/sponsors/friends * 2010-10: DNS TSIG and DNSSEC * 2010-11: Toushirou reached Gbps (with a reboot to work around a firmware bug) * 2010-12: ** power outage at VBO, kernel bug preventing Orfeo to restart (IPMI-related) ** Jinta (VM provided by mm), replacing T1R secondary IRC server * 2011-01: problems with backup and capacity * 2011-05: improved IMAP and SIEVE support, shared and public folders * 2011-06: launch of the [https://projects.duckcorp.org/projects/dc-ducklings-volunteer-activities Ducklings Volunteer Activities] * 2011-08: new web service: news feeds (tt-rss), IRC on web replacement, XMPP on web, file sharing (Jyraphe), new web stats (Piwik) * 2011-10: Jinta is dow for good * 2012-01: Korutopi is born (backups) * 2012-02: handly mail retraining through IMAP * 2012-08: ** short electrical outage affecting Orfeo ** file sharing replace by a "cloud" oriented broader software (Owncloud) * 2012-11: XMPP problems -ejabberd cluster bugs) * 2012-12: ** Daneel is dead ** MOSH support * 2013-06: ** Nerim's sponsoring is over => many things to change and end of the IPv6 broker service ** [http://www.minetest.net/ Minetest] server * 2013-10: ** Thorfinn moving from the legacy Nerim Root infrastructure to the Sivit/Nerim virtualization plateform ** Orfeo reached Gbps * 2013-01 to 2012-02, lots of maintenance and consolidation: ** web hosting major upgrade ** Daneel is back alive (so do supervision) ** Toushirou's having bad load problems ** new XMPP server (replacing the wonky ejabberd cluster) ** new blog plateform * 2013-03: ** Thorfinn moving at Hivane ** Jinta revival (Hivane VM) in order to unload Toushirou == Admins == * Arnau [~2004-12 to now] (fallback admin since 2010-04-27, more active since early 2014) * Duck [begining to now] (leader) * Finger [2006-07-05 to 2008-02-04] (assistant) * Mmenal [~2004-12 to ~2006-07] * Rtp [2003-10 to 2007-07-15, kernel assistant] == Evolution == No real traces were kept, so old numbers are mere rough guess. * 2000 -> 2004 ** more than 60 users served in the [[Media:Coinnetwork resal 2001-2002.png|CoinNetwork LAN]], nearly no external services besides a basic website and IRC ** services targeted for the CoinNetwork LAN * 2004 -> 2007 ** a few users (probably around 20) and 2 entities (RtpNet and [http://www.hurdfr.org/ HurdFr]) hosted ** more Internet-oriented services (complete mail software suite, MLs, Web hosting, DBs, RCS, ...) * 2007 -> 2010 ** more users (nearly 70 users in 2010, a few not very active) and 2 more entity hosted ([http://thebrain.lautre.net/ TheBrain] and [http://www.andesi.org/ Andesi]) ** more services (Jabber, user-friendly antispam, LDAP, IPv6, ...) == Photos == Look at the [http://photos.duckcorp.org/v/duckcorp/ gallery]. 41c283ddca83c80f834b9b81790ebaef4297450e 428 427 2014-03-03T14:49:01Z Duck 2 /* Admins */ wikitext text/x-wiki == The DuckCorp Story == DuckCorp was born in 2000, from Duck's will to construct something more personal out of the CoinNetwork student house's LAN. At that time, it was merely a simple website, advertising a few personal projects. Later, several machines, gathered with various parts from people willing to dispose of them, used the 'duckcorp.org' domain name and provided services for CoinNetwork; this was the begining of the DC's sponsoring mission. Duck then met Rtp, and they began sharing about system administration topics. As they were willing to administrate CoinNetwork better, they began working on the infrastructure and tools together. Rtp created RtpNet, and received the magical SSH key to be a full DC administrator (so did Duck for Rtpnet indeed). They developed a software prototype aimed at managing the most important services of a distributed web of servers (LMS, LDAP Management System), which helped reducing the daily burden of CoinNetwork's administration a lot. After a while working hand in hand, they both found a job and moved to a new home, still helping each other when possible. Currently, RtpNet and DuckCorp have different goals, and follow their own path. On the way, DC found friendly sponsors (in order of appearance): * Nerim (first Orfeo's housing, IPv6 block, indirect sponsor via Hivane) * Hivane (global connectivity, secondary NS and MX) * Sivit (special accomodations for Toushirou's housing and connectivity) (now Nerim again, as it was acquired recently) * Alionis (Orfeo's housing) Thanks a lot pals :-). == The MilkyPond Project == MP is an historical share of an IRC network between DC and RN when they both stopped working on the CoinNetwork project. They were willing to cooperate but with the important changes that occurred in their lives, only IRC was kept as a communication link. With time going, DC began recreating services, with the main server Orfeo being kindly sponsored by Nerim, which was used by RN and later by other associations or individuals. Nothing much is done in the name of MP until 2007, besides adding a Jabber server. In early 2007, RN hired a server, Lechat (Dédibox), and was willing to participate more in the share. At the end of the year, T1R joined to help improving the IRC Network. In September 2007, RN was not able to provide services anymore, as it was too much of a burden. Nevertheless, it is still sponsoring the ''milkypond.org'' domain since then. == Key Dates == * 2000-05-22: DuckCorp is created * 2003-04-25: IANA PEN 16829 * 2003-07-09: RtpNet is created * ~2003-10-20: RSA key exchanged between DC and RN (date is from the exif info, but Photoshop is in the way) * 2004-06-12: MilkyPond is created (after DC and RN stopped working on the CoinNetwork project) * 2005-04/05: Orfeo RAM upgraded (512Mo->1.5Go) (blocked to ~800Mo [[Media:Orfeo.duckcorp.org-memory-day.png|until highmem in kernel]]) * 2005-05: IPv6 Ready (using a tunnel) * 2005-11: ** the users' mailing-list started ** major mail system improvements (SMTP auth, improved antispam, webdesk) * 2005-12-08: Orfeo moved from the Nerim's Ivry datacenter to the Nerim suite in the LDCOM Courbevoie datacenter * 2006-01 to 2006-06: Orfeo problems due to an [http://xfs.org/index.php/XFS_FAQ#Q:_What_is_the_issue_with_directory_corruption_in_Linux_2.6.17.3F XFS bug] * 2007-04: IPv6 Ready (native IPv6) * 2007-07: Tōshirō bought and being prepared * 2007-08-08: Nerim's boss shutdown Orfeo violently; quickly repaired and setup behind a mere ADSL (helped by Nerim friends), but BLACKOUT for most services * 2007-08-13: Tōshirō installed in the Sivit suite of the Redbus datacenter, services progressively back online * 2007-09: LDAP infrastructure (again) * 2007-12: ** Orfeo-NG bough and installed in Alionis suite in EQX (Equinix) datacenter ** T1R enters MilkyPond (for the IRC network) * 2008-07: VCS rework, Portal (Restricted Access Helper), Projects Manager (Redmine) * 2009-03: Banya bot (mail gateway for DNS modification, part of the CyborgHood project) * 2009-09: Orfeo moved to [http://www.alionis.net/infra/VBO.html Alionis VBO datacenter] * 2010-03: Thorfinn acquired (Nerim VDS) * 2010-04-24: stratum 2 NTP server [http://support.ntp.org/bin/view/Servers/NtpDuckCorpOrg publicly advertised] and in the [http://www.pool.ntp.org/user/DuckCorp pool] * 2010-05-22: 10th Anniversary !!! * 2010-05-29: 10th Anniversary party with users/sponsors/friends * 2010-10: DNS TSIG and DNSSEC * 2010-11: Toushirou reached Gbps (with a reboot to work around a firmware bug) * 2010-12: ** power outage at VBO, kernel bug preventing Orfeo to restart (IPMI-related) ** Jinta (VM provided by mm), replacing T1R secondary IRC server * 2011-01: problems with backup and capacity * 2011-05: improved IMAP and SIEVE support, shared and public folders * 2011-06: launch of the [https://projects.duckcorp.org/projects/dc-ducklings-volunteer-activities Ducklings Volunteer Activities] * 2011-08: new web service: news feeds (tt-rss), IRC on web replacement, XMPP on web, file sharing (Jyraphe), new web stats (Piwik) * 2011-10: Jinta is dow for good * 2012-01: Korutopi is born (backups) * 2012-02: handly mail retraining through IMAP * 2012-08: ** short electrical outage affecting Orfeo ** file sharing replace by a "cloud" oriented broader software (Owncloud) * 2012-11: XMPP problems -ejabberd cluster bugs) * 2012-12: ** Daneel is dead ** MOSH support * 2013-06: ** Nerim's sponsoring is over => many things to change and end of the IPv6 broker service ** [http://www.minetest.net/ Minetest] server * 2013-10: ** Thorfinn moving from the legacy Nerim Root infrastructure to the Sivit/Nerim virtualization plateform ** Orfeo reached Gbps * 2013-01 to 2012-02, lots of maintenance and consolidation: ** web hosting major upgrade ** Daneel is back alive (so do supervision) ** Toushirou's having bad load problems ** new XMPP server (replacing the wonky ejabberd cluster) ** new blog plateform * 2013-03: ** Thorfinn moving at Hivane ** Jinta revival (Hivane VM) in order to unload Toushirou == Admins == * Arnau [~2004-12 to now] (fallback admin since 2010-04-27, more active since early 2014) * Duck [begining to now] (leader) * Finger [2006-07-05 to 2008-02-04] (assistant) * Mmenal [~2004-12 to ~2006-07] * Rtp [2003-10 to 2007-07-15, kernel assistant when needed] == Evolution == No real traces were kept, so old numbers are mere rough guess. * 2000 -> 2004 ** more than 60 users served in the [[Media:Coinnetwork resal 2001-2002.png|CoinNetwork LAN]], nearly no external services besides a basic website and IRC ** services targeted for the CoinNetwork LAN * 2004 -> 2007 ** a few users (probably around 20) and 2 entities (RtpNet and [http://www.hurdfr.org/ HurdFr]) hosted ** more Internet-oriented services (complete mail software suite, MLs, Web hosting, DBs, RCS, ...) * 2007 -> 2010 ** more users (nearly 70 users in 2010, a few not very active) and 2 more entity hosted ([http://thebrain.lautre.net/ TheBrain] and [http://www.andesi.org/ Andesi]) ** more services (Jabber, user-friendly antispam, LDAP, IPv6, ...) == Photos == Look at the [http://photos.duckcorp.org/v/duckcorp/ gallery]. 9f85d254c4402aee533538ca1ebe72083ce0962f 429 428 2014-03-03T14:49:55Z Duck 2 /* Key Dates */ wikitext text/x-wiki == The DuckCorp Story == DuckCorp was born in 2000, from Duck's will to construct something more personal out of the CoinNetwork student house's LAN. At that time, it was merely a simple website, advertising a few personal projects. Later, several machines, gathered with various parts from people willing to dispose of them, used the 'duckcorp.org' domain name and provided services for CoinNetwork; this was the begining of the DC's sponsoring mission. Duck then met Rtp, and they began sharing about system administration topics. As they were willing to administrate CoinNetwork better, they began working on the infrastructure and tools together. Rtp created RtpNet, and received the magical SSH key to be a full DC administrator (so did Duck for Rtpnet indeed). They developed a software prototype aimed at managing the most important services of a distributed web of servers (LMS, LDAP Management System), which helped reducing the daily burden of CoinNetwork's administration a lot. After a while working hand in hand, they both found a job and moved to a new home, still helping each other when possible. Currently, RtpNet and DuckCorp have different goals, and follow their own path. On the way, DC found friendly sponsors (in order of appearance): * Nerim (first Orfeo's housing, IPv6 block, indirect sponsor via Hivane) * Hivane (global connectivity, secondary NS and MX) * Sivit (special accomodations for Toushirou's housing and connectivity) (now Nerim again, as it was acquired recently) * Alionis (Orfeo's housing) Thanks a lot pals :-). == The MilkyPond Project == MP is an historical share of an IRC network between DC and RN when they both stopped working on the CoinNetwork project. They were willing to cooperate but with the important changes that occurred in their lives, only IRC was kept as a communication link. With time going, DC began recreating services, with the main server Orfeo being kindly sponsored by Nerim, which was used by RN and later by other associations or individuals. Nothing much is done in the name of MP until 2007, besides adding a Jabber server. In early 2007, RN hired a server, Lechat (Dédibox), and was willing to participate more in the share. At the end of the year, T1R joined to help improving the IRC Network. In September 2007, RN was not able to provide services anymore, as it was too much of a burden. Nevertheless, it is still sponsoring the ''milkypond.org'' domain since then. == Key Dates == * 2000-05-22: DuckCorp is created * 2003-04-25: IANA PEN 16829 * 2003-07-09: RtpNet is created * ~2003-10-20: RSA key exchanged between DC and RN (date is from the exif info, but Photoshop is in the way) * 2004-06-12: MilkyPond is created (after DC and RN stopped working on the CoinNetwork project) * 2005-04/05: Orfeo RAM upgraded (512Mo->1.5Go) (blocked to ~800Mo [[Media:Orfeo.duckcorp.org-memory-day.png|until highmem in kernel]]) * 2005-05: IPv6 Ready (using a tunnel) * 2005-11: ** the users' mailing-list started ** major mail system improvements (SMTP auth, improved antispam, webdesk) * 2005-12-08: Orfeo moved from the Nerim's Ivry datacenter to the Nerim suite in the LDCOM Courbevoie datacenter * 2006-01 to 2006-06: Orfeo problems due to an [http://xfs.org/index.php/XFS_FAQ#Q:_What_is_the_issue_with_directory_corruption_in_Linux_2.6.17.3F XFS bug] * 2007-04: IPv6 Ready (native IPv6) * 2007-07: Tōshirō bought and being prepared * 2007-08-08: Nerim's boss shutdown Orfeo violently; quickly repaired and setup behind a mere ADSL (helped by Nerim friends), but BLACKOUT for most services * 2007-08-13: Tōshirō installed in the Sivit suite of the Redbus datacenter, services progressively back online * 2007-09: LDAP infrastructure (again) * 2007-12: ** Orfeo-NG bough and installed in Alionis suite in EQX (Equinix) datacenter ** T1R enters MilkyPond (for the IRC network) * 2008-07: VCS rework, Portal (Restricted Access Helper), Projects Manager (Redmine) * 2009-03: Banya bot (mail gateway for DNS modification, part of the CyborgHood project) * 2009-09: Orfeo moved to [http://www.alionis.net/infra/VBO.html Alionis VBO datacenter] * 2010-03: Thorfinn acquired (Nerim VDS) * 2010-04-24: stratum 2 NTP server [http://support.ntp.org/bin/view/Servers/NtpDuckCorpOrg publicly advertised] and in the [http://www.pool.ntp.org/user/DuckCorp pool] * 2010-05-22: 10th Anniversary !!! * 2010-05-29: 10th Anniversary party with users/sponsors/friends * 2010-10: DNS TSIG and DNSSEC * 2010-11: Toushirou reached Gbps (with a reboot to work around a firmware bug) * 2010-12: ** power outage at VBO, kernel bug preventing Orfeo to restart (IPMI-related) ** Jinta (VM provided by mm), replacing T1R secondary IRC server * 2011-01: problems with backup and capacity * 2011-05: improved IMAP and SIEVE support, shared and public folders * 2011-06: launch of the [https://projects.duckcorp.org/projects/dc-ducklings-volunteer-activities Ducklings Volunteer Activities] * 2011-08: new web service: news feeds (tt-rss), IRC on web replacement, XMPP on web, file sharing (Jyraphe), new web stats (Piwik) * 2011-10: Jinta is dow for good * 2012-01: Korutopi is born (backups) * 2012-02: handly mail retraining through IMAP * 2012-08: ** short electrical outage affecting Orfeo ** file sharing replace by a "cloud" oriented broader software (Owncloud) * 2012-11: XMPP problems -ejabberd cluster bugs) * 2012-12: ** Daneel is dead ** MOSH support * 2013-06: ** Nerim's sponsoring is over => many things to change and end of the IPv6 broker service ** [http://www.minetest.net/ Minetest] server * 2013-10: ** Thorfinn moving from the legacy Nerim Root infrastructure to the Sivit/Nerim virtualization plateform ** Orfeo reached Gbps * 2014-01 to 2014-02, lots of maintenance and consolidation: ** web hosting major upgrade ** Daneel is back alive (so do supervision) ** Toushirou's having bad load problems ** new XMPP server (replacing the wonky ejabberd cluster) ** new blog plateform * 2014-03: ** Thorfinn moving at Hivane ** Jinta revival (Hivane VM) in order to unload Toushirou == Admins == * Arnau [~2004-12 to now] (fallback admin since 2010-04-27, more active since early 2014) * Duck [begining to now] (leader) * Finger [2006-07-05 to 2008-02-04] (assistant) * Mmenal [~2004-12 to ~2006-07] * Rtp [2003-10 to 2007-07-15, kernel assistant when needed] == Evolution == No real traces were kept, so old numbers are mere rough guess. * 2000 -> 2004 ** more than 60 users served in the [[Media:Coinnetwork resal 2001-2002.png|CoinNetwork LAN]], nearly no external services besides a basic website and IRC ** services targeted for the CoinNetwork LAN * 2004 -> 2007 ** a few users (probably around 20) and 2 entities (RtpNet and [http://www.hurdfr.org/ HurdFr]) hosted ** more Internet-oriented services (complete mail software suite, MLs, Web hosting, DBs, RCS, ...) * 2007 -> 2010 ** more users (nearly 70 users in 2010, a few not very active) and 2 more entity hosted ([http://thebrain.lautre.net/ TheBrain] and [http://www.andesi.org/ Andesi]) ** more services (Jabber, user-friendly antispam, LDAP, IPv6, ...) == Photos == Look at the [http://photos.duckcorp.org/v/duckcorp/ gallery]. 8d5e7edf9a81c0a231f276697607bb9c31bdd7b1 440 429 2014-04-02T13:26:47Z Duck 2 /* Admins */ wikitext text/x-wiki == The DuckCorp Story == DuckCorp was born in 2000, from Duck's will to construct something more personal out of the CoinNetwork student house's LAN. At that time, it was merely a simple website, advertising a few personal projects. Later, several machines, gathered with various parts from people willing to dispose of them, used the 'duckcorp.org' domain name and provided services for CoinNetwork; this was the begining of the DC's sponsoring mission. Duck then met Rtp, and they began sharing about system administration topics. As they were willing to administrate CoinNetwork better, they began working on the infrastructure and tools together. Rtp created RtpNet, and received the magical SSH key to be a full DC administrator (so did Duck for Rtpnet indeed). They developed a software prototype aimed at managing the most important services of a distributed web of servers (LMS, LDAP Management System), which helped reducing the daily burden of CoinNetwork's administration a lot. After a while working hand in hand, they both found a job and moved to a new home, still helping each other when possible. Currently, RtpNet and DuckCorp have different goals, and follow their own path. On the way, DC found friendly sponsors (in order of appearance): * Nerim (first Orfeo's housing, IPv6 block, indirect sponsor via Hivane) * Hivane (global connectivity, secondary NS and MX) * Sivit (special accomodations for Toushirou's housing and connectivity) (now Nerim again, as it was acquired recently) * Alionis (Orfeo's housing) Thanks a lot pals :-). == The MilkyPond Project == MP is an historical share of an IRC network between DC and RN when they both stopped working on the CoinNetwork project. They were willing to cooperate but with the important changes that occurred in their lives, only IRC was kept as a communication link. With time going, DC began recreating services, with the main server Orfeo being kindly sponsored by Nerim, which was used by RN and later by other associations or individuals. Nothing much is done in the name of MP until 2007, besides adding a Jabber server. In early 2007, RN hired a server, Lechat (Dédibox), and was willing to participate more in the share. At the end of the year, T1R joined to help improving the IRC Network. In September 2007, RN was not able to provide services anymore, as it was too much of a burden. Nevertheless, it is still sponsoring the ''milkypond.org'' domain since then. == Key Dates == * 2000-05-22: DuckCorp is created * 2003-04-25: IANA PEN 16829 * 2003-07-09: RtpNet is created * ~2003-10-20: RSA key exchanged between DC and RN (date is from the exif info, but Photoshop is in the way) * 2004-06-12: MilkyPond is created (after DC and RN stopped working on the CoinNetwork project) * 2005-04/05: Orfeo RAM upgraded (512Mo->1.5Go) (blocked to ~800Mo [[Media:Orfeo.duckcorp.org-memory-day.png|until highmem in kernel]]) * 2005-05: IPv6 Ready (using a tunnel) * 2005-11: ** the users' mailing-list started ** major mail system improvements (SMTP auth, improved antispam, webdesk) * 2005-12-08: Orfeo moved from the Nerim's Ivry datacenter to the Nerim suite in the LDCOM Courbevoie datacenter * 2006-01 to 2006-06: Orfeo problems due to an [http://xfs.org/index.php/XFS_FAQ#Q:_What_is_the_issue_with_directory_corruption_in_Linux_2.6.17.3F XFS bug] * 2007-04: IPv6 Ready (native IPv6) * 2007-07: Tōshirō bought and being prepared * 2007-08-08: Nerim's boss shutdown Orfeo violently; quickly repaired and setup behind a mere ADSL (helped by Nerim friends), but BLACKOUT for most services * 2007-08-13: Tōshirō installed in the Sivit suite of the Redbus datacenter, services progressively back online * 2007-09: LDAP infrastructure (again) * 2007-12: ** Orfeo-NG bough and installed in Alionis suite in EQX (Equinix) datacenter ** T1R enters MilkyPond (for the IRC network) * 2008-07: VCS rework, Portal (Restricted Access Helper), Projects Manager (Redmine) * 2009-03: Banya bot (mail gateway for DNS modification, part of the CyborgHood project) * 2009-09: Orfeo moved to [http://www.alionis.net/infra/VBO.html Alionis VBO datacenter] * 2010-03: Thorfinn acquired (Nerim VDS) * 2010-04-24: stratum 2 NTP server [http://support.ntp.org/bin/view/Servers/NtpDuckCorpOrg publicly advertised] and in the [http://www.pool.ntp.org/user/DuckCorp pool] * 2010-05-22: 10th Anniversary !!! * 2010-05-29: 10th Anniversary party with users/sponsors/friends * 2010-10: DNS TSIG and DNSSEC * 2010-11: Toushirou reached Gbps (with a reboot to work around a firmware bug) * 2010-12: ** power outage at VBO, kernel bug preventing Orfeo to restart (IPMI-related) ** Jinta (VM provided by mm), replacing T1R secondary IRC server * 2011-01: problems with backup and capacity * 2011-05: improved IMAP and SIEVE support, shared and public folders * 2011-06: launch of the [https://projects.duckcorp.org/projects/dc-ducklings-volunteer-activities Ducklings Volunteer Activities] * 2011-08: new web service: news feeds (tt-rss), IRC on web replacement, XMPP on web, file sharing (Jyraphe), new web stats (Piwik) * 2011-10: Jinta is dow for good * 2012-01: Korutopi is born (backups) * 2012-02: handly mail retraining through IMAP * 2012-08: ** short electrical outage affecting Orfeo ** file sharing replace by a "cloud" oriented broader software (Owncloud) * 2012-11: XMPP problems -ejabberd cluster bugs) * 2012-12: ** Daneel is dead ** MOSH support * 2013-06: ** Nerim's sponsoring is over => many things to change and end of the IPv6 broker service ** [http://www.minetest.net/ Minetest] server * 2013-10: ** Thorfinn moving from the legacy Nerim Root infrastructure to the Sivit/Nerim virtualization plateform ** Orfeo reached Gbps * 2014-01 to 2014-02, lots of maintenance and consolidation: ** web hosting major upgrade ** Daneel is back alive (so do supervision) ** Toushirou's having bad load problems ** new XMPP server (replacing the wonky ejabberd cluster) ** new blog plateform * 2014-03: ** Thorfinn moving at Hivane ** Jinta revival (Hivane VM) in order to unload Toushirou == Admins == * Arnau [~2004-12 to now] (fallback admin since 2010-04-27, more active since early 2014) * Duck [begining to now] (leader) * Finger [2006-07-05 to 2008-02-04] (assistant) * Mmenal [~2004-12 to ~2006-07] * Pilou [2014-04-02 to now] (fallback admin in charge of hardware/breakage rescue) * Rtp [2003-10 to 2007-07-15, kernel assistant when needed] == Evolution == No real traces were kept, so old numbers are mere rough guess. * 2000 -> 2004 ** more than 60 users served in the [[Media:Coinnetwork resal 2001-2002.png|CoinNetwork LAN]], nearly no external services besides a basic website and IRC ** services targeted for the CoinNetwork LAN * 2004 -> 2007 ** a few users (probably around 20) and 2 entities (RtpNet and [http://www.hurdfr.org/ HurdFr]) hosted ** more Internet-oriented services (complete mail software suite, MLs, Web hosting, DBs, RCS, ...) * 2007 -> 2010 ** more users (nearly 70 users in 2010, a few not very active) and 2 more entity hosted ([http://thebrain.lautre.net/ TheBrain] and [http://www.andesi.org/ Andesi]) ** more services (Jabber, user-friendly antispam, LDAP, IPv6, ...) == Photos == Look at the [http://photos.duckcorp.org/v/duckcorp/ gallery]. 0a79c81a4bf89ab2ca26f1e7e67bcd9bcd12f0d7 441 440 2014-04-02T13:27:22Z Duck 2 /* Admins */ wikitext text/x-wiki == The DuckCorp Story == DuckCorp was born in 2000, from Duck's will to construct something more personal out of the CoinNetwork student house's LAN. At that time, it was merely a simple website, advertising a few personal projects. Later, several machines, gathered with various parts from people willing to dispose of them, used the 'duckcorp.org' domain name and provided services for CoinNetwork; this was the begining of the DC's sponsoring mission. Duck then met Rtp, and they began sharing about system administration topics. As they were willing to administrate CoinNetwork better, they began working on the infrastructure and tools together. Rtp created RtpNet, and received the magical SSH key to be a full DC administrator (so did Duck for Rtpnet indeed). They developed a software prototype aimed at managing the most important services of a distributed web of servers (LMS, LDAP Management System), which helped reducing the daily burden of CoinNetwork's administration a lot. After a while working hand in hand, they both found a job and moved to a new home, still helping each other when possible. Currently, RtpNet and DuckCorp have different goals, and follow their own path. On the way, DC found friendly sponsors (in order of appearance): * Nerim (first Orfeo's housing, IPv6 block, indirect sponsor via Hivane) * Hivane (global connectivity, secondary NS and MX) * Sivit (special accomodations for Toushirou's housing and connectivity) (now Nerim again, as it was acquired recently) * Alionis (Orfeo's housing) Thanks a lot pals :-). == The MilkyPond Project == MP is an historical share of an IRC network between DC and RN when they both stopped working on the CoinNetwork project. They were willing to cooperate but with the important changes that occurred in their lives, only IRC was kept as a communication link. With time going, DC began recreating services, with the main server Orfeo being kindly sponsored by Nerim, which was used by RN and later by other associations or individuals. Nothing much is done in the name of MP until 2007, besides adding a Jabber server. In early 2007, RN hired a server, Lechat (Dédibox), and was willing to participate more in the share. At the end of the year, T1R joined to help improving the IRC Network. In September 2007, RN was not able to provide services anymore, as it was too much of a burden. Nevertheless, it is still sponsoring the ''milkypond.org'' domain since then. == Key Dates == * 2000-05-22: DuckCorp is created * 2003-04-25: IANA PEN 16829 * 2003-07-09: RtpNet is created * ~2003-10-20: RSA key exchanged between DC and RN (date is from the exif info, but Photoshop is in the way) * 2004-06-12: MilkyPond is created (after DC and RN stopped working on the CoinNetwork project) * 2005-04/05: Orfeo RAM upgraded (512Mo->1.5Go) (blocked to ~800Mo [[Media:Orfeo.duckcorp.org-memory-day.png|until highmem in kernel]]) * 2005-05: IPv6 Ready (using a tunnel) * 2005-11: ** the users' mailing-list started ** major mail system improvements (SMTP auth, improved antispam, webdesk) * 2005-12-08: Orfeo moved from the Nerim's Ivry datacenter to the Nerim suite in the LDCOM Courbevoie datacenter * 2006-01 to 2006-06: Orfeo problems due to an [http://xfs.org/index.php/XFS_FAQ#Q:_What_is_the_issue_with_directory_corruption_in_Linux_2.6.17.3F XFS bug] * 2007-04: IPv6 Ready (native IPv6) * 2007-07: Tōshirō bought and being prepared * 2007-08-08: Nerim's boss shutdown Orfeo violently; quickly repaired and setup behind a mere ADSL (helped by Nerim friends), but BLACKOUT for most services * 2007-08-13: Tōshirō installed in the Sivit suite of the Redbus datacenter, services progressively back online * 2007-09: LDAP infrastructure (again) * 2007-12: ** Orfeo-NG bough and installed in Alionis suite in EQX (Equinix) datacenter ** T1R enters MilkyPond (for the IRC network) * 2008-07: VCS rework, Portal (Restricted Access Helper), Projects Manager (Redmine) * 2009-03: Banya bot (mail gateway for DNS modification, part of the CyborgHood project) * 2009-09: Orfeo moved to [http://www.alionis.net/infra/VBO.html Alionis VBO datacenter] * 2010-03: Thorfinn acquired (Nerim VDS) * 2010-04-24: stratum 2 NTP server [http://support.ntp.org/bin/view/Servers/NtpDuckCorpOrg publicly advertised] and in the [http://www.pool.ntp.org/user/DuckCorp pool] * 2010-05-22: 10th Anniversary !!! * 2010-05-29: 10th Anniversary party with users/sponsors/friends * 2010-10: DNS TSIG and DNSSEC * 2010-11: Toushirou reached Gbps (with a reboot to work around a firmware bug) * 2010-12: ** power outage at VBO, kernel bug preventing Orfeo to restart (IPMI-related) ** Jinta (VM provided by mm), replacing T1R secondary IRC server * 2011-01: problems with backup and capacity * 2011-05: improved IMAP and SIEVE support, shared and public folders * 2011-06: launch of the [https://projects.duckcorp.org/projects/dc-ducklings-volunteer-activities Ducklings Volunteer Activities] * 2011-08: new web service: news feeds (tt-rss), IRC on web replacement, XMPP on web, file sharing (Jyraphe), new web stats (Piwik) * 2011-10: Jinta is dow for good * 2012-01: Korutopi is born (backups) * 2012-02: handly mail retraining through IMAP * 2012-08: ** short electrical outage affecting Orfeo ** file sharing replace by a "cloud" oriented broader software (Owncloud) * 2012-11: XMPP problems -ejabberd cluster bugs) * 2012-12: ** Daneel is dead ** MOSH support * 2013-06: ** Nerim's sponsoring is over => many things to change and end of the IPv6 broker service ** [http://www.minetest.net/ Minetest] server * 2013-10: ** Thorfinn moving from the legacy Nerim Root infrastructure to the Sivit/Nerim virtualization plateform ** Orfeo reached Gbps * 2014-01 to 2014-02, lots of maintenance and consolidation: ** web hosting major upgrade ** Daneel is back alive (so do supervision) ** Toushirou's having bad load problems ** new XMPP server (replacing the wonky ejabberd cluster) ** new blog plateform * 2014-03: ** Thorfinn moving at Hivane ** Jinta revival (Hivane VM) in order to unload Toushirou == Admins == * '''Arnau''' [~2004-12 to now] (fallback admin since 2010-04-27, more active since early 2014) * '''Duck''' [begining to now] (leader) * Finger [2006-07-05 to 2008-02-04] (assistant) * Mmenal [~2004-12 to ~2006-07] * '''Pilou''' [2014-04-02 to now] (fallback admin in charge of hardware/breakage rescue) * Rtp [2003-10 to 2007-07-15, kernel assistant when needed] == Evolution == No real traces were kept, so old numbers are mere rough guess. * 2000 -> 2004 ** more than 60 users served in the [[Media:Coinnetwork resal 2001-2002.png|CoinNetwork LAN]], nearly no external services besides a basic website and IRC ** services targeted for the CoinNetwork LAN * 2004 -> 2007 ** a few users (probably around 20) and 2 entities (RtpNet and [http://www.hurdfr.org/ HurdFr]) hosted ** more Internet-oriented services (complete mail software suite, MLs, Web hosting, DBs, RCS, ...) * 2007 -> 2010 ** more users (nearly 70 users in 2010, a few not very active) and 2 more entity hosted ([http://thebrain.lautre.net/ TheBrain] and [http://www.andesi.org/ Andesi]) ** more services (Jabber, user-friendly antispam, LDAP, IPv6, ...) == Photos == Look at the [http://photos.duckcorp.org/v/duckcorp/ gallery]. 94a61340d4b6dee39488029e89d05d4dcf947704 0 67 430 382 2014-03-10T14:05:07Z Duck 2 /* Command Line Interface */ wikitext text/x-wiki {{Template:Service | description = This service is an online dictionary, used both for definitions and translations, providing information from multiple sources | prerequisite = | account = | ipv6 = false | security_notes = There is no big security concern except you can't be sure you're talking to our DICT server (no TLS support). }} == Access == === Web Interface === Use the following URL: http://dico.duckcorp.org/ === Command Line Interface === You need a DICT software to query the dictionary. On Debian you can install it easily using: apt-get install dico or (another compatible software): apt-get install dict With ''dico'' you can query for &lt;word&gt;: dico --host=dict.duckcorp.org &lt;word&gt; or with ''dict'': dict --host=dict.duckcorp.org &lt;word&gt; == Documentation == * generic documentation on [[wikipedia:Dict|DICT]] * [http://puszcza.gnu.org.ua/software/dico/manual/dico.html#SEC69 command line syntax for dico] == Technical Details == This service is made using: * [http://www.gnu.org/software/dico/ GNU Dico] * [http://www.djangoproject.com/ Django] 19b758faaf2e45f7ba696747766f3fb786911a1b 0 31 439 408 2014-03-24T12:51:00Z Duck 2 wikitext text/x-wiki <fdp_graph> graph DcMap { label = "DuckCorp Architecture"; fontsize = 13; overlap = false; splines = true; edge [fontsize=10.0]; style = bold; node [fontsize=10.0]; labelloc = "t"; internet [label="Internet", fontsize=14, shape=tripleoctagon]; hivane [label="Hivane\nNetwork", fontsize=14, shape=house]; hivane -- internet [label="Hivane\nTransit", style=dashed]; subgraph cluster_hq { label = "DuckCorp HQ (DuckLand)"; color = green; labeljust = "l"; elwing [label="Elwing", URL="DcArchitecture/Elwing"]; daneel [label="Daneel", URL="DcArchitecture/Daneel"]; earendil [label="Eärendil\n(DOWN)", URL="DcArchitecture/Eärendil"]; modem_dc [label="ADSL Modem", shape=box]; sw_dc [label="Switch", shape=box]; sw_dc -- {elwing earendil daneel}; elwing -- {modem_dc}; subgraph cluster_hurdfr { label = "HurdFr (DuckLand part)"; URL = "http://www.hurdfr.org/"; color = darkviolet; labeljust = "l"; amroth [label="Amroth\n(DOWN)", URL="DcArchitecture/Amroth"]; } amroth -- sw_dc; } cluster_hq -- hivane [label="Nerim / Hivane\nADSL", style=dashed]; subgraph cluster_alionis { label = "Alionis Suite\n(Villebon Datacenter)"; URL = "http://maps.google.com/maps/ms?ie=UTF8&hl=en&msa=0&msid=105368272885926046620.0004600d15bf1a76aa1a9&t=h&z=15"; color = black; labeljust = "l"; orfeo [label="Orfeo", URL="DcArchitecture/Orfeo"]; } cluster_alionis -- hivane [label="Hivane / Alionis\nPeering", style=dashed]; subgraph cluster_hivane_virtu { label = "Hivane Virtual Hosting"; color = orange; labeljust = "l"; toushirou [label="Tōshirō\n(VM)", URL="DcArchitecture/Tōshirō"]; jinta [label="Jinta\n(VM)", URL="DcArchitecture/Jinta"]; } cluster_hivane_virtu -- hivane [style=dashed]; subgraph cluster_nerim { label = "Nerim Suite\n(Equinix PA3 Datacenter)"; color = blue; labeljust = "l"; thorfinn [label="Thorfinn\n(Nerim Root VDS)", URL="DcArchitecture/Thorfinn"]; } cluster_nerim -- hivane [label="Nerim / Hivane\nPeering", style=dashed]; subgraph cluster_arnal { label = "Arnal's Lair\n(Japan)"; color = violet; labeljust = "l"; korutopi [label="Korutopi\n(LXC)", URL="DcArchitecture/Korutopi"]; } cluster_arnal -- internet [style=dashed]; } <fdp_graph> 0e8e99c165e40d1905c2d8d08b148ee3d69a1f67 0 33 442 407 2014-07-14T10:07:09Z Duck 2 /* List of Previous Contributions */ wikitext text/x-wiki DuckCorp is built and maintained by volunteers, mostly with their own money. The services are totaly free of charge for all users, but you may wish to contribute to help us keep it working well and improve. == How to Contribute ? == You can help us with: * sponsoring: if you can host a machine and/or provide connectivity * equipements: see the list of possible improvements below * money: you can send us money which will be used in the association: ** by check (see the duckcorp.org whois for Duck's postal address, or ask him by mail or IRC) ** by Paypal to duck@duckcorp.org == What can you Contribute ? == Here are ideas on which to contribute: * [[DcExpenses#Regular_Expenses|regular expenses]] * [???] buy a new machine, to provide: VMs, more services redondancy, ... (needed hardware not yet evaluated, more on this later) * [~120€] add a battery backup unit for Toushirou's 3ware card (for more data security, as datacenters tends to be less and less reliable) * [??? (quite expensive)] change Orfeo's backplane to have 4 disks slot instead of 2, and add 2 new disks (in a new RAID 1 array), planned at least 120GB capacity (2.5″ 10000 RPM SAS, like the other ones) (can be bought anywhere, but proprietary braquets needed) == List of Previous Contributions == Only pure financial contributions are listed here; equipments and sponsored purchases are listed on the [[DcExpenses|DuckCorp expenses page]]. {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Amount !! Donnor !! Comments |- | 2014-07-14 || 15€ || Clawfire || via paypal => ?€ |- | 2013-09-22 || 100$ USD || Damien || via Paypal => 69€ |- | 2011-01-10 || 500€ || AnonymousDonnor1 || |- | 2010-05-16 || 42€ || Chloé || |} Note: early contributions in the CoinNetwork project are not taken into account, as most information is lost. 9f2a8dea7f80559a3cb50310fae9b746efc8b9a1 443 442 2014-07-14T10:07:24Z Duck 2 wikitext text/x-wiki DuckCorp is built and maintained by volunteers, mostly with their own money. The services are totaly free of charge for all users, but you may wish to contribute to help us keep it working well and improve. == How to Contribute ? == You can help us with: * sponsoring: if you can host a machine and/or provide connectivity * equipements: see the list of possible improvements below * money: you can send us money which will be used in the association: ** by check (see the duckcorp.org whois for Duck's postal address, or ask him by mail or IRC) ** by Paypal to duck@duckcorp.org == What can you Contribute ? == Here are ideas on which to contribute: * [[DcExpenses#Regular_Expenses|regular expenses]] * [???] buy a new machine, to provide: VMs, more services redondancy, ... (needed hardware not yet evaluated, more on this later) * [~120€] add a battery backup unit for Toushirou's 3ware card (for more data security, as datacenters tends to be less and less reliable) * [??? (quite expensive)] change Orfeo's backplane to have 4 disks slot instead of 2, and add 2 new disks (in a new RAID 1 array), planned at least 120GB capacity (2.5″ 10000 RPM SAS, like the other ones) (can be bought anywhere, but proprietary braquets needed) == List of Previous Contributions == Only pure financial contributions are listed here; equipments and sponsored purchases are listed on the [[DcExpenses|DuckCorp expenses page]]. {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Amount !! Donnor !! Comments |- | 2014-07-14 || 15€ || Clawfire || via Paypal => ?€ |- | 2013-09-22 || 100$ USD || Damien || via Paypal => 69€ |- | 2011-01-10 || 500€ || AnonymousDonnor1 || |- | 2010-05-16 || 42€ || Chloé || |} Note: early contributions in the CoinNetwork project are not taken into account, as most information is lost. 09fbc8ab97bf982c38762a8cedf75d3f240f5c09 445 443 2014-07-14T10:15:06Z Duck 2 /* List of Previous Contributions */ wikitext text/x-wiki DuckCorp is built and maintained by volunteers, mostly with their own money. The services are totaly free of charge for all users, but you may wish to contribute to help us keep it working well and improve. == How to Contribute ? == You can help us with: * sponsoring: if you can host a machine and/or provide connectivity * equipements: see the list of possible improvements below * money: you can send us money which will be used in the association: ** by check (see the duckcorp.org whois for Duck's postal address, or ask him by mail or IRC) ** by Paypal to duck@duckcorp.org == What can you Contribute ? == Here are ideas on which to contribute: * [[DcExpenses#Regular_Expenses|regular expenses]] * [???] buy a new machine, to provide: VMs, more services redondancy, ... (needed hardware not yet evaluated, more on this later) * [~120€] add a battery backup unit for Toushirou's 3ware card (for more data security, as datacenters tends to be less and less reliable) * [??? (quite expensive)] change Orfeo's backplane to have 4 disks slot instead of 2, and add 2 new disks (in a new RAID 1 array), planned at least 120GB capacity (2.5″ 10000 RPM SAS, like the other ones) (can be bought anywhere, but proprietary braquets needed) == List of Previous Contributions == Only pure financial contributions are listed here; equipments and sponsored purchases are listed on the [[DcExpenses|DuckCorp expenses page]]. {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Amount !! Donnor !! Comments |- | 2014-07-14 || 15€ || Clawfire || via Paypal, commission paid by donnor |- | 2013-09-22 || 100$ USD || Damien || via Paypal => 69€ |- | 2011-01-10 || 500€ || AnonymousDonnor1 || |- | 2010-05-16 || 42€ || Chloé || |} Note: early contributions in the CoinNetwork project are not taken into account, as most information is lost. 4ed283974d0b09afbd95a5b4351e1d8523943ef0 455 445 2014-11-24T13:39:50Z Duck 2 /* List of Previous Contributions */ wikitext text/x-wiki DuckCorp is built and maintained by volunteers, mostly with their own money. The services are totaly free of charge for all users, but you may wish to contribute to help us keep it working well and improve. == How to Contribute ? == You can help us with: * sponsoring: if you can host a machine and/or provide connectivity * equipements: see the list of possible improvements below * money: you can send us money which will be used in the association: ** by check (see the duckcorp.org whois for Duck's postal address, or ask him by mail or IRC) ** by Paypal to duck@duckcorp.org == What can you Contribute ? == Here are ideas on which to contribute: * [[DcExpenses#Regular_Expenses|regular expenses]] * [???] buy a new machine, to provide: VMs, more services redondancy, ... (needed hardware not yet evaluated, more on this later) * [~120€] add a battery backup unit for Toushirou's 3ware card (for more data security, as datacenters tends to be less and less reliable) * [??? (quite expensive)] change Orfeo's backplane to have 4 disks slot instead of 2, and add 2 new disks (in a new RAID 1 array), planned at least 120GB capacity (2.5″ 10000 RPM SAS, like the other ones) (can be bought anywhere, but proprietary braquets needed) == List of Previous Contributions == Only pure financial contributions are listed here; equipments and sponsored purchases are listed on the [[DcExpenses|DuckCorp expenses page]]. {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Amount !! Donnor !! Comments |- | 2014-11-24 || 15€ || Clawfire || via Paypal, commission paid by donnor |- | 2014-07-14 || 15€ || Clawfire || via Paypal, commission paid by donnor |- | 2013-09-22 || 100$ USD || Damien || via Paypal => 69€ |- | 2011-01-10 || 500€ || AnonymousDonnor1 || |- | 2010-05-16 || 42€ || Chloé || |} Note: early contributions in the CoinNetwork project are not taken into account, as most information is lost. 92c96f17460389e53839ebc2502901ffb7977e81 0 32 444 404 2014-07-14T10:11:48Z Duck 2 /* Regular Expenses */ wikitext text/x-wiki Let's be transparent about money too. Pure financial contributions are not listed here, but in the [[DcDonation|donation page]]. == Regular Expenses == This does not account for external sponsorship, but contributions by members. {| class="wikitable" style="text-align: center; width: 100%;" ! Object !! Amount !! Sponsor !! Comments |- | DuckCorp DNS domain || ~7€/year (since 2014-07)<br/><del>~15€/year</del> || Duck |- | MilkyPond DNS domain || ~7€/year (since 2014-07)<br/><del>~15€/year</del> || Rtp |- | Toushirou's housing || 41.56€/month || Duck || collocation with Sam (considering network switch and APC powerswitch shared rack space) |} Note: this does not take into account the ADSL line used by Elwing and Daneel, coupled in the same offer providing the VM Thorfinn, as it is used privately. == Exceptional Expenses == Note: this does not take into account expenses before 2006 because most historical data were lost. Note: Elwing and Daneel are used privately. Elwing is not taken into account, as most services are not used for DC (and since begining of 2010 are moving progresively elsewhere), but Daneel is, as a big part of the backup is for DC's machines. === Improvement Expenses === {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Object !! Amount !! Sponsor !! Comments |- | 2012-05-09 || more memory for Toushirou (2*2GB) || ~60€ || Pilou || PC2-6400 instead of PC2-5300/5400 (see replacement memory details) |- | 2007-10 || replacement server (Orfeo-NG) || 1210€ || Duck || Sun Fire X4100 |- | 2007-05 || new server (Toushirou) || 1709.08€ || Duck || Supermicro PDSMI+ / Core 2 Duo E6600 / 2GB PC5400 / 3ware 9550SX4LP / 4x HD SATA II 250GB |} === Failure Expenses === {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Object !! Amount !! Sponsor !! Comments |- | 2010-05-22 || replacement memory for Toushirou (2*2GB) || 105€ || Duck || PC2-5300/5400 2*2GB memory in a correct brand could not be found anymore, so we had to take PC2-6400 instead |- | 2010-01-06 || spare disk || 73€ || Duck || avoided tragedy when both disks in Daneel died at one week interval |- | 2007-09-29 || replacement server (Daneel-ng) || 534.90€ || Duck || machine too old and previous disk died horribly |- | 2006-01 || 300GB HD for Daneel (backup) || || AnonymousDonnor1 || replaced since then |} === Other Expenses === {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Object !! Amount !! Sponsor !! Comments |- | 2010-06-29 || taxi || 26.20€ || Duck || Nerim bought Sivit, moving Toushirou to their new suite at Equinix PA3 (CBV->STD) |} b19143f8dc318d0062f74fd264ac4e58b3549c1c 454 444 2014-11-24T13:38:44Z Duck 2 /* Regular Expenses */ wikitext text/x-wiki Let's be transparent about money too. Pure financial contributions are not listed here, but in the [[DcDonation|donation page]]. == Regular Expenses == This does not account for external sponsorship, but contributions by members. {| class="wikitable" style="text-align: center; width: 100%;" ! Object !! Amount !! Sponsor !! Comments |- | DuckCorp DNS domain || ~7€/year (since 2014-07)<br/><del>~15€/year</del> || Duck |- | MilkyPond DNS domain || ~7€/year (since 2014-07)<br/><del>~15€/year</del> || Rtp |- | Toushirou's housing || 41.56€/month || Duck || collocation with Sam (considering network switch and APC powerswitch shared rack space) |} Note: this does not take into account the ADSL line used by Elwing and Daneel, <del>coupled in the same offer providing the VM Thorfinn</del>(now hosted by Hivane), as it is used privately. == Exceptional Expenses == Note: this does not take into account expenses before 2006 because most historical data were lost. Note: Elwing and Daneel are used privately. Elwing is not taken into account, as most services are not used for DC (and since begining of 2010 are moving progresively elsewhere), but Daneel is, as a big part of the backup is for DC's machines. === Improvement Expenses === {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Object !! Amount !! Sponsor !! Comments |- | 2012-05-09 || more memory for Toushirou (2*2GB) || ~60€ || Pilou || PC2-6400 instead of PC2-5300/5400 (see replacement memory details) |- | 2007-10 || replacement server (Orfeo-NG) || 1210€ || Duck || Sun Fire X4100 |- | 2007-05 || new server (Toushirou) || 1709.08€ || Duck || Supermicro PDSMI+ / Core 2 Duo E6600 / 2GB PC5400 / 3ware 9550SX4LP / 4x HD SATA II 250GB |} === Failure Expenses === {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Object !! Amount !! Sponsor !! Comments |- | 2010-05-22 || replacement memory for Toushirou (2*2GB) || 105€ || Duck || PC2-5300/5400 2*2GB memory in a correct brand could not be found anymore, so we had to take PC2-6400 instead |- | 2010-01-06 || spare disk || 73€ || Duck || avoided tragedy when both disks in Daneel died at one week interval |- | 2007-09-29 || replacement server (Daneel-ng) || 534.90€ || Duck || machine too old and previous disk died horribly |- | 2006-01 || 300GB HD for Daneel (backup) || || AnonymousDonnor1 || replaced since then |} === Other Expenses === {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Object !! Amount !! Sponsor !! Comments |- | 2010-06-29 || taxi || 26.20€ || Duck || Nerim bought Sivit, moving Toushirou to their new suite at Equinix PA3 (CBV->STD) |} 0f121c018d92ff20ef625d299067422df6c0c9d9 0 47 447 168 2014-10-07T14:52:30Z Duck 2 /* Fallback administrators */ wikitext text/x-wiki Here is the list of '''current''' DuckCorp's administrators. These are the only people which have full access to the system (even if we may delegate nonsensitive things to trusted parties, but you'll always be warned of such changes). == Active administrators == * Duck: *: Full Name: Marc Dequènes *: GPG Key Fingerprint: 6ADD 5093 AC6D 1072 C912 9000 B1CC D972 9026 7086 == Fallback administrators == * Arnau: *: Full Name: Arnaud Fontaine *: GPG Key Fingerprint: 43B5 1C2A AAD3 E0D4 9ACF 8F59 97C2 C6AB 313C 7B03 *: (old: D792 B8A5 A567 B001 C342 2613 BDF2 A220 5E36 19D3) * Pilou: *: Full Name: Pierre-Louis Bonicoli *: GPG Key Fingerprint: 2B1E DB5E ABEB 0483 AA50 15B3 13FA 63E9 3F25 BB1F 7a67a508ac1d1b13e5a167a145432b8948ec3c7e 448 447 2014-10-07T14:56:17Z Duck 2 /* Active administrators */ wikitext text/x-wiki Here is the list of '''current''' DuckCorp's administrators. These are the only people which have full access to the system (even if we may delegate nonsensitive things to trusted parties, but you'll always be warned of such changes). == Active administrators == * Duck: *: Full Name: Marc Dequènes *: GPG Key Fingerprint: 7297 2A83 E526 453D F288 5F81 55E9 F9F7 AC1C 443F *: (old: 6ADD 5093 AC6D 1072 C912 9000 B1CC D972 9026 7086) == Fallback administrators == * Arnau: *: Full Name: Arnaud Fontaine *: GPG Key Fingerprint: 43B5 1C2A AAD3 E0D4 9ACF 8F59 97C2 C6AB 313C 7B03 *: (old: D792 B8A5 A567 B001 C342 2613 BDF2 A220 5E36 19D3) * Pilou: *: Full Name: Pierre-Louis Bonicoli *: GPG Key Fingerprint: 2B1E DB5E ABEB 0483 AA50 15B3 13FA 63E9 3F25 BB1F b588b781671dc0025572e63cbbeb8e71c82a1659 6 45 449 167 2014-10-21T10:09:49Z Duck 2 Duck uploaded a new version of &quot;[[File:Duckcorp.crt]]&quot;: rollover wikitext text/x-wiki DuckCorp's Certificate Authority Certificate 96073ec9125a4b0e24a9a3cfb940f10c41ec9a37 6 72 450 2014-10-21T10:10:52Z Duck 2 signed CA wikitext text/x-wiki signed CA adba90fb74edde0f7db4fff29557876fddc52daa 6 73 451 2014-10-21T10:10:59Z Duck 2 signed CA wikitext text/x-wiki signed CA adba90fb74edde0f7db4fff29557876fddc52daa 6 74 452 2014-10-21T10:11:09Z Duck 2 signed CA wikitext text/x-wiki signed CA adba90fb74edde0f7db4fff29557876fddc52daa 0 46 453 406 2014-10-21T10:19:00Z Duck 2 /* TLS/SSL-based Services */ wikitext text/x-wiki == Introduction == '''All''' services containing sensitive information are protected using cryptography. Whenever possible, we add the necessary configuration to ensure unsecure usages are not possible, to protect your data. Nevertheless, a few things are needed on your side to improve security, that's why we are providing the following notes in order to help you configure your software in a secure fashion. == Areas of Security == === Mails from DC's Administrators === You should not trust mails pretenting to come from us. The only way to be sure a mail is from someone, is to agree on exchanging cryptographically-protected messages. On [[Admins|this page]] you'll find the list of DC's administrators from which you may receive mails (on the users's mailing-list for example). You could trust their GPG keys directly, but that would not be secure at all. The best way is to meet, live, in a [[wikipedia:Key_signing_party|key signing party]]. If a friend has already signed our key, and is not too far from you, you may also propagate your trust to our keys. Once done, you'll be sure what seems to come from us is really from us. === Talking to the Right Machine/Service === All remote services use an address on the internet, like ''superservice.duckcorp.org'', but if you are connected through an untrusted network (like if you're using a third-party's WIFI), you cannot be sure you'll be connecting to the right machine, and you may disclose important information like your credentials. ==== TLS/SSL-based Services ==== To ensure you're talking to the right server, and noone pretend to be a DC's server to tricks you, you need to install the following certificate ([[File:Duckcorp.crt]], which was signed by Arnau [[File:Arnau duckcorp.crt.asc]], Pilou [[File:Pilou duckcorp.crt.asc]] and Duck [[File:Duck duckcorp.crt.asc]]): * either in your software configuration (for example, to validate HTTP site in your browser, clicking on the link should ask for installation, and you'll just need to confirm you trust it) ** For Firefox you must manually import the certificate ([http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=316436 #316436]): Preferences -> Advanced -> Certificates -> View Certificates -> Authorities -> Import. ** For Chromium too, you must manually import the certificate: Settings -> Show advanced settings -> Manage certificates -> Authorities -> Import. * or globally on your host by installing the certificate, as root: ** (method 1, prefered) in ''/usr/local/share/ca-certificates'', and running ''update-ca-certificates'' (the ''ca-certificates'' package needs to be installed) ** (method 2, not suitable for GNUTLS-based apps) in ''/etc/ssl/certs'', and running ''c_rehash'' (the ''openssl'' package needs to be installed) ==== Service Locator Security ==== One possible attack is to alter replies from the machine locator service (DNS) in order to redirect your communication to a nasty machine. Since November 2010, ''duckcorp.org'' and ''milkypond.org'' domains are cryptographically signed using the DNSSEC system, so you are now able to verify the address returned for the service is the right one. This system is not new, but has recently switched into production, so your operating system may not yet be properly configured to use this protection. Until it is pre-configured in most of them, you may configure it yourself using [[Services/DNS#How_to_test_my_zone_is_secured.3F|this procedure]]. {{warning}} Beware this protection solves certains security problems but is not sufficient to ensure you're talking to the right machine/service. Nevertheless it ensures: * the address of the machine/service is the right one * information related to the domain, list of mail servers, security information on hosts (SSHFP)… are not tampered Using this security plus certificate verification (see [[Services/Security#TLS.2FSSL-based_Services|section about TLS/SSL-based Security]]) would ensure full security. === Secure SSH Connections === In order not to be tricked connecting to a fake server, or to a rooted server (just in case), it is possible to check the SSH key of the server. As this verification is quite boring both for administrators and users, almost nobody on earth does it. Fortunately, it is possible to publish this information in the DNS and have OpenSSH check it for you automatically. To add this security, you can edit your system configuration (''/etc/ssh/ssh_config'') or your personal one (''~/.ssh/config''), and add the folowing: Host * VerifyHostKeyDNS ask Of course, the DNS replies may be altered, so if you want full security, read the [[Services/Security#Service_Locator_Security|section about Service Locator Security]]. 50895dd42ec387d1347900acf7fd70e2e3adcff8 459 453 2015-06-22T13:40:55Z Duck 2 /* TLS/SSL-based Services */ wikitext text/x-wiki == Introduction == '''All''' services containing sensitive information are protected using cryptography. Whenever possible, we add the necessary configuration to ensure unsecure usages are not possible, to protect your data. Nevertheless, a few things are needed on your side to improve security, that's why we are providing the following notes in order to help you configure your software in a secure fashion. == Areas of Security == === Mails from DC's Administrators === You should not trust mails pretenting to come from us. The only way to be sure a mail is from someone, is to agree on exchanging cryptographically-protected messages. On [[Admins|this page]] you'll find the list of DC's administrators from which you may receive mails (on the users's mailing-list for example). You could trust their GPG keys directly, but that would not be secure at all. The best way is to meet, live, in a [[wikipedia:Key_signing_party|key signing party]]. If a friend has already signed our key, and is not too far from you, you may also propagate your trust to our keys. Once done, you'll be sure what seems to come from us is really from us. === Talking to the Right Machine/Service === All remote services use an address on the internet, like ''superservice.duckcorp.org'', but if you are connected through an untrusted network (like if you're using a third-party's WIFI), you cannot be sure you'll be connecting to the right machine, and you may disclose important information like your credentials. ==== TLS/SSL-based Services ==== To ensure you're talking to the right server, and noone pretend to be a DC's server to tricks you, you need to install the following certificate ([[File:Duckcorp.crt]], which was signed by Arnau [[File:Arnau duckcorp.crt.asc]], Pilou [[File:Pilou duckcorp.crt.asc]] and Duck [[File:Duck duckcorp.crt.asc]]): * either in your software configuration (for example, to validate HTTP site in your browser, clicking on the link should ask for installation, and you'll just need to confirm you trust it) ** For Firefox you must manually import the certificate ([http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=316436 #316436]): Preferences -> Advanced -> Certificates -> View Certificates -> Authorities -> Import. ** For Chromium too, you must manually import the certificate: Settings -> Show advanced settings -> Manage certificates -> Authorities -> Import. * or globally on your host by installing the certificate, as root: ** (method 1, prefered) in ''/usr/local/share/ca-certificates'', and running ''update-ca-certificates'' (the ''ca-certificates'' package needs to be installed) ** (method 2, not suitable for GNUTLS-based apps) in ''/etc/ssl/certs'', and running ''c_rehash'' (the ''openssl'' package needs to be installed) The certificate and signatures can also be downloaded from the following link (without SSL): http://ca.duckcorp.org/ ==== Service Locator Security ==== One possible attack is to alter replies from the machine locator service (DNS) in order to redirect your communication to a nasty machine. Since November 2010, ''duckcorp.org'' and ''milkypond.org'' domains are cryptographically signed using the DNSSEC system, so you are now able to verify the address returned for the service is the right one. This system is not new, but has recently switched into production, so your operating system may not yet be properly configured to use this protection. Until it is pre-configured in most of them, you may configure it yourself using [[Services/DNS#How_to_test_my_zone_is_secured.3F|this procedure]]. {{warning}} Beware this protection solves certains security problems but is not sufficient to ensure you're talking to the right machine/service. Nevertheless it ensures: * the address of the machine/service is the right one * information related to the domain, list of mail servers, security information on hosts (SSHFP)… are not tampered Using this security plus certificate verification (see [[Services/Security#TLS.2FSSL-based_Services|section about TLS/SSL-based Security]]) would ensure full security. === Secure SSH Connections === In order not to be tricked connecting to a fake server, or to a rooted server (just in case), it is possible to check the SSH key of the server. As this verification is quite boring both for administrators and users, almost nobody on earth does it. Fortunately, it is possible to publish this information in the DNS and have OpenSSH check it for you automatically. To add this security, you can edit your system configuration (''/etc/ssh/ssh_config'') or your personal one (''~/.ssh/config''), and add the folowing: Host * VerifyHostKeyDNS ask Of course, the DNS replies may be altered, so if you want full security, read the [[Services/Security#Service_Locator_Security|section about Service Locator Security]]. 4d7329a525a313ea3a5c95736de16f862d4387d6 0 75 456 2014-11-24T18:10:42Z Pilou 7 Create page wikitext text/x-wiki {{Template:Service | description = A few VCS tools are available to DC users. | prerequisite = Write access is currently limited to people having a shell account. No prerequisite for read access. | account = global-reg | ipv6 = true | security_notes = This service is secure. }} == Access == Use the following URL: https://rcs.duckcorp.org/ === Git === * Direct SSH access: <tt>ssh://login@vcs.duckcorp.org/srv/vcs/git/...</tt> * [https://vcs-git.duckcorp.org/ Git via HTTP (read-only)] * Git via Git protocol using <tt>git://vcs-git.duckcorp.org/...</tt> to access <tt>/vcs/git/...</tt> * [https://vcs-git-viewer.duckcorp.org/ Git browser] cc3aba647a851f54ca1ca14eb80084b124ae3136 0 76 457 2015-02-18T02:42:45Z Pilou 7 Create page wikitext text/x-wiki {{Template:Service | description = Available services: * a node on the Jabber network, based on XMPP, the open standard for instant messaging. | prerequisite = None | account = global-reg | ipv6 = true | security_notes = }} == Access == * Domain: milkypond.org * TCP port for client connections: 5222 * Host: jabber.milkypond.org (Orfeo.duckcorp.org) The daemon listens on other TCP ports: * 5269 (server to server connections) * 5280 ([http://en.wikipedia.org/wiki/BOSH BOSH] http) * 5281 ([http://en.wikipedia.org/wiki/BOSH BOSH] https) == Features == MUC (multi-user chat) is available. ac8cf86d783df4c8460cb7485be49692905b538c 0 49 458 375 2015-05-20T05:34:53Z Arnau 8 wikitext text/x-wiki {{Template:Service | description = Available services: * multiple email addresses (mailboxes+aliases or redirections) based on the ''milkypond.org'' (or maybe ''duckcorp.org'') domain * roaming accounts to be able to send emails wherever you are If you want email addresses using you own domain(s), see the [[Services/MailHosting|mail hosting service]]. | prerequisite = | account = global-reg | ipv6 = true | security_notes = Access to the mail services are fully secured, and to your data, nevertheless most mail exchange on the Internet are not. Complete security can be achieved using signed and encrypted mail (see [[wikipedia:Pretty_Good_Privacy|OpenPGP]] and [[wikipedia:S/MIME|S/MIME]]) }} == Access == === Using a Mail Reader === You can retrieve your mails, in case of a real mailbox, using either: * IMAP+TLS (TCP 143) / IMAPS (TCP 993) on imap.duckcorp.org * or POP3+TLS (TCP 110) / POP3S (TCP 995) on pop.duckcorp.org The IMAP protocol is recommended over POP3, as it provides many interesting features. If you want to download all your mails absolutely at home, loosing the ability to read your mail from anywhere on the planet, you can do that with IMAP too (look at your mail client settings). You can use our servers to send mails out too via smtp.duckcorp.org using: * SMTP+TLS (TCP 25) / SMTPS (TCP 465) * and SASL authentication === Using a Web Interface === Several [https://webmail.duckcorp.org/ webmail interfaces] are available. == Antivirus and Antispam == Mails stored on our server are checked upon arrival for viruses and SPAMs. Mail redirected to a third party mailbox are not, not to mess with the strategy of the the final destination (which could arm learning greatly). Mails being viruses are suppressed automatically upon arrival. Once in a week, an extra antivirus check is done on all hosted mailboxes, to remove viruses not detected at the time it arrived (our antivirus database is updated daily), so you may see such mail disappear from your mailbox, don't fear. SPAMs are more difficult to detect, and it is an error-prone process, so we chose to use a learning software instead of using a global database. On the bright side of things, you would never loose mails and the software should be able to learn what is a SPAM from '''your''' point of view (which has proved to differ slightly between our users), but on the grey side you will have to teach him regularly to avoid errors. When your account is created, it acts like an empty headed body letting everything through, but after a few weeks of teaching it is able to recognize most of your habits and block a lot of annoying SPAM. === Web Interface === The web interface is an easy way to view your mail history, changes your settings, and more. It is available using this URL: https://spamfilter.duckcorp.org/ ==== User Settings ==== You can yourself setup a few parameters in the ''Preferences'' page of the [https://spamfilter.duckcorp.org/ web interface], mostly: * how the system should train: ** TEFT (''On every new message scanned by the filter''): useful to learn very quickly especially on a new mailbox or when you've got tons of spam on your addresses, but you need to train it regulary (daily is better) or it will learn wrong (very quickly too !) ** TOE (''Only when the filter makes a mistake''): slow learning, but if you don't have time for training very often or go on long holidays without internet access this mode will give you a stable behavior ** TUM (''Only with new data or if the filter makes a mistake''): trade-off between the two previous modes, learn quite fast and not too demanding, adapts better to new SPAMs then TOE * filter sensitivity: you can ask the system to be more or less aggressive * message handling: see [[#Delivery Mode|delivery mode]] below * ''Disable DSPAM filtering'': you may switch off filtering at your own risk We strongly recommend using TEFT with daily training for a few weeks then switching to TUM. If you need to go away for a long time, switching to TOE is recommended. Using the quarantine feature is also a safe choice, as the web interface is quite easy to use. === Delivery Mode === ==== Quarantine ==== With the ''message handling'' setting set to ''Quarantine the message'' (see [[#User Settings|user preferences]]), then your SPAMs will not go into your mailbox but stay in this stagging area. These mails are kept by the system until you decide their fate. Through the ''Quarantine'' page of the web interface, you can list these mails and: * free legitimate mails wrongly considered as SPAM by the system * delete real SPAMs if the system was right about them (freeing useful space) In this mode, you need to flush your quarantine once in a while. ==== Delivered with Special Header (default, recommended) ==== With the ''message handling'' setting set to ''Deliver the message normally with a X-DSPAM-Result header'', mails are delivered normally, but with a special field added to your mail headers (not always visible depending on your mail client and its configuration). This is quite handy if you prefer SPAMs arranged in a specific folder. You may use then the provided [[#Mail Filtering |filtering system]] to sort them properly, or configure your eMail client. ==== Delivered with Modified Subject (not recommended) ==== With the ''message handling'' setting set to ''Tag the Subject header with'', mails are delivered normally, but with a modified title to alert you this is a SPAM (which is a tad ugly). This mode is really not clean and not recommended, but it exist for historical purposes, so you might still use it if you really wish to. === Retraining === Teaching the system what is SPAM and HAM (non-SPAM) is called ''retraining''. ==== Retraining using the Special ''Junk'' Folder (default, recommended) ==== If you have of create a folder named ''Junk'', then it is automatically magic: * if you drop mail into it, it is automatically retrained as SPAM * if you move it out of it, it is automatically retrained as HAM * with time, certain old mails automatically expire, see below To use this folder properly, SPAMs '''must''' be delivered in the ''Junk'' folder automatically, so you can move them out in case of error. If using the default settings, you just need to subscribe to this folder in your mail software (this folder is always auto-created). If you are using different setting, you need to select the [[#Delivered with Special Header|delivery mode using a special header]], and use the provided [[#Mail Filtering|filtering system]] to drop them in the ''Junk'' folder ('''Do not use your mail software for this filtering, this is horribly inefficient and might alter the learning badly'''). Automatic expiration logic, based on delivery time (and not the mail timestamp): * deleted mails are purged after 1 day * read mails without an important flag are purge after 7 days * unread mails without an important flag are purge after 30 days If you use the ''incoming_spam'' [[#Global_Rules|global rule]], then SPAMs newly discovered by the system are flagged as important, which means these mails will never by purged until you review it and decide to delete them or mark them as not important. Custom rules might play with this flag and achieve an automatic selection. ==== Retraining via Web Interface ==== Use the [https://spamfilter.duckcorp.org/ web interface] to retrain from errors in the ''History'' page. If you are using the ''quarantine'', then freed mails will automatically be retrained as HAM. ==== Retraining via Mail ==== Resend SPAMs to [mailto:dc-spam@duckcorp.org dc-spam@duckcorp.org] and HAM (non-SPAM) to [mailto:dc-ham@duckcorp.org dc-ham@duckcorp.org]. {{warning}} PLEASE TAKE CARE to use the ''resend'' function of your mailer and never use ''forward'', which would result in '''yourself''' being considered as SPAM or HAM. == Mail Filtering == With your favourite mail client, you can probably filter your mails in proper folders already. Nevertheless, this can be an annoying operation: * blocking you mail client for a long time if you have to process plenty of mails * downloading each mail information, and sometimes content (depending on your filters), is lenghty too, and cost much bandwidth * syncing filters across your machines (home desktop, laptop, office machine…) is a pain in the ass * processing only when you're online prevents triggering actions in a timely manner (automatic redirect, vacation messages…), and running a machine 24/7 with a mail client polling new mails every 30s is not a solution We provide a much better way to do this using the [[wikipedia:Sieve_(mail_filtering_language)|SIEVE]] filters. Shortly, SIEVE is a language dedicated to expressing mail filters (also called ''rules''). Our server is able to process your mails according to these filters as soon as they arrive. You then don't have to care about them anymore, and may use light mail clients or webmails when you're not on your machine with your favourite software. === Rules Configuration === You can express sort/reject/vacation/… filters using these rules, as the capabilities are very rich. Several softwares support managing SIEVE rules: * Icedove/Thunderbird: *: using the SIEVE extension (in ''xul-ext-sieve'' Debian package), it provides a rules editor (for power-users) * Horde (Ingo): *: provides an easy to use web interface *: this webmail has been made available [https://webdesk.duckcorp.org/ here] * Squirrelmail: *: coupled with the Avelsieve extension, provides an easy to use web interface *: this webmail has been made available [https://webmail-sm.duckcorp.org/ here] * Roundcube: *: coupled with the sieverules extension, provides an easy to use web interface *: this webmail has been made available [https://webmail-rc.duckcorp.org/ here] * sieve-connect: *: provides a CLI to upload/download/activate your rules files *: this tool is available on [[Services/Shell|shell hosts]] (tell us if you know more software supporting this feature) To push your filters on the server, a dedicated protocol exists: MANAGESIEVE (TCP 4190) on ''sieve.duckcorp.org''. Our webmails are already configured to use it, but it you use sieve-connect from our hosts or your own mail software, you'll need these parameters. You can read more info about SIEVE here: * supported SIEVE features on our server: http://pigeonhole.dovecot.org/ * http://www.fastmail.fm/docs/sieve/ * http://sieve.info/ === Default Rules === The default settings (since 2112-02-11) are to use the global ''incoming_spam'' rule and the [[#Delivered with Special Header|delivery using a special header]], in order to provide a simple default configuration for most users. All other mails will end-up in your ''Inbox'' folder and you may then sort them by yourself. If you create your own rules, the default rules won't apply anymore, so power-users can replace the default behavior completely to achieve what they really need. === Global Rules === Global rules are provided to ease configuration on specific filters. They can easily be included in your own configuration. Available rules: * ''incoming_spam'': *: SPAMs will automatically be delivered in the ''Junk'' folder and marked as ''important'' *: you need to use the [[#Delivered with Special Header|delivery using a special header]] for this rule to have any effect If you write your own custom rules, here is an example on how to use one of them: require ["include"]; include :global "&lt;rule-name&gt;"; == Fetching eMails from an External Mailbox == {{todo}} == Shared/Public Folders == You may need to share mails or messages with friends or people you do stuff with (in a project or association). Depending on your needs, two solutions are possible: * share some of your own private folders, thus called ''shared folders'' * manage a special folder hierarchy, called ''public folders'' (even if they may not be accessible to everyone) *: if you need one, ask an administrator; the namespace name can be freely chosen but must be unambiguous and is subject to approval === Namespaces === Through IMAP, or our webmails internally using IMAP, it is possible to partition the folder hierarchy into ''namespaces''. Traditionally you are using the root namespace for your private folders. Additional namespaces can be created and will appear among your own folders or separate, depending on your mail client's choice of representation. To avoid name clashes, we decided to prefix all additional namespace names with a '''#'''. Since 2011-05-14, the following extra namespaces are created and reserved: * #Shared, containing all folders other users decided to share with you * #MilkyPond, containing public MP/DC informational mailboxes you may subscribe at will === Folders Permissions === Using IMAP, it is possible to setup rights (read only, write allowed…) to your own folders in order to share them with other users, or group of users. Public folders are owned by no-one, and must be created by the administrators. Once your request is accepted we will delegate its administration to your care. It can then can be managed like shared folders. === Software Support === Client mail softwares support: * Horde: *: support namespaces, shared folders configurable via ''Options->Share Folders'' menu but no ACLs for public folders * RoundCube: *: support namespaces, shared and public folders configurable via ''Settings->Folders'', selecting a folder then using the ''Sharing'' tab * Icedove/Thunderbird: *: support namespaces, shared and public folders configurable via folder selection and ''Tools->Imap-ACL'' menu action Most other softwares have namespace support only, so you should be able to use shared/public folders you have rights on but not configure them yourself (tell us if you know more software supporting this feature). == Limitations == === Maximum Mail Size === Mail you send or receive are limited to '''10MB'''. If you need to transmit much bigger data, then a mail transport is not appropriate, you'd better use a file sharing method instead. === Quotas === Even if it would be nice to live without it, we had to establish quotas to force people sort their mails out once in a while and delete useless things instead of leaving an ever-growing mess behind. The default quota is '''512MB''' which is not that big but should match needs of most users. This said, you may ask us for more and there's no reason we would refuse a reasonable demand. == Technical Details == This service is made using: * [http://www.postfix.org/ Postfix] * [http://dovecot.org/ Dovecot] * [http://dspam.sourceforge.net DSPAM] * [http://johannes.sipsolutions.net/Projects/dovecot-antispam dovecot-antispam] * [https://projects.duckcorp.org/projects/spoolinger Spoolinger] * [http://www.horde.org/ Horde] * [http://www.squirrelmail.org/ SquirrelMail] * [http://www.roundcube.net/ RoundCube] e2d6d8acf87ac270280120ec4a82dedfba47c323 0 70 460 412 2017-01-22T14:06:25Z Duck 2 wikitext text/x-wiki {{Template:Service | description = Automatically find a changing (dynamic) IP address (home address for example) using this service. | prerequisite = | account = local | ipv6 = true | security_notes = This service is secured using TLS, web certificates and a specific account (separate from your main account). }} == Access == To use this service, ask for an account to an administrator. For each IP you need to track, you should provide with (explanations follows): * secondary account suffix (characters allowed: letters, numbers) * hostname suffix (characters allowed: letters, numbers, dash) The secondary account prefix is used to create your secondary account name, based on your main account name. If your main account is called ''toto'' and the secondary account prefix is called ''home'', then the secondary account name would be ''toto-home''. It is used as service username in the configuration, and along with a password, identify yourself as owner of the DNS entry. The hostname prefix is used to create the DNS entry for your host. If you use ''house'' as prefix, then the DNS entry would be ''toto-house.ddns.duckcorp.org''. It is possible to have multiple DNS names associated with the same account. So you could have another prefix ''manor'' and the additional DNS entry would be ''toto-manor.ddns.duckcorp.org''. === Installation on Debian === Currently the software is not packaged, so a few manual steps are needed. Install the dependencies: apt-get install kwalify ruby-curb ruby-safe-yaml ruby-log4r Install the Software: cd /opt git clone https://vcs-git.duckcorp.org/duckcorp/ddns.git cd ddns ruby setup.rb config --bindir=bin --rbdir=lib --datadir=data --sysconfdir=conf --localstatedir=var --shebang=never ruby setup.rb setup dir -p conf/ddns var/log/ddns === Configuration on Debian === Create ''/opt/ddns/conf/ddns/myip.conf'' containing: --- url: "https://myip.duckcorp.org/" timeout: 3 Create ''/opt/ddns/conf/ddns/client.conf'' containing: --- log: path: "./var/log/ddns/" regip: url: "https://ddns.duckcorp.org/" user: <secondary-account-name> passwd: <secondary-account-password> timeout: 3 profiles: <dns-entry>: ipv4: auto ipv6: auto and replace fields into angle brackets using your own credentials and DNS info. The ''profiles'' block can hold as many DNS entries as you need; they may not be on the same site though. You can find more information on the various configuration parameters on the [https://projects.duckcorp.org/projects/ddns/wiki/Configuration#RegIP-client-ddns-client DDNS project wiki]. == Technical Details == This service is made using: * [https://projects.duckcorp.org/projects/ddns DDNS] da7c7b29d8fb5c6ece2e7892dfa5dfec1cabcadf 0 39 463 462 2017-01-22T14:22:02Z Duck 2 wikitext text/x-wiki Here is a short overview of the services provided by DuckCorp. Our services are supervised and important data are [[Services/Backup|saved regularly]]. {{warning}} [[Services/Security|Notes about security !]] {| class="wikitable" style="text-align: center; width: 100%;" |+ Available Services |- ! Category !! colspan="2" | Service !! Access !! Status !! Description |- | Entertainment || colspan="2" | [[Games/Minetest|Minetest]] || public/users || {{status_ok}} || style="text-align: left;" | Minecraft-like game |- | rowspan="8" | Communication || rowspan="2" | Mail || [[Services/Mail|eMails]] || users || {{status_ok}} || style="text-align: left;" | Mail boxes with anti-spam/anti-virus, filtering…, or mail redirections |- | [[Services/ML|Mailing-Lists]] || users || {{status_ok}} || style="text-align: left;" | Distribution lists for mails |- | rowspan="3" | IRC || [[Services/IRC|IRC Network]] || public || {{status_ok}} || style="text-align: left;" | MilkyPond Chat Network using a dedicated software or a Web-interface |- | [[Services/IRC-Bouncer|IRC Bouncer]] || users || {{status_ok}} || style="text-align: left;" | IRC proxy (IRC server relaying IRC communications, keeping connections open and remembering logs) |- | [[Services/IRC-IM-GW|IRC to IM gateway]] || users || {{status_ok}} || style="text-align: left;" | Communication to multiple instant messaging networks through a unified IRC-like interface |- | rowspan="2" | XMPP (Jabber) || [[Services/XMPP|XMPP Network]] || users || {{status_ok}} || style="text-align: left;" | Global Chat Network (inter-communication between many [[wikipedia:Xmpp#History|well-known public IM services]]) |- | [[Services/XMPP WebGW|XMPP WebChat]] || users || {{status_down}} || style="text-align: left;" | Social Platform |- | colspan="2" | [[Services/Tribioune|Triboune Libre]] || public || {{status_down}} || style="text-align: left;" | MilkyPond Web-chat system inspired by [http://linuxfr.org/board the famous one] on [http://linuxfr.org/ Linuxfr.org] |- | rowspan="5" | Sharing || colspan="2" | [[Services/Gallery|Media Gallery]] || public/users || {{status_ok}} || style="text-align: left;" | Photo and video gallery |- | colspan="2" | [[Services/Wiki|Wiki]] || public/users || {{status_ok}} || style="text-align: left;" | Documentation, technical knowledge, useful tips… |- | colspan="2" | [[Services/OwnCloud|OwnCloud]] || public/users || {{status_ok}} || style="text-align: left;" | Personal data store (contacts, calendars, files…) with syncing/sharing capabilities |- | rowspan="2" | Generic || [[Services/FTP|File Repository]] || public/users || {{status_ok}} || style="text-align: left;" | Generic file sharing system (using FTP) |- | [[Services/SAFT|Shell Transfer]] || trusted || {{status_ok}} || style="text-align: left;" | File transfer system using the SAFT protocol (shell access needed) |- | rowspan="3" | Utilities || colspan="2" | [[Services/WebFeeds|News WebReader]] || users || {{status_ok}} || style="text-align: left;" | News feeds reader through a web interface |- | colspan="2" | [[Services/NTP|Time Server]] || public || {{status_ok}} || style="text-align: left;" | System used to automatically setup time on your machines |- | colspan="2" | [[Services/Dico|Dictionary Server]] || public || {{status_ok}} || style="text-align: left;" | Words searching system via a dedicated software (using the DICT protocol) or a Web-interface |- | rowspan="6" | Development || colspan="2" | [[Services/Projects|Project Management & Issue Tracking]] || public/users || {{status_ok}} || style="text-align: left;" | Tool intended to help organize projects |- | rowspan="2" | Code || [[Services/VCS|VCS]] || public/users || {{status_ok}} || style="text-align: left;" | Code/configuration versioning tools (Git, SVN, Baz, Bzr…) |- | [[Services/CodeReview|Code Review]] || public/users || {{status_down}} || style="text-align: left;" | Tool intended to help improve software quality |- | rowspan="2" | Databases || [[Services/SQL|SQL]] || users || {{status_ok}} || style="text-align: left;" | SQL server (PostgreSQL or MySQL) |- | [[Services/LDAP|LDAP]] || users || {{status_ok}} || style="text-align: left;" | LDAP server (OpenLDAP) |- | colspan="2" | [[Services/SoftwareRepository|Software Repository]] || public/users || {{status_ok}} || style="text-align: left;" | Software repository, to provide custom packages (think Debian debs) or installation media (thinks DVDs) |- | rowspan="7" | Hosting || rowspan="2" | Hostnames Directory || [[Services/DNS|DNS]] || users || {{status_ok}} || style="text-align: left;" | Domain Name System (NS1/NS2, DNSSEC…) |- | [[Services/DDNS|Dynamic DNS]] || users || {{status_ok}} || style="text-align: left;" | Dynamic DNS entries, for places where IPs are dynamic and not under your control |- | rowspan="2" | Mail || [[Services/MailHosting|Mail Domains]] || users || {{status_ok}} || style="text-align: left;" | Mail hosting (MX1/MX2) |- | [[Services/MLHosting|Mailing-Lists]] || users || {{status_ok}} || style="text-align: left;" | Distribution lists for mail domains |- | colspan="2" | [[Services/WebHosting|Web Sites/Applications]] || users || {{status_ok}} || style="text-align: left;" | Web pages using HTML/XHTML, CSS, JS, and various server-side programming languages (SSI, PHP, Perl, Python, Ruby…), and statistics (analytics data/reports) |- | colspan="2" | [[Services/XMPPHosting|XMPP Domains]] || users || {{status_ok}} || style="text-align: left;" | XMPP Node for a custom domain |- | colspan="2" | [[Services/Shell|Shell]] || trusted || {{status_ok}} || style="text-align: left;" | Useful for website administration, development, run custom scripts, persistent applications for text-mode geeks… |- | rowspan="2" | Network || colspan="2" | [[Services/IPv6-Broker|IPv6 tunnels]] || users || {{status_down}} || style="text-align: left;" | Access to the IPv6 world through an IPv4 connection |- | colspan="2" | [[Services/NSTX|NSTX]] || users || {{status_ok}} || style="text-align: left;" | Access to the Internet through a restricted WIFI connection (via an IP over DNS tunnel) |} == TODO == * in Services/Wiki: https://wiki.duckcorp.org/ * in Services/Shell: link to SAFT * in Services/VCS: https://vcs.duckcorp.org/ * Radio … 22ed308073e7214996c7105664773c21ba9bf27a 466 463 2017-06-25T12:01:50Z Duck 2 NSTX is obsolete wikitext text/x-wiki Here is a short overview of the services provided by DuckCorp. Our services are supervised and important data are [[Services/Backup|saved regularly]]. {{warning}} [[Services/Security|Notes about security !]] {| class="wikitable" style="text-align: center; width: 100%;" |+ Available Services |- ! Category !! colspan="2" | Service !! Access !! Status !! Description |- | Entertainment || colspan="2" | [[Games/Minetest|Minetest]] || public/users || {{status_ok}} || style="text-align: left;" | Minecraft-like game |- | rowspan="8" | Communication || rowspan="2" | Mail || [[Services/Mail|eMails]] || users || {{status_ok}} || style="text-align: left;" | Mail boxes with anti-spam/anti-virus, filtering…, or mail redirections |- | [[Services/ML|Mailing-Lists]] || users || {{status_ok}} || style="text-align: left;" | Distribution lists for mails |- | rowspan="3" | IRC || [[Services/IRC|IRC Network]] || public || {{status_ok}} || style="text-align: left;" | MilkyPond Chat Network using a dedicated software or a Web-interface |- | [[Services/IRC-Bouncer|IRC Bouncer]] || users || {{status_ok}} || style="text-align: left;" | IRC proxy (IRC server relaying IRC communications, keeping connections open and remembering logs) |- | [[Services/IRC-IM-GW|IRC to IM gateway]] || users || {{status_ok}} || style="text-align: left;" | Communication to multiple instant messaging networks through a unified IRC-like interface |- | rowspan="2" | XMPP (Jabber) || [[Services/XMPP|XMPP Network]] || users || {{status_ok}} || style="text-align: left;" | Global Chat Network (inter-communication between many [[wikipedia:Xmpp#History|well-known public IM services]]) |- | [[Services/XMPP WebGW|XMPP WebChat]] || users || {{status_down}} || style="text-align: left;" | Social Platform |- | colspan="2" | [[Services/Tribioune|Triboune Libre]] || public || {{status_down}} || style="text-align: left;" | MilkyPond Web-chat system inspired by [http://linuxfr.org/board the famous one] on [http://linuxfr.org/ Linuxfr.org] |- | rowspan="5" | Sharing || colspan="2" | [[Services/Gallery|Media Gallery]] || public/users || {{status_ok}} || style="text-align: left;" | Photo and video gallery |- | colspan="2" | [[Services/Wiki|Wiki]] || public/users || {{status_ok}} || style="text-align: left;" | Documentation, technical knowledge, useful tips… |- | colspan="2" | [[Services/OwnCloud|OwnCloud]] || public/users || {{status_ok}} || style="text-align: left;" | Personal data store (contacts, calendars, files…) with syncing/sharing capabilities |- | rowspan="2" | Generic || [[Services/FTP|File Repository]] || public/users || {{status_ok}} || style="text-align: left;" | Generic file sharing system (using FTP) |- | [[Services/SAFT|Shell Transfer]] || trusted || {{status_ok}} || style="text-align: left;" | File transfer system using the SAFT protocol (shell access needed) |- | rowspan="3" | Utilities || colspan="2" | [[Services/WebFeeds|News WebReader]] || users || {{status_ok}} || style="text-align: left;" | News feeds reader through a web interface |- | colspan="2" | [[Services/NTP|Time Server]] || public || {{status_ok}} || style="text-align: left;" | System used to automatically setup time on your machines |- | colspan="2" | [[Services/Dico|Dictionary Server]] || public || {{status_ok}} || style="text-align: left;" | Words searching system via a dedicated software (using the DICT protocol) or a Web-interface |- | rowspan="6" | Development || colspan="2" | [[Services/Projects|Project Management & Issue Tracking]] || public/users || {{status_ok}} || style="text-align: left;" | Tool intended to help organize projects |- | rowspan="2" | Code || [[Services/VCS|VCS]] || public/users || {{status_ok}} || style="text-align: left;" | Code/configuration versioning tools (Git, SVN, Baz, Bzr…) |- | [[Services/CodeReview|Code Review]] || public/users || {{status_down}} || style="text-align: left;" | Tool intended to help improve software quality |- | rowspan="2" | Databases || [[Services/SQL|SQL]] || users || {{status_ok}} || style="text-align: left;" | SQL server (PostgreSQL or MySQL) |- | [[Services/LDAP|LDAP]] || users || {{status_ok}} || style="text-align: left;" | LDAP server (OpenLDAP) |- | colspan="2" | [[Services/SoftwareRepository|Software Repository]] || public/users || {{status_ok}} || style="text-align: left;" | Software repository, to provide custom packages (think Debian debs) or installation media (thinks DVDs) |- | rowspan="7" | Hosting || rowspan="2" | Hostnames Directory || [[Services/DNS|DNS]] || users || {{status_ok}} || style="text-align: left;" | Domain Name System (NS1/NS2, DNSSEC…) |- | [[Services/DDNS|Dynamic DNS]] || users || {{status_ok}} || style="text-align: left;" | Dynamic DNS entries, for places where IPs are dynamic and not under your control |- | rowspan="2" | Mail || [[Services/MailHosting|Mail Domains]] || users || {{status_ok}} || style="text-align: left;" | Mail hosting (MX1/MX2) |- | [[Services/MLHosting|Mailing-Lists]] || users || {{status_ok}} || style="text-align: left;" | Distribution lists for mail domains |- | colspan="2" | [[Services/WebHosting|Web Sites/Applications]] || users || {{status_ok}} || style="text-align: left;" | Web pages using HTML/XHTML, CSS, JS, and various server-side programming languages (SSI, PHP, Perl, Python, Ruby…), and statistics (analytics data/reports) |- | colspan="2" | [[Services/XMPPHosting|XMPP Domains]] || users || {{status_ok}} || style="text-align: left;" | XMPP Node for a custom domain |- | colspan="2" | [[Services/Shell|Shell]] || trusted || {{status_ok}} || style="text-align: left;" | Useful for website administration, development, run custom scripts, persistent applications for text-mode geeks… |- | Network || colspan="2" | [[Services/IPv6-Broker|IPv6 tunnels]] || users || {{status_down}} || style="text-align: left;" | Access to the IPv6 world through an IPv4 connection |} == TODO == * in Services/Wiki: https://wiki.duckcorp.org/ * in Services/Shell: link to SAFT * in Services/VCS: https://vcs.duckcorp.org/ * Radio … ac0d0e1f42e37fd81df97761693b75aed68856ea 468 466 2017-06-25T17:09:39Z Duck 2 wikitext text/x-wiki Here is a short overview of the services provided by DuckCorp. Our services are supervised and important data are [[Services/Backup|saved regularly]]. {{warning}} [[Services/Security|Notes about security !]] {| class="wikitable" style="text-align: center; width: 100%;" |+ Available Services |- ! Category !! colspan="2" | Service !! Access !! Status !! Description |- | Entertainment || colspan="2" | [[Games/Minetest|Minetest]] || public/users || {{status_ok}} || style="text-align: left;" | Minecraft-like game |- | rowspan="8" | Communication || rowspan="2" | Mail || [[Services/Mail|eMails]] || users || {{status_ok}} || style="text-align: left;" | Mail boxes with anti-spam/anti-virus, filtering…, or mail redirections |- | [[Services/ML|Mailing-Lists]] || users || {{status_ok}} || style="text-align: left;" | Distribution lists for mails |- | rowspan="3" | IRC || [[Services/IRC|IRC Network]] || public || {{status_ok}} || style="text-align: left;" | MilkyPond Chat Network using a dedicated software or a Web-interface |- | [[Services/IRC-Bouncer|IRC Bouncer]] || users || {{status_ok}} || style="text-align: left;" | IRC proxy (IRC server relaying IRC communications, keeping connections open and remembering logs) |- | [[Services/IRC-IM-GW|IRC to IM gateway]] || users || {{status_ok}} || style="text-align: left;" | Communication to multiple instant messaging networks through a unified IRC-like interface |- | rowspan="2" | XMPP (Jabber) || [[Services/XMPP|XMPP Network]] || users || {{status_ok}} || style="text-align: left;" | Global Chat Network (inter-communication between many [[wikipedia:Xmpp#History|well-known public IM services]]) |- | [[Services/XMPP WebGW|XMPP WebChat]] || users || {{status_down}} || style="text-align: left;" | Social Platform |- | colspan="2" | [[Services/Tribioune|Triboune Libre]] || public || {{status_down}} || style="text-align: left;" | MilkyPond Web-chat system inspired by [http://linuxfr.org/board the famous one] on [http://linuxfr.org/ Linuxfr.org] |- | rowspan="5" | Sharing || colspan="2" | [[Services/Gallery|Media Gallery]] || public/users || {{status_ok}} || style="text-align: left;" | Photo and video gallery |- | colspan="2" | [[Services/Wiki|Wiki]] || public/users || {{status_ok}} || style="text-align: left;" | Documentation, technical knowledge, useful tips… |- | colspan="2" | [[Services/StuffCloud|StuffCloud]] || public/users || {{status_ok}} || style="text-align: left;" | Personal data store (contacts, calendars, files…) with syncing/sharing capabilities |- | rowspan="2" | Generic || [[Services/FTP|File Repository]] || public/users || {{status_ok}} || style="text-align: left;" | Generic file sharing system (using FTP) |- | [[Services/SAFT|Shell Transfer]] || trusted || {{status_ok}} || style="text-align: left;" | File transfer system using the SAFT protocol (shell access needed) |- | rowspan="3" | Utilities || colspan="2" | [[Services/WebFeeds|News WebReader]] || users || {{status_ok}} || style="text-align: left;" | News feeds reader through a web interface |- | colspan="2" | [[Services/NTP|Time Server]] || public || {{status_ok}} || style="text-align: left;" | System used to automatically setup time on your machines |- | colspan="2" | [[Services/Dico|Dictionary Server]] || public || {{status_ok}} || style="text-align: left;" | Words searching system via a dedicated software (using the DICT protocol) or a Web-interface |- | rowspan="6" | Development || colspan="2" | [[Services/Projects|Project Management & Issue Tracking]] || public/users || {{status_ok}} || style="text-align: left;" | Tool intended to help organize projects |- | rowspan="2" | Code || [[Services/VCS|VCS]] || public/users || {{status_ok}} || style="text-align: left;" | Code/configuration versioning tools (Git, SVN, Baz, Bzr…) |- | [[Services/CodeReview|Code Review]] || public/users || {{status_down}} || style="text-align: left;" | Tool intended to help improve software quality |- | rowspan="2" | Databases || [[Services/SQL|SQL]] || users || {{status_ok}} || style="text-align: left;" | SQL server (PostgreSQL or MySQL) |- | [[Services/LDAP|LDAP]] || users || {{status_ok}} || style="text-align: left;" | LDAP server (OpenLDAP) |- | colspan="2" | [[Services/SoftwareRepository|Software Repository]] || public/users || {{status_ok}} || style="text-align: left;" | Software repository, to provide custom packages (think Debian debs) or installation media (thinks DVDs) |- | rowspan="7" | Hosting || rowspan="2" | Hostnames Directory || [[Services/DNS|DNS]] || users || {{status_ok}} || style="text-align: left;" | Domain Name System (NS1/NS2, DNSSEC…) |- | [[Services/DDNS|Dynamic DNS]] || users || {{status_ok}} || style="text-align: left;" | Dynamic DNS entries, for places where IPs are dynamic and not under your control |- | rowspan="2" | Mail || [[Services/MailHosting|Mail Domains]] || users || {{status_ok}} || style="text-align: left;" | Mail hosting (MX1/MX2) |- | [[Services/MLHosting|Mailing-Lists]] || users || {{status_ok}} || style="text-align: left;" | Distribution lists for mail domains |- | colspan="2" | [[Services/WebHosting|Web Sites/Applications]] || users || {{status_ok}} || style="text-align: left;" | Web pages using HTML/XHTML, CSS, JS, and various server-side programming languages (SSI, PHP, Perl, Python, Ruby…), and statistics (analytics data/reports) |- | colspan="2" | [[Services/XMPPHosting|XMPP Domains]] || users || {{status_ok}} || style="text-align: left;" | XMPP Node for a custom domain |- | colspan="2" | [[Services/Shell|Shell]] || trusted || {{status_ok}} || style="text-align: left;" | Useful for website administration, development, run custom scripts, persistent applications for text-mode geeks… |- | Network || colspan="2" | [[Services/IPv6-Broker|IPv6 tunnels]] || users || {{status_down}} || style="text-align: left;" | Access to the IPv6 world through an IPv4 connection |} == TODO == * in Services/Wiki: https://wiki.duckcorp.org/ * in Services/Shell: link to SAFT * in Services/VCS: https://vcs.duckcorp.org/ * Radio … 94a14cb1084e0c578fcce4770272f83e366b2c85 489 468 2017-07-18T18:12:35Z Duck 2 wikitext text/x-wiki Here is a short overview of the services provided by DuckCorp. Our services are supervised and important data are [[Services/Backup|saved regularly]]. {{warning}} [[Services/Security|Notes about security !]] {| class="wikitable" style="text-align: center; width: 100%;" |+ Available Services |- ! Category !! colspan="2" | Service !! Access !! Status !! Description |- | Entertainment || colspan="2" | [[Games/Minetest|Minetest]] || public/users || {{status_ok}} || style="text-align: left;" | Minecraft-like game |- | rowspan="8" | Communication || rowspan="2" | Mail || [[Services/Mail|eMails]] || users || {{status_ok}} || style="text-align: left;" | Mail boxes with anti-spam/anti-virus, filtering…, or mail redirections |- | [[Services/ML|Mailing-Lists]] || users || {{status_ok}} || style="text-align: left;" | Distribution lists for mails |- | rowspan="3" | IRC || [[Services/IRC|IRC Network]] || public || {{status_ok}} || style="text-align: left;" | MilkyPond Chat Network using a dedicated software or a Web-interface |- | [[Services/IRC-Bouncer|IRC Bouncer]] || users || {{status_ok}} || style="text-align: left;" | IRC proxy (IRC server relaying IRC communications, keeping connections open and remembering logs) |- | [[Services/IRC-IM-GW|IRC to IM gateway]] || users || {{status_ok}} || style="text-align: left;" | Communication to multiple instant messaging networks through a unified IRC-like interface |- | rowspan="2" | XMPP (Jabber) || [[Services/XMPP|XMPP Network]] || users || {{status_ok}} || style="text-align: left;" | Global Chat Network (inter-communication between many [[wikipedia:Xmpp#History|well-known public IM services]]) |- | [[Services/XMPP WebGW|XMPP WebChat]] || users || {{status_down}} || style="text-align: left;" | Social Platform |- | colspan="2" | [[Services/Tribioune|Triboune Libre]] || public || {{status_down}} || style="text-align: left;" | MilkyPond Web-chat system inspired by [http://linuxfr.org/board the famous one] on [http://linuxfr.org/ Linuxfr.org] |- | rowspan="5" | Sharing || colspan="2" | [[Services/Gallery|Media Gallery]] || public/users || {{status_down}} || style="text-align: left;" | Photo and video gallery |- | colspan="2" | [[Services/Wiki|Wiki]] || public/users || {{status_ok}} || style="text-align: left;" | Documentation, technical knowledge, useful tips… |- | colspan="2" | [[Services/StuffCloud|StuffCloud]] || public/users || {{status_ok}} || style="text-align: left;" | Personal data store (contacts, calendars, files…) with syncing/sharing capabilities |- | rowspan="2" | Generic || [[Services/FTP|File Repository]] || public/users || {{status_ok}} || style="text-align: left;" | Generic file sharing system (using FTP) |- | [[Services/SAFT|Shell Transfer]] || trusted || {{status_ok}} || style="text-align: left;" | File transfer system using the SAFT protocol (shell access needed) |- | rowspan="3" | Utilities || colspan="2" | [[Services/WebFeeds|News WebReader]] || users || {{status_ok}} || style="text-align: left;" | News feeds reader through a web interface |- | colspan="2" | [[Services/NTP|Time Server]] || public || {{status_ok}} || style="text-align: left;" | System used to automatically setup time on your machines |- | colspan="2" | [[Services/Dico|Dictionary Server]] || public || {{status_ok}} || style="text-align: left;" | Words searching system via a dedicated software (using the DICT protocol) or a Web-interface |- | rowspan="6" | Development || colspan="2" | [[Services/Projects|Project Management & Issue Tracking]] || public/users || {{status_ok}} || style="text-align: left;" | Tool intended to help organize projects |- | rowspan="2" | Code || [[Services/VCS|VCS]] || public/users || {{status_ok}} || style="text-align: left;" | Code/configuration versioning tools (Git, SVN, Baz, Bzr…) |- | [[Services/CodeReview|Code Review]] || public/users || {{status_down}} || style="text-align: left;" | Tool intended to help improve software quality |- | rowspan="2" | Databases || [[Services/SQL|SQL]] || users || {{status_ok}} || style="text-align: left;" | SQL server (PostgreSQL or MySQL) |- | [[Services/LDAP|LDAP]] || users || {{status_ok}} || style="text-align: left;" | LDAP server (OpenLDAP) |- | colspan="2" | [[Services/SoftwareRepository|Software Repository]] || public/users || {{status_ok}} || style="text-align: left;" | Software repository, to provide custom packages (think Debian debs) or installation media (thinks DVDs) |- | rowspan="7" | Hosting || rowspan="2" | Hostnames Directory || [[Services/DNS|DNS]] || users || {{status_ok}} || style="text-align: left;" | Domain Name System (NS1/NS2, DNSSEC…) |- | [[Services/DDNS|Dynamic DNS]] || users || {{status_ok}} || style="text-align: left;" | Dynamic DNS entries, for places where IPs are dynamic and not under your control |- | rowspan="2" | Mail || [[Services/MailHosting|Mail Domains]] || users || {{status_ok}} || style="text-align: left;" | Mail hosting (MX1/MX2) |- | [[Services/MLHosting|Mailing-Lists]] || users || {{status_ok}} || style="text-align: left;" | Distribution lists for mail domains |- | colspan="2" | [[Services/WebHosting|Web Sites/Applications]] || users || {{status_ok}} || style="text-align: left;" | Web pages using HTML/XHTML, CSS, JS, and various server-side programming languages (SSI, PHP, Perl, Python, Ruby…), and statistics (analytics data/reports) |- | colspan="2" | [[Services/XMPPHosting|XMPP Domains]] || users || {{status_ok}} || style="text-align: left;" | XMPP Node for a custom domain |- | colspan="2" | [[Services/Shell|Shell]] || trusted || {{status_ok}} || style="text-align: left;" | Useful for website administration, development, run custom scripts, persistent applications for text-mode geeks… |- | Network || colspan="2" | [[Services/IPv6-Broker|IPv6 tunnels]] || users || {{status_down}} || style="text-align: left;" | Access to the IPv6 world through an IPv4 connection |} == TODO == * in Services/Wiki: https://wiki.duckcorp.org/ * in Services/Shell: link to SAFT * in Services/VCS: https://vcs.duckcorp.org/ * Radio … 8a3905c92b3ff37382b2e821085eedea9c1104ea 496 489 2017-07-20T04:33:25Z Duck 2 wikitext text/x-wiki Here is a short overview of the services provided by DuckCorp. Our services are supervised and important data are [[Services/Backup|saved regularly]]. {{warning}} [[Services/Security|Notes about security !]] {| class="wikitable" style="text-align: center; width: 100%;" |+ Available Services |- ! Category !! colspan="2" | Service !! Access !! Status !! Description |- | Entertainment || colspan="2" | [[Games/Minetest|Minetest]] || public/users || {{status_ok}} || style="text-align: left;" | Minecraft-like game |- | rowspan="8" | Communication || rowspan="2" | Mail || [[Services/Mail|eMails]] || users || {{status_ok}} || style="text-align: left;" | Mail boxes with anti-spam/anti-virus, filtering…, or mail redirections |- | [[Services/ML|Mailing-Lists]] || users || {{status_ok}} || style="text-align: left;" | Distribution lists for mails |- | rowspan="3" | IRC || [[Services/IRC|IRC Network]] || public || {{status_ok}} || style="text-align: left;" | MilkyPond Chat Network using a dedicated software or a Web-interface |- | [[Services/IRC-Bouncer|IRC Bouncer]] || users || {{status_ok}} || style="text-align: left;" | IRC proxy (IRC server relaying IRC communications, keeping connections open and remembering logs) |- | [[Services/IRC-IM-GW|IRC to IM gateway]] || users || {{status_ok}} || style="text-align: left;" | Communication to multiple instant messaging networks through a unified IRC-like interface |- | rowspan="2" | XMPP (Jabber) || [[Services/XMPP|XMPP Network]] || users || {{status_ok}} || style="text-align: left;" | Global Chat Network (inter-communication between many [[wikipedia:Xmpp#History|well-known public IM services]]) |- | [[Services/XMPP WebGW|XMPP WebChat]] || users || {{status_down}} || style="text-align: left;" | Social Platform |- | colspan="2" | [[Services/Tribioune|Triboune Libre]] || public || {{status_down}} || style="text-align: left;" | MilkyPond Web-chat system inspired by [http://linuxfr.org/board the famous one] on [http://linuxfr.org/ Linuxfr.org] |- | rowspan="4" | Sharing || colspan="2" | [[Services/Gallery|Media Gallery]] || public/users || {{status_down}} || style="text-align: left;" | Photo and video gallery |- | colspan="2" | [[Services/Wiki|Wiki]] || public/users || {{status_ok}} || style="text-align: left;" | Documentation, technical knowledge, useful tips… |- | colspan="2" | [[Services/StuffCloud|StuffCloud]] || public/users || {{status_ok}} || style="text-align: left;" | Personal data store (contacts, calendars, files…) with syncing/sharing capabilities |- | colspan="2" | [[Services/FTP|File Repository]] || public/users || {{status_ok}} || style="text-align: left;" | Generic file sharing system (using FTP) |- | rowspan="3" | Utilities || colspan="2" | [[Services/WebFeeds|News WebReader]] || users || {{status_ok}} || style="text-align: left;" | News feeds reader through a web interface |- | colspan="2" | [[Services/NTP|Time Server]] || public || {{status_ok}} || style="text-align: left;" | System used to automatically setup time on your machines |- | colspan="2" | [[Services/Dico|Dictionary Server]] || public || {{status_ok}} || style="text-align: left;" | Words searching system via a dedicated software (using the DICT protocol) or a Web-interface |- | rowspan="6" | Development || colspan="2" | [[Services/Projects|Project Management & Issue Tracking]] || public/users || {{status_ok}} || style="text-align: left;" | Tool intended to help organize projects |- | rowspan="2" | Code || [[Services/VCS|VCS]] || public/users || {{status_ok}} || style="text-align: left;" | Code/configuration versioning tools (Git, SVN, Baz, Bzr…) |- | [[Services/CodeReview|Code Review]] || public/users || {{status_down}} || style="text-align: left;" | Tool intended to help improve software quality |- | rowspan="2" | Databases || [[Services/SQL|SQL]] || users || {{status_ok}} || style="text-align: left;" | SQL server (PostgreSQL or MySQL) |- | [[Services/LDAP|LDAP]] || users || {{status_ok}} || style="text-align: left;" | LDAP server (OpenLDAP) |- | colspan="2" | [[Services/SoftwareRepository|Software Repository]] || public/users || {{status_ok}} || style="text-align: left;" | Software repository, to provide custom packages (think Debian debs) or installation media (thinks DVDs) |- | rowspan="7" | Hosting || rowspan="2" | Hostnames Directory || [[Services/DNS|DNS]] || users || {{status_ok}} || style="text-align: left;" | Domain Name System (NS1/NS2, DNSSEC…) |- | [[Services/DDNS|Dynamic DNS]] || users || {{status_ok}} || style="text-align: left;" | Dynamic DNS entries, for places where IPs are dynamic and not under your control |- | rowspan="2" | Mail || [[Services/MailHosting|Mail Domains]] || users || {{status_ok}} || style="text-align: left;" | Mail hosting (MX1/MX2) |- | [[Services/MLHosting|Mailing-Lists]] || users || {{status_ok}} || style="text-align: left;" | Distribution lists for mail domains |- | colspan="2" | [[Services/WebHosting|Web Sites/Applications]] || users || {{status_ok}} || style="text-align: left;" | Web pages using HTML/XHTML, CSS, JS, and various server-side programming languages (SSI, PHP, Perl, Python, Ruby…), and statistics (analytics data/reports) |- | colspan="2" | [[Services/XMPPHosting|XMPP Domains]] || users || {{status_ok}} || style="text-align: left;" | XMPP Node for a custom domain |- | colspan="2" | [[Services/Shell|Shell]] || trusted || {{status_ok}} || style="text-align: left;" | Useful for website administration, development, run custom scripts, persistent applications for text-mode geeks… |- | Network || colspan="2" | [[Services/IPv6-Broker|IPv6 tunnels]] || users || {{status_down}} || style="text-align: left;" | Access to the IPv6 world through an IPv4 connection |} == TODO == * in Services/Wiki: https://wiki.duckcorp.org/ * in Services/VCS: https://vcs.duckcorp.org/ * Radio … 6da3725b4940e412ae27440e0c87bbf5c0bca334 533 496 2017-09-02T16:51:44Z Duck 2 /* TODO */ wikitext text/x-wiki Here is a short overview of the services provided by DuckCorp. Our services are supervised and important data are [[Services/Backup|saved regularly]]. {{warning}} [[Services/Security|Notes about security !]] {| class="wikitable" style="text-align: center; width: 100%;" |+ Available Services |- ! Category !! colspan="2" | Service !! Access !! Status !! Description |- | Entertainment || colspan="2" | [[Games/Minetest|Minetest]] || public/users || {{status_ok}} || style="text-align: left;" | Minecraft-like game |- | rowspan="8" | Communication || rowspan="2" | Mail || [[Services/Mail|eMails]] || users || {{status_ok}} || style="text-align: left;" | Mail boxes with anti-spam/anti-virus, filtering…, or mail redirections |- | [[Services/ML|Mailing-Lists]] || users || {{status_ok}} || style="text-align: left;" | Distribution lists for mails |- | rowspan="3" | IRC || [[Services/IRC|IRC Network]] || public || {{status_ok}} || style="text-align: left;" | MilkyPond Chat Network using a dedicated software or a Web-interface |- | [[Services/IRC-Bouncer|IRC Bouncer]] || users || {{status_ok}} || style="text-align: left;" | IRC proxy (IRC server relaying IRC communications, keeping connections open and remembering logs) |- | [[Services/IRC-IM-GW|IRC to IM gateway]] || users || {{status_ok}} || style="text-align: left;" | Communication to multiple instant messaging networks through a unified IRC-like interface |- | rowspan="2" | XMPP (Jabber) || [[Services/XMPP|XMPP Network]] || users || {{status_ok}} || style="text-align: left;" | Global Chat Network (inter-communication between many [[wikipedia:Xmpp#History|well-known public IM services]]) |- | [[Services/XMPP WebGW|XMPP WebChat]] || users || {{status_down}} || style="text-align: left;" | Social Platform |- | colspan="2" | [[Services/Tribioune|Triboune Libre]] || public || {{status_down}} || style="text-align: left;" | MilkyPond Web-chat system inspired by [http://linuxfr.org/board the famous one] on [http://linuxfr.org/ Linuxfr.org] |- | rowspan="4" | Sharing || colspan="2" | [[Services/Gallery|Media Gallery]] || public/users || {{status_down}} || style="text-align: left;" | Photo and video gallery |- | colspan="2" | [[Services/Wiki|Wiki]] || public/users || {{status_ok}} || style="text-align: left;" | Documentation, technical knowledge, useful tips… |- | colspan="2" | [[Services/StuffCloud|StuffCloud]] || public/users || {{status_ok}} || style="text-align: left;" | Personal data store (contacts, calendars, files…) with syncing/sharing capabilities |- | colspan="2" | [[Services/FTP|File Repository]] || public/users || {{status_ok}} || style="text-align: left;" | Generic file sharing system (using FTP) |- | rowspan="3" | Utilities || colspan="2" | [[Services/WebFeeds|News WebReader]] || users || {{status_ok}} || style="text-align: left;" | News feeds reader through a web interface |- | colspan="2" | [[Services/NTP|Time Server]] || public || {{status_ok}} || style="text-align: left;" | System used to automatically setup time on your machines |- | colspan="2" | [[Services/Dico|Dictionary Server]] || public || {{status_ok}} || style="text-align: left;" | Words searching system via a dedicated software (using the DICT protocol) or a Web-interface |- | rowspan="6" | Development || colspan="2" | [[Services/Projects|Project Management & Issue Tracking]] || public/users || {{status_ok}} || style="text-align: left;" | Tool intended to help organize projects |- | rowspan="2" | Code || [[Services/VCS|VCS]] || public/users || {{status_ok}} || style="text-align: left;" | Code/configuration versioning tools (Git, SVN, Baz, Bzr…) |- | [[Services/CodeReview|Code Review]] || public/users || {{status_down}} || style="text-align: left;" | Tool intended to help improve software quality |- | rowspan="2" | Databases || [[Services/SQL|SQL]] || users || {{status_ok}} || style="text-align: left;" | SQL server (PostgreSQL or MySQL) |- | [[Services/LDAP|LDAP]] || users || {{status_ok}} || style="text-align: left;" | LDAP server (OpenLDAP) |- | colspan="2" | [[Services/SoftwareRepository|Software Repository]] || public/users || {{status_ok}} || style="text-align: left;" | Software repository, to provide custom packages (think Debian debs) or installation media (thinks DVDs) |- | rowspan="7" | Hosting || rowspan="2" | Hostnames Directory || [[Services/DNS|DNS]] || users || {{status_ok}} || style="text-align: left;" | Domain Name System (NS1/NS2, DNSSEC…) |- | [[Services/DDNS|Dynamic DNS]] || users || {{status_ok}} || style="text-align: left;" | Dynamic DNS entries, for places where IPs are dynamic and not under your control |- | rowspan="2" | Mail || [[Services/MailHosting|Mail Domains]] || users || {{status_ok}} || style="text-align: left;" | Mail hosting (MX1/MX2) |- | [[Services/MLHosting|Mailing-Lists]] || users || {{status_ok}} || style="text-align: left;" | Distribution lists for mail domains |- | colspan="2" | [[Services/WebHosting|Web Sites/Applications]] || users || {{status_ok}} || style="text-align: left;" | Web pages using HTML/XHTML, CSS, JS, and various server-side programming languages (SSI, PHP, Perl, Python, Ruby…), and statistics (analytics data/reports) |- | colspan="2" | [[Services/XMPPHosting|XMPP Domains]] || users || {{status_ok}} || style="text-align: left;" | XMPP Node for a custom domain |- | colspan="2" | [[Services/Shell|Shell]] || trusted || {{status_ok}} || style="text-align: left;" | Useful for website administration, development, run custom scripts, persistent applications for text-mode geeks… |- | Network || colspan="2" | [[Services/IPv6-Broker|IPv6 tunnels]] || users || {{status_down}} || style="text-align: left;" | Access to the IPv6 world through an IPv4 connection |} == TODO == * in Services/Wiki: https://wiki.duckcorp.org/ * Radio … aad9c4f9189c31b7387aec48fc803517bbbf43a4 0 30 464 441 2017-05-11T03:16:22Z Duck 2 /* The DuckCorp Story */ wikitext text/x-wiki == The DuckCorp Story == DuckCorp was born in 2000, from Duck's will to construct something more personal out of the CoinNetwork student house's LAN. At that time, it was merely a simple website, advertising a few personal projects. Later, several machines, gathered with various parts from people willing to dispose of them, used the 'duckcorp.org' domain name and provided services for CoinNetwork; this was the begining of the DC's sponsoring mission. Duck then met Rtp, and they began sharing about system administration topics. As they were willing to administrate CoinNetwork better, they began working on the infrastructure and tools together. Rtp created RtpNet, and received the magical SSH key to be a full DC administrator (so did Duck for Rtpnet indeed). They developed a software prototype aimed at managing the most important services of a distributed web of servers (LMS, LDAP Management System), which helped reducing the daily burden of CoinNetwork's administration a lot. After a while working hand in hand, they both found a job and moved to a new home, still helping each other when possible. Currently, RtpNet and DuckCorp have different goals, and follow their own path. On the way, DC found friendly sponsors (in order of appearance): * Nerim (first Orfeo's housing, IPv6 block, indirect sponsor via Hivane) * Hivane (global connectivity, secondary NS and MX) * Sivit (special accommodations for Toushirou's housing and connectivity) (Nerim again, as it was acquired in 2009) * Alionis (Orfeo's previous housing) * Jaguar Network (Orfeo's housing) (acquired Alionis in 2015) Thanks a lot pals :-). == The MilkyPond Project == MP is an historical share of an IRC network between DC and RN when they both stopped working on the CoinNetwork project. They were willing to cooperate but with the important changes that occurred in their lives, only IRC was kept as a communication link. With time going, DC began recreating services, with the main server Orfeo being kindly sponsored by Nerim, which was used by RN and later by other associations or individuals. Nothing much is done in the name of MP until 2007, besides adding a Jabber server. In early 2007, RN hired a server, Lechat (Dédibox), and was willing to participate more in the share. At the end of the year, T1R joined to help improving the IRC Network. In September 2007, RN was not able to provide services anymore, as it was too much of a burden. Nevertheless, it is still sponsoring the ''milkypond.org'' domain since then. == Key Dates == * 2000-05-22: DuckCorp is created * 2003-04-25: IANA PEN 16829 * 2003-07-09: RtpNet is created * ~2003-10-20: RSA key exchanged between DC and RN (date is from the exif info, but Photoshop is in the way) * 2004-06-12: MilkyPond is created (after DC and RN stopped working on the CoinNetwork project) * 2005-04/05: Orfeo RAM upgraded (512Mo->1.5Go) (blocked to ~800Mo [[Media:Orfeo.duckcorp.org-memory-day.png|until highmem in kernel]]) * 2005-05: IPv6 Ready (using a tunnel) * 2005-11: ** the users' mailing-list started ** major mail system improvements (SMTP auth, improved antispam, webdesk) * 2005-12-08: Orfeo moved from the Nerim's Ivry datacenter to the Nerim suite in the LDCOM Courbevoie datacenter * 2006-01 to 2006-06: Orfeo problems due to an [http://xfs.org/index.php/XFS_FAQ#Q:_What_is_the_issue_with_directory_corruption_in_Linux_2.6.17.3F XFS bug] * 2007-04: IPv6 Ready (native IPv6) * 2007-07: Tōshirō bought and being prepared * 2007-08-08: Nerim's boss shutdown Orfeo violently; quickly repaired and setup behind a mere ADSL (helped by Nerim friends), but BLACKOUT for most services * 2007-08-13: Tōshirō installed in the Sivit suite of the Redbus datacenter, services progressively back online * 2007-09: LDAP infrastructure (again) * 2007-12: ** Orfeo-NG bough and installed in Alionis suite in EQX (Equinix) datacenter ** T1R enters MilkyPond (for the IRC network) * 2008-07: VCS rework, Portal (Restricted Access Helper), Projects Manager (Redmine) * 2009-03: Banya bot (mail gateway for DNS modification, part of the CyborgHood project) * 2009-09: Orfeo moved to [http://www.alionis.net/infra/VBO.html Alionis VBO datacenter] * 2010-03: Thorfinn acquired (Nerim VDS) * 2010-04-24: stratum 2 NTP server [http://support.ntp.org/bin/view/Servers/NtpDuckCorpOrg publicly advertised] and in the [http://www.pool.ntp.org/user/DuckCorp pool] * 2010-05-22: 10th Anniversary !!! * 2010-05-29: 10th Anniversary party with users/sponsors/friends * 2010-10: DNS TSIG and DNSSEC * 2010-11: Toushirou reached Gbps (with a reboot to work around a firmware bug) * 2010-12: ** power outage at VBO, kernel bug preventing Orfeo to restart (IPMI-related) ** Jinta (VM provided by mm), replacing T1R secondary IRC server * 2011-01: problems with backup and capacity * 2011-05: improved IMAP and SIEVE support, shared and public folders * 2011-06: launch of the [https://projects.duckcorp.org/projects/dc-ducklings-volunteer-activities Ducklings Volunteer Activities] * 2011-08: new web service: news feeds (tt-rss), IRC on web replacement, XMPP on web, file sharing (Jyraphe), new web stats (Piwik) * 2011-10: Jinta is dow for good * 2012-01: Korutopi is born (backups) * 2012-02: handly mail retraining through IMAP * 2012-08: ** short electrical outage affecting Orfeo ** file sharing replace by a "cloud" oriented broader software (Owncloud) * 2012-11: XMPP problems -ejabberd cluster bugs) * 2012-12: ** Daneel is dead ** MOSH support * 2013-06: ** Nerim's sponsoring is over => many things to change and end of the IPv6 broker service ** [http://www.minetest.net/ Minetest] server * 2013-10: ** Thorfinn moving from the legacy Nerim Root infrastructure to the Sivit/Nerim virtualization plateform ** Orfeo reached Gbps * 2014-01 to 2014-02, lots of maintenance and consolidation: ** web hosting major upgrade ** Daneel is back alive (so do supervision) ** Toushirou's having bad load problems ** new XMPP server (replacing the wonky ejabberd cluster) ** new blog plateform * 2014-03: ** Thorfinn moving at Hivane ** Jinta revival (Hivane VM) in order to unload Toushirou == Admins == * '''Arnau''' [~2004-12 to now] (fallback admin since 2010-04-27, more active since early 2014) * '''Duck''' [begining to now] (leader) * Finger [2006-07-05 to 2008-02-04] (assistant) * Mmenal [~2004-12 to ~2006-07] * '''Pilou''' [2014-04-02 to now] (fallback admin in charge of hardware/breakage rescue) * Rtp [2003-10 to 2007-07-15, kernel assistant when needed] == Evolution == No real traces were kept, so old numbers are mere rough guess. * 2000 -> 2004 ** more than 60 users served in the [[Media:Coinnetwork resal 2001-2002.png|CoinNetwork LAN]], nearly no external services besides a basic website and IRC ** services targeted for the CoinNetwork LAN * 2004 -> 2007 ** a few users (probably around 20) and 2 entities (RtpNet and [http://www.hurdfr.org/ HurdFr]) hosted ** more Internet-oriented services (complete mail software suite, MLs, Web hosting, DBs, RCS, ...) * 2007 -> 2010 ** more users (nearly 70 users in 2010, a few not very active) and 2 more entity hosted ([http://thebrain.lautre.net/ TheBrain] and [http://www.andesi.org/ Andesi]) ** more services (Jabber, user-friendly antispam, LDAP, IPv6, ...) == Photos == Look at the [http://photos.duckcorp.org/v/duckcorp/ gallery]. b881fb31c1531cbd1ed4e26ef1a55cd37820c378 465 464 2017-05-11T03:24:58Z Duck 2 /* Admins */ wikitext text/x-wiki == The DuckCorp Story == DuckCorp was born in 2000, from Duck's will to construct something more personal out of the CoinNetwork student house's LAN. At that time, it was merely a simple website, advertising a few personal projects. Later, several machines, gathered with various parts from people willing to dispose of them, used the 'duckcorp.org' domain name and provided services for CoinNetwork; this was the begining of the DC's sponsoring mission. Duck then met Rtp, and they began sharing about system administration topics. As they were willing to administrate CoinNetwork better, they began working on the infrastructure and tools together. Rtp created RtpNet, and received the magical SSH key to be a full DC administrator (so did Duck for Rtpnet indeed). They developed a software prototype aimed at managing the most important services of a distributed web of servers (LMS, LDAP Management System), which helped reducing the daily burden of CoinNetwork's administration a lot. After a while working hand in hand, they both found a job and moved to a new home, still helping each other when possible. Currently, RtpNet and DuckCorp have different goals, and follow their own path. On the way, DC found friendly sponsors (in order of appearance): * Nerim (first Orfeo's housing, IPv6 block, indirect sponsor via Hivane) * Hivane (global connectivity, secondary NS and MX) * Sivit (special accommodations for Toushirou's housing and connectivity) (Nerim again, as it was acquired in 2009) * Alionis (Orfeo's previous housing) * Jaguar Network (Orfeo's housing) (acquired Alionis in 2015) Thanks a lot pals :-). == The MilkyPond Project == MP is an historical share of an IRC network between DC and RN when they both stopped working on the CoinNetwork project. They were willing to cooperate but with the important changes that occurred in their lives, only IRC was kept as a communication link. With time going, DC began recreating services, with the main server Orfeo being kindly sponsored by Nerim, which was used by RN and later by other associations or individuals. Nothing much is done in the name of MP until 2007, besides adding a Jabber server. In early 2007, RN hired a server, Lechat (Dédibox), and was willing to participate more in the share. At the end of the year, T1R joined to help improving the IRC Network. In September 2007, RN was not able to provide services anymore, as it was too much of a burden. Nevertheless, it is still sponsoring the ''milkypond.org'' domain since then. == Key Dates == * 2000-05-22: DuckCorp is created * 2003-04-25: IANA PEN 16829 * 2003-07-09: RtpNet is created * ~2003-10-20: RSA key exchanged between DC and RN (date is from the exif info, but Photoshop is in the way) * 2004-06-12: MilkyPond is created (after DC and RN stopped working on the CoinNetwork project) * 2005-04/05: Orfeo RAM upgraded (512Mo->1.5Go) (blocked to ~800Mo [[Media:Orfeo.duckcorp.org-memory-day.png|until highmem in kernel]]) * 2005-05: IPv6 Ready (using a tunnel) * 2005-11: ** the users' mailing-list started ** major mail system improvements (SMTP auth, improved antispam, webdesk) * 2005-12-08: Orfeo moved from the Nerim's Ivry datacenter to the Nerim suite in the LDCOM Courbevoie datacenter * 2006-01 to 2006-06: Orfeo problems due to an [http://xfs.org/index.php/XFS_FAQ#Q:_What_is_the_issue_with_directory_corruption_in_Linux_2.6.17.3F XFS bug] * 2007-04: IPv6 Ready (native IPv6) * 2007-07: Tōshirō bought and being prepared * 2007-08-08: Nerim's boss shutdown Orfeo violently; quickly repaired and setup behind a mere ADSL (helped by Nerim friends), but BLACKOUT for most services * 2007-08-13: Tōshirō installed in the Sivit suite of the Redbus datacenter, services progressively back online * 2007-09: LDAP infrastructure (again) * 2007-12: ** Orfeo-NG bough and installed in Alionis suite in EQX (Equinix) datacenter ** T1R enters MilkyPond (for the IRC network) * 2008-07: VCS rework, Portal (Restricted Access Helper), Projects Manager (Redmine) * 2009-03: Banya bot (mail gateway for DNS modification, part of the CyborgHood project) * 2009-09: Orfeo moved to [http://www.alionis.net/infra/VBO.html Alionis VBO datacenter] * 2010-03: Thorfinn acquired (Nerim VDS) * 2010-04-24: stratum 2 NTP server [http://support.ntp.org/bin/view/Servers/NtpDuckCorpOrg publicly advertised] and in the [http://www.pool.ntp.org/user/DuckCorp pool] * 2010-05-22: 10th Anniversary !!! * 2010-05-29: 10th Anniversary party with users/sponsors/friends * 2010-10: DNS TSIG and DNSSEC * 2010-11: Toushirou reached Gbps (with a reboot to work around a firmware bug) * 2010-12: ** power outage at VBO, kernel bug preventing Orfeo to restart (IPMI-related) ** Jinta (VM provided by mm), replacing T1R secondary IRC server * 2011-01: problems with backup and capacity * 2011-05: improved IMAP and SIEVE support, shared and public folders * 2011-06: launch of the [https://projects.duckcorp.org/projects/dc-ducklings-volunteer-activities Ducklings Volunteer Activities] * 2011-08: new web service: news feeds (tt-rss), IRC on web replacement, XMPP on web, file sharing (Jyraphe), new web stats (Piwik) * 2011-10: Jinta is dow for good * 2012-01: Korutopi is born (backups) * 2012-02: handly mail retraining through IMAP * 2012-08: ** short electrical outage affecting Orfeo ** file sharing replace by a "cloud" oriented broader software (Owncloud) * 2012-11: XMPP problems -ejabberd cluster bugs) * 2012-12: ** Daneel is dead ** MOSH support * 2013-06: ** Nerim's sponsoring is over => many things to change and end of the IPv6 broker service ** [http://www.minetest.net/ Minetest] server * 2013-10: ** Thorfinn moving from the legacy Nerim Root infrastructure to the Sivit/Nerim virtualization plateform ** Orfeo reached Gbps * 2014-01 to 2014-02, lots of maintenance and consolidation: ** web hosting major upgrade ** Daneel is back alive (so do supervision) ** Toushirou's having bad load problems ** new XMPP server (replacing the wonky ejabberd cluster) ** new blog plateform * 2014-03: ** Thorfinn moving at Hivane ** Jinta revival (Hivane VM) in order to unload Toushirou == Admins == === Active === * '''Arnau''' [~2004-12 to now] (fallback admin since 2010-04-27, fully active during 2014) * '''Duck''' [begining to now] (leader) * '''Pilou''' [2014-04-02 to now] (fallback admin in charge of hardware/breakage rescue until February 2016, full-time admin since then) === Emeritus === * Finger [2006-07-05 to 2008-02-04] (assistant) * Mmenal [~2004-12 to ~2006-07] * Rtp [2003-10 to 2007-07-15, kernel assistant when needed] == Evolution == No real traces were kept, so old numbers are mere rough guess. * 2000 -> 2004 ** more than 60 users served in the [[Media:Coinnetwork resal 2001-2002.png|CoinNetwork LAN]], nearly no external services besides a basic website and IRC ** services targeted for the CoinNetwork LAN * 2004 -> 2007 ** a few users (probably around 20) and 2 entities (RtpNet and [http://www.hurdfr.org/ HurdFr]) hosted ** more Internet-oriented services (complete mail software suite, MLs, Web hosting, DBs, RCS, ...) * 2007 -> 2010 ** more users (nearly 70 users in 2010, a few not very active) and 2 more entity hosted ([http://thebrain.lautre.net/ TheBrain] and [http://www.andesi.org/ Andesi]) ** more services (Jabber, user-friendly antispam, LDAP, IPv6, ...) == Photos == Look at the [http://photos.duckcorp.org/v/duckcorp/ gallery]. daeebb3771d7caece372a327321d53dd1f33b48d 0 68 467 446 2017-06-25T17:09:20Z Duck 2 Duck moved page [[Services/OwnCloud]] to [[Services/StuffCloud]] without leaving a redirect wikitext text/x-wiki {{Template:Service | description = The OwnCloud service is a webservice used to access, sync, and share your personal data. Currently you can: * store your files (and in-place view/edit of certain extensions directly from the web interface) * manage your contacts * manage your calendars * <del>manage your tasks</del> (deactivated because broken at the moment) * manage your web bookmarks (with Firefox Sync) | prerequisite = | account = global | ipv6 = true | security_notes = This service is secure but beware when sharing your data to other people. }} {{warning}} Remember not to use this service to store illegal or non-free data. == Access == === Web Interface === Use this URL in your browser: https://stuff.milkypond.org/ Then you can setup your contacts, calendars, and store files. === WebDAV Interface === You can use the [[wikipedia:WebDAV|WebDAV]] interface to sync your data from a desktop application or you mobile device. Applications can use the main address of the web interface (see above) with your credentials and should be able to discover you data, but sometimes they have limitations and you need to specify a full ugly link ; in this case you can find the link in the interface, either on the resource to access or in your personal settings page. ==== Files ==== * Desktop: ** remote drive (synchrounous): use XFCE/Gigolo or GNOME/Nautilus ** synchronize (asynchronous): use the [http://doc.owncloud.org/desktop/ sync] utility (''owncloud-client'' package on Debian) * Mobile Devices: ** Android: use the [http://owncloud.org/support/android/ Owncloud] app (available on [http://f-droid.org/ F-Droid]) to synchronize files ==== Contacts ==== * Desktop: synchronize with GNOME/Evolution * Mobile Devices: ** Android: the [http://owncloud.org/support/android/ Owncloud] app should be able to do it in the future, but you may use the [http://dmfs.org/wiki/index.php?title=CardDAV-Sync CardDAV-Sync] app which is [http://dmfs.org/wiki/index.php?title=Open_source_status to be opensourced] * Webmail: ** Webdesk (Horde): does not work ** old webmail (Squirrelmail): does not work ** newest webmail (RoundCube): works nicely with the newest webmail (RoundCube) (see in Settings->Preferences->CardDAV) ==== Calendars ==== * Desktop: synchronize with GNOME/Evolution * Mobile Devices: ** Android: the [http://owncloud.org/support/android/ Owncloud] app should be able to do it in the future, but you may use the [http://dmfs.org/wiki/index.php?title=CalDAV-Sync CalDAV-Sync] app which is [http://dmfs.org/wiki/index.php?title=Open_source_status to be opensourced], or try [http://acal.me/wiki/Main_Page aCal] (available on [http://f-droid.org/ F-Droid]) which does not use the internal calendar and proved quite slow * Webmail: ** Webdesk (Horde): does not work ** old webmail (Squirrelmail): does not work ** newest webmail (RoundCube): should work but it does not seem to parse events properly even if there's no errors (see in Settings->Preferences->Calendar and the Provider field) ==== Tasks ==== It may be provided by your calendar application. * Desktop: ??? * Mobile Devices: ** Android: the [https://github.com/dmfs/tasks Task] app works well (available on [http://f-droid.org/ F-Droid]) ** Webdesk (Horde): ??? ** old webmail (Squirrelmail): ??? ** newest webmail (RoundCube): ??? == Documentation == * ''OwnCloud'' section in the [http://owncloud.org/support/ Help Page] == Technical Details == This service is made using: * [http://owncloud.org/ OwnCloud] 14ac50abbcde46b01a4103d9bf0a894fe8433752 469 467 2017-06-25T17:45:27Z Duck 2 wikitext text/x-wiki {{Template:Service | description = The StuffCloud service is a webservice used to access, sync, and share your personal data. Currently you can: * store your files and share them with people inside and outside DuckCorp (and in-place view/edit of certain extensions directly from the web interface) * manage your contacts * manage your calendars * manage your tasks * manage your notes * manage your web bookmarks (with browser Sync) * backup your SMS * create your own groups (circles) | prerequisite = | account = global | ipv6 = true | security_notes = This service is secure but beware when sharing your data to other people. }} {{warning}} Remember not to use this service to store illegal or non-free data. == Access == === Web Interface === Use this URL in your browser: https://stuff.milkypond.org/ Then you can setup your contacts, calendars, and store files. === WebDAV Interface === You can use the [[wikipedia:WebDAV|WebDAV]] interface to sync your data from a desktop application or you mobile device. Applications can use the main address of the web interface (see above) with your credentials and should be able to discover you data, but sometimes they have limitations and you need to specify a full ugly link ; in this case you can find the link in the interface, either on the resource to access or in your personal settings page. ==== Files ==== * Desktop: ** remote drive (synchrounous): use XFCE/Gigolo or GNOME/Nautilus ** synchronize (asynchronous): use the [https://nextcloud.com/install/#install-clients sync] utility (no Debian package yet) * Mobile Devices: ** Android: use the [https://nextcloud.com/install/#install-clients NextCloud] app (available on [http://f-droid.org/ F-Droid]) to synchronize files ==== Contacts ==== * Desktop: synchronize with GNOME/Evolution * Mobile Devices: ** Android: you may use the [http://dmfs.org/wiki/index.php?title=CardDAV-Sync CardDAV-Sync] app which is [http://dmfs.org/wiki/index.php?title=Open_source_status to be opensourced] * Webmail: ** Webdesk (Horde): does not work ** webmail (RoundCube): works nicely with the newest webmail (RoundCube) (see in Settings->Preferences->CardDAV) ==== Calendars ==== * Desktop: synchronize with GNOME/Evolution * Mobile Devices: ** Android: you may use the [http://dmfs.org/wiki/index.php?title=CalDAV-Sync CalDAV-Sync] app which is [http://dmfs.org/wiki/index.php?title=Open_source_status to be opensourced], or try [http://acal.me/wiki/Main_Page aCal] (available on [http://f-droid.org/ F-Droid]) which does not use the internal calendar and proved quite slow * Webmail: ** Webdesk (Horde): does not work ** webmail (RoundCube): should work but it does not seem to parse events properly even if there's no errors (see in Settings->Preferences->Calendar and the Provider field) ==== Tasks ==== It may be provided by your calendar application. * Desktop: ??? * Mobile Devices: ** Android: the [https://github.com/dmfs/tasks Task] app works well (available on [http://f-droid.org/ F-Droid]) ** Webdesk (Horde): ??? ** webmail (RoundCube): ??? ==== Web Bookmarks ==== The application "save to Nextcloud Bookmarks" on F-Droid is supposed to work but… == Documentation == * ''NextCloud'' section in the [https://docs.nextcloud.com/ Documentation Page] == Technical Details == This service is made using: * [https://nextcloud.com/ NextCloud] 42d9d4fe614d3d17af41c5d916ab9b8e1f262cee 470 469 2017-06-25T18:10:42Z Duck 2 wikitext text/x-wiki {{Template:Service | description = The StuffCloud service is a webservice used to access, sync, and share your personal data. Currently you can: * store your files and share them with people inside and outside DuckCorp (and in-place view/edit of certain extensions directly from the web interface) * manage your contacts * manage your calendars * manage your tasks * manage your notes * manage your web bookmarks (with browser Sync) * backup your SMS * create your own groups (circles) | prerequisite = | account = global | ipv6 = true | security_notes = This service is secure but beware when sharing your data to other people. }} {{warning}} Remember not to use this service to store illegal or non-free data. == Access == === Web Interface === Use this URL in your browser: https://stuff.milkypond.org/ Then you can setup your contacts, calendars, and store files. === WebDAV Interface === You can use the [[wikipedia:WebDAV|WebDAV]] interface to sync your data from a desktop application or you mobile device. Applications can use the main address of the web interface (see above) with your credentials and should be able to discover you data, but sometimes they have limitations and you need to specify a full ugly link ; in this case you can find the link in the interface, either on the resource to access or in your personal settings page. ==== Files ==== * Desktop: ** remote drive (synchrounous): use XFCE/Gigolo or GNOME/Nautilus ** synchronize (asynchronous): use the [https://nextcloud.com/install/#install-clients sync] utility (no Debian package yet) * Mobile Devices: ** Android: use the [https://nextcloud.com/install/#install-clients NextCloud] app (available on [http://f-droid.org/ F-Droid]) to synchronize files ==== Contacts ==== * Desktop: synchronize with GNOME/Evolution * Mobile Devices: ** Android: you may use the [http://dmfs.org/wiki/index.php?title=CardDAV-Sync CardDAV-Sync] app which is [http://dmfs.org/wiki/index.php?title=Open_source_status to be opensourced] * Webmail: ** Webdesk (Horde): does not work ** webmail (RoundCube): works nicely with the newest webmail (RoundCube) (see in Settings->Preferences->CardDAV) ==== Calendars ==== * Desktop: synchronize with GNOME/Evolution * Mobile Devices: ** Android: you may use the [http://dmfs.org/wiki/index.php?title=CalDAV-Sync CalDAV-Sync] app which is [http://dmfs.org/wiki/index.php?title=Open_source_status to be opensourced], or try [http://acal.me/wiki/Main_Page aCal] (available on [http://f-droid.org/ F-Droid]) which does not use the internal calendar and proved quite slow * Webmail: ** Webdesk (Horde): does not work ** webmail (RoundCube): should work but it does not seem to parse events properly even if there's no errors (see in Settings->Preferences->Calendar and the Provider field) ==== Tasks ==== It may be provided by your calendar application. * Desktop: ??? * Mobile Devices: ** Android: the [https://github.com/dmfs/tasks Task] app works well (available on [http://f-droid.org/ F-Droid]) ** Webdesk (Horde): ??? ** webmail (RoundCube): ??? ==== Web Bookmarks ==== * Desktop: ** Firefox: the [https://addons.mozilla.org/en-US/firefox/addon/floccus/ Floccus] app does not seem to work ** Chromium: the [https://github.com/marcelklehr/floccus/releases/ Floccus] app is untested * Mobile Devices: ** Android: the "save to Nextcloud Bookmarks" app on F-Droid is supposed to work but… == Documentation == * ''NextCloud'' section in the [https://docs.nextcloud.com/ Documentation Page] == Technical Details == This service is made using: * [https://nextcloud.com/ NextCloud] 9820863db7b72927a70cb5191bcd4e2c8ede8fa0 471 470 2017-06-25T18:19:09Z Duck 2 wikitext text/x-wiki {{Template:Service | description = The StuffCloud service is a webservice used to access, sync, and share your personal data. Currently you can: * store your files and share them with people inside and outside DuckCorp (and in-place view/edit of certain extensions directly from the web interface) * manage your contacts * manage your calendars * manage your tasks * manage your notes * manage your web bookmarks (with browser Sync) * backup your SMS * create your own groups (circles) | prerequisite = | account = global | ipv6 = true | security_notes = This service is secure but beware when sharing your data to other people. }} {{warning}} Remember not to use this service to store illegal or non-free data. == Access == === Web Interface === Use this URL in your browser: https://stuff.milkypond.org/ Then you can setup your contacts, calendars, and store files. === WebDAV Interface === You can use the [[wikipedia:WebDAV|WebDAV]] interface to sync your data from a desktop application or you mobile device. Applications can use the main address of the web interface (see above) with your credentials and should be able to discover you data, but sometimes they have limitations and you need to specify a full ugly link ; in this case you can find the link in the interface, either on the resource to access or in your personal settings page. ==== Files ==== * Desktop: ** remote drive (synchrounous): use XFCE/Gigolo or GNOME/Nautilus ** synchronize (asynchronous): use the [https://nextcloud.com/install/#install-clients sync] utility (no Debian package yet) * Mobile Devices: ** Android: use the [https://nextcloud.com/install/#install-clients NextCloud] app (available on [http://f-droid.org/ F-Droid]) to synchronize files ==== Contacts ==== * Desktop: synchronize with GNOME/Evolution * Mobile Devices: ** Android: you may use the [http://dmfs.org/wiki/index.php?title=CardDAV-Sync CardDAV-Sync] app which is [http://dmfs.org/wiki/index.php?title=Open_source_status to be opensourced] * Webmail: ** Webdesk (Horde): does not work ** webmail (RoundCube): works nicely with the newest webmail (RoundCube) (see in Settings->Preferences->CardDAV) ==== Calendars ==== * Desktop: synchronize with GNOME/Evolution * Mobile Devices: ** Android: you may use the [http://dmfs.org/wiki/index.php?title=CalDAV-Sync CalDAV-Sync] app which is [http://dmfs.org/wiki/index.php?title=Open_source_status to be opensourced], or try [http://acal.me/wiki/Main_Page aCal] (available on [http://f-droid.org/ F-Droid]) which does not use the internal calendar and proved quite slow * Webmail: ** Webdesk (Horde): does not work ** webmail (RoundCube): should work but it does not seem to parse events properly even if there's no errors (see in Settings->Preferences->Calendar and the Provider field) ==== Tasks ==== It may be provided by your calendar application. * Desktop: ??? * Mobile Devices: ** Android: the [https://github.com/dmfs/tasks Task] app works well (available on [http://f-droid.org/ F-Droid]) ** Webdesk (Horde): ??? ** webmail (RoundCube): ??? ==== Notes ==== * Desktop: ??? * Mobile Devices: ** Android: the '''Notes''' app on F-Droid is working fine ==== Web Bookmarks ==== * Desktop: ** Firefox: the [https://addons.mozilla.org/en-US/firefox/addon/floccus/ Floccus] app does not seem to work ** Chromium: the [https://github.com/marcelklehr/floccus/releases/ Floccus] app is untested * Mobile Devices: ** Android: the '''save to Nextcloud Bookmarks''' app on F-Droid is supposed to work but… == Documentation == * ''NextCloud'' section in the [https://docs.nextcloud.com/ Documentation Page] == Technical Details == This service is made using: * [https://nextcloud.com/ NextCloud] 85f5f88e457b31004e600648461e0ebe3a0011e1 472 471 2017-06-25T18:49:39Z Duck 2 wikitext text/x-wiki {{Template:Service | description = The StuffCloud service is a webservice used to access, sync, and share your personal data. Currently you can: * store your files and share them with people inside and outside DuckCorp (and in-place view/edit of certain extensions directly from the web interface) * manage your contacts * manage your calendars * manage your tasks * manage your notes * manage your web bookmarks (with browser Sync) * backup your SMS * create your own groups (circles) | prerequisite = | account = global | ipv6 = true | security_notes = This service is secure but beware when sharing your data to other people. }} {{warning}} Remember not to use this service to store illegal or non-free data. == Access == === Web Interface === Use this URL in your browser: https://stuff.milkypond.org/ Then you can setup your contacts, calendars, and store files. === WebDAV Interface === You can use the [[wikipedia:WebDAV|WebDAV]] interface to sync your data from a desktop application or you mobile device. Applications can use the main address of the web interface (see above) with your credentials and should be able to discover you data, but sometimes they have limitations and you need to specify a full ugly link ; in this case you can find the link in the interface, either on the resource to access or in your personal settings page. ==== Files ==== * Desktop: ** remote drive (synchrounous): use XFCE/Gigolo or GNOME/Nautilus ** synchronize (asynchronous): use the [https://nextcloud.com/install/#install-clients sync] utility (no Debian package yet) * Mobile Devices: ** Android: use the [https://nextcloud.com/install/#install-clients NextCloud] app (available on [http://f-droid.org/ F-Droid]) to synchronize files ==== Contacts ==== * Desktop: synchronize with GNOME/Evolution * Mobile Devices: ** Android: you may use the [http://dmfs.org/wiki/index.php?title=CardDAV-Sync CardDAV-Sync] app which is [http://dmfs.org/wiki/index.php?title=Open_source_status to be opensourced] * Webmail: ** Webdesk (Horde): does not work ** webmail (RoundCube): works nicely with the newest webmail (RoundCube) (see in Settings->Preferences->CardDAV) ==== Calendars ==== * Desktop: synchronize with GNOME/Evolution * Mobile Devices: ** Android: you may use the [http://dmfs.org/wiki/index.php?title=CalDAV-Sync CalDAV-Sync] app which is [http://dmfs.org/wiki/index.php?title=Open_source_status to be opensourced], or try [http://acal.me/wiki/Main_Page aCal] (available on [http://f-droid.org/ F-Droid]) which does not use the internal calendar and proved quite slow * Webmail: ** Webdesk (Horde): does not work ** webmail (RoundCube): should work but it does not seem to parse events properly even if there's no errors (see in Settings->Preferences->Calendar and the Provider field) ==== Tasks ==== It may be provided by your calendar application. * Desktop: ??? * Mobile Devices: ** Android: the [https://github.com/dmfs/tasks Task] app works well (available on [http://f-droid.org/ F-Droid]) ** Webdesk (Horde): ??? ** webmail (RoundCube): ??? ==== Notes ==== * Desktop: ??? * Mobile Devices: ** Android: the '''Notes''' app on F-Droid is working fine ==== Web Bookmarks ==== * Desktop: ** Firefox: the [https://addons.mozilla.org/en-US/firefox/addon/floccus/ Floccus] app works; it creates a special bookmark in ''Other Bookmarks'' called ''Owncloud'' (I don't think renaming would not break things); the sync happens every 25 minutes, so be patient ** Chromium: the [https://github.com/marcelklehr/floccus/releases/ Floccus] app is untested * Mobile Devices: ** Android: the '''save to Nextcloud Bookmarks''' app on F-Droid is supposed to work but… == Documentation == * ''NextCloud'' section in the [https://docs.nextcloud.com/ Documentation Page] == Technical Details == This service is made using: * [https://nextcloud.com/ NextCloud] 9ab6a9b5acb9537dcbbb8991bee7231df3d442cd 473 472 2017-07-03T16:41:13Z Duck 2 wikitext text/x-wiki {{Template:Service | description = The StuffCloud service is a webservice used to access, sync, and share your personal data. Currently you can: * store your files and share them with people inside and outside DuckCorp (and in-place view/edit of certain extensions directly from the web interface) * manage your contacts * manage your calendars * manage your tasks * manage your notes * manage your web bookmarks (with browser Sync) * backup your SMS * create your own groups (circles) | prerequisite = | account = global | ipv6 = true | security_notes = This service is secure but beware when sharing your data to other people. }} {{warning}} Remember not to use this service to store illegal or non-free data. == Access == === Web Interface === Use this URL in your browser: https://stuff.milkypond.org/ Then you can setup your contacts, calendars, and store files. === WebDAV Interface === You can use the [[wikipedia:WebDAV|WebDAV]] interface to sync your data from a desktop application or you mobile device. Applications can use the main address of the web interface (see above) with your credentials and should be able to discover you data, but sometimes they have limitations and you need to specify a full ugly link ; in this case you can find the link in the interface, either on the resource to access or in your personal settings page. ==== Files ==== * Desktop: ** remote drive (synchrounous): use XFCE/Gigolo or GNOME/Nautilus ** synchronize (asynchronous): use the [https://nextcloud.com/install/#install-clients sync] utility (no Debian package yet) * Mobile Devices: ** Android: use the [https://nextcloud.com/install/#install-clients NextCloud] app (available on [http://f-droid.org/ F-Droid]) to synchronize files ==== Contacts ==== * Desktop: synchronize with GNOME/Evolution * Mobile Devices: ** Android: the '''DAVdroid''' app (available on [http://f-droid.org/ F-Droid]) works well * Webmail: ** Webdesk (Horde): does not work ** webmail (RoundCube): works nicely with the newest webmail (RoundCube) (see in Settings->Preferences->CardDAV) ==== Calendars ==== * Desktop: synchronize with GNOME/Evolution * Mobile Devices: ** Android: the '''DAVdroid''' app (available on [http://f-droid.org/ F-Droid]) works well * Webmail: ** Webdesk (Horde): does not work ** webmail (RoundCube): should work but it does not seem to parse events properly even if there's no errors (see in Settings->Preferences->Calendar and the Provider field) ==== Tasks ==== It may be provided by your calendar application. * Desktop: ??? * Mobile Devices: ** Android: the '''DAVdroid'' app for synchronization and '''OpenTasks''' for UI work well (both available on [http://f-droid.org/ F-Droid]) ** Webdesk (Horde): ??? ** webmail (RoundCube): ??? ==== Notes ==== * Desktop: ??? * Mobile Devices: ** Android: the '''Notes''' app (available on [http://f-droid.org/ F-Droid]) works but seem to have some bugs (like duplicate saving, to be investigated) ==== Web Bookmarks ==== * Desktop: ** Firefox: the [https://addons.mozilla.org/en-US/firefox/addon/floccus/ Floccus] app works; it creates a special bookmark in ''Other Bookmarks'' called ''Owncloud'' (I don't think renaming would not break things); the sync happens every 25 minutes, so be patient ** Chromium: the [https://github.com/marcelklehr/floccus/releases/ Floccus] app is untested * Mobile Devices: ** Android: the '''save to Nextcloud Bookmarks''' app on F-Droid is supposed to work but… == Documentation == * ''NextCloud'' section in the [https://docs.nextcloud.com/ Documentation Page] == Technical Details == This service is made using: * [https://nextcloud.com/ NextCloud] 32668289460d100e41d4afe2c2082be572505d31 474 473 2017-07-03T16:43:37Z Duck 2 wikitext text/x-wiki {{Template:Service | description = The StuffCloud service is a webservice used to access, sync, and share your personal data. Currently you can: * store your files and share them with people inside and outside DuckCorp (and in-place view/edit of certain extensions directly from the web interface) * manage your contacts * manage your calendars * manage your tasks * manage your notes * manage your web bookmarks (with browser Sync) * backup/restore your SMS * create your own groups (circles) | prerequisite = | account = global | ipv6 = true | security_notes = This service is secure but beware when sharing your data to other people. }} {{warning}} Remember not to use this service to store illegal or non-free data. == Access == === Web Interface === Use this URL in your browser: https://stuff.milkypond.org/ Then you can setup your contacts, calendars, and store files. === WebDAV Interface === You can use the [[wikipedia:WebDAV|WebDAV]] interface to sync your data from a desktop application or you mobile device. Applications can use the main address of the web interface (see above) with your credentials and should be able to discover you data, but sometimes they have limitations and you need to specify a full ugly link ; in this case you can find the link in the interface, either on the resource to access or in your personal settings page. ==== Files ==== * Desktop: ** remote drive (synchrounous): use XFCE/Gigolo or GNOME/Nautilus ** synchronize (asynchronous): use the [https://nextcloud.com/install/#install-clients sync] utility (no Debian package yet) * Mobile Devices: ** Android: use the [https://nextcloud.com/install/#install-clients NextCloud] app (available on [http://f-droid.org/ F-Droid]) to synchronize files ==== Contacts ==== * Desktop: synchronize with GNOME/Evolution * Mobile Devices: ** Android: the '''DAVdroid''' app (available on [http://f-droid.org/ F-Droid]) works well * Webmail: ** Webdesk (Horde): does not work ** webmail (RoundCube): works nicely with the newest webmail (RoundCube) (see in Settings->Preferences->CardDAV) ==== Calendars ==== * Desktop: synchronize with GNOME/Evolution * Mobile Devices: ** Android: the '''DAVdroid''' app (available on [http://f-droid.org/ F-Droid]) works well * Webmail: ** Webdesk (Horde): does not work ** webmail (RoundCube): should work but it does not seem to parse events properly even if there's no errors (see in Settings->Preferences->Calendar and the Provider field) ==== Tasks ==== It may be provided by your calendar application. * Desktop: ??? * Mobile Devices: ** Android: the '''DAVdroid'' app for synchronization and '''OpenTasks''' for UI work well (both available on [http://f-droid.org/ F-Droid]) ** Webdesk (Horde): ??? ** webmail (RoundCube): ??? ==== Notes ==== * Desktop: ??? * Mobile Devices: ** Android: the '''Notes''' app (available on [http://f-droid.org/ F-Droid]) works but seem to have some bugs (like duplicate saving, to be investigated) ==== Web Bookmarks ==== * Desktop: ** Firefox: the [https://addons.mozilla.org/en-US/firefox/addon/floccus/ Floccus] app works; it creates a special bookmark in ''Other Bookmarks'' called ''Owncloud'' (I don't think renaming would not break things); the sync happens every 25 minutes, so be patient ** Chromium: the [https://github.com/marcelklehr/floccus/releases/ Floccus] app is untested * Mobile Devices: ** Android: the '''save to Nextcloud Bookmarks''' app on F-Droid is supposed to work but… == Documentation == * ''NextCloud'' section in the [https://docs.nextcloud.com/ Documentation Page] == Technical Details == This service is made using: * [https://nextcloud.com/ NextCloud] ba2ab7b1c56b280a285f23190558df0c7b385c81 475 474 2017-07-03T16:44:43Z Duck 2 /* Files */ wikitext text/x-wiki {{Template:Service | description = The StuffCloud service is a webservice used to access, sync, and share your personal data. Currently you can: * store your files and share them with people inside and outside DuckCorp (and in-place view/edit of certain extensions directly from the web interface) * manage your contacts * manage your calendars * manage your tasks * manage your notes * manage your web bookmarks (with browser Sync) * backup/restore your SMS * create your own groups (circles) | prerequisite = | account = global | ipv6 = true | security_notes = This service is secure but beware when sharing your data to other people. }} {{warning}} Remember not to use this service to store illegal or non-free data. == Access == === Web Interface === Use this URL in your browser: https://stuff.milkypond.org/ Then you can setup your contacts, calendars, and store files. === WebDAV Interface === You can use the [[wikipedia:WebDAV|WebDAV]] interface to sync your data from a desktop application or you mobile device. Applications can use the main address of the web interface (see above) with your credentials and should be able to discover you data, but sometimes they have limitations and you need to specify a full ugly link ; in this case you can find the link in the interface, either on the resource to access or in your personal settings page. ==== Files ==== * Desktop: ** remote drive (synchronous): use XFCE/Gigolo or GNOME/Nautilus ** synchronize (asynchronous): use the [https://nextcloud.com/install/#install-clients sync] utility (no Debian package yet) * Mobile Devices: ** Android: use the [https://nextcloud.com/install/#install-clients NextCloud] app (available on [http://f-droid.org/ F-Droid]) to synchronize files ==== Contacts ==== * Desktop: synchronize with GNOME/Evolution * Mobile Devices: ** Android: the '''DAVdroid''' app (available on [http://f-droid.org/ F-Droid]) works well * Webmail: ** Webdesk (Horde): does not work ** webmail (RoundCube): works nicely with the newest webmail (RoundCube) (see in Settings->Preferences->CardDAV) ==== Calendars ==== * Desktop: synchronize with GNOME/Evolution * Mobile Devices: ** Android: the '''DAVdroid''' app (available on [http://f-droid.org/ F-Droid]) works well * Webmail: ** Webdesk (Horde): does not work ** webmail (RoundCube): should work but it does not seem to parse events properly even if there's no errors (see in Settings->Preferences->Calendar and the Provider field) ==== Tasks ==== It may be provided by your calendar application. * Desktop: ??? * Mobile Devices: ** Android: the '''DAVdroid'' app for synchronization and '''OpenTasks''' for UI work well (both available on [http://f-droid.org/ F-Droid]) ** Webdesk (Horde): ??? ** webmail (RoundCube): ??? ==== Notes ==== * Desktop: ??? * Mobile Devices: ** Android: the '''Notes''' app (available on [http://f-droid.org/ F-Droid]) works but seem to have some bugs (like duplicate saving, to be investigated) ==== Web Bookmarks ==== * Desktop: ** Firefox: the [https://addons.mozilla.org/en-US/firefox/addon/floccus/ Floccus] app works; it creates a special bookmark in ''Other Bookmarks'' called ''Owncloud'' (I don't think renaming would not break things); the sync happens every 25 minutes, so be patient ** Chromium: the [https://github.com/marcelklehr/floccus/releases/ Floccus] app is untested * Mobile Devices: ** Android: the '''save to Nextcloud Bookmarks''' app on F-Droid is supposed to work but… == Documentation == * ''NextCloud'' section in the [https://docs.nextcloud.com/ Documentation Page] == Technical Details == This service is made using: * [https://nextcloud.com/ NextCloud] 662eb078a3ec729685337c2f9e37fdb891c82f5c 502 475 2017-09-02T16:24:32Z Duck 2 /* Web Bookmarks */ wikitext text/x-wiki {{Template:Service | description = The StuffCloud service is a webservice used to access, sync, and share your personal data. Currently you can: * store your files and share them with people inside and outside DuckCorp (and in-place view/edit of certain extensions directly from the web interface) * manage your contacts * manage your calendars * manage your tasks * manage your notes * manage your web bookmarks (with browser Sync) * backup/restore your SMS * create your own groups (circles) | prerequisite = | account = global | ipv6 = true | security_notes = This service is secure but beware when sharing your data to other people. }} {{warning}} Remember not to use this service to store illegal or non-free data. == Access == === Web Interface === Use this URL in your browser: https://stuff.milkypond.org/ Then you can setup your contacts, calendars, and store files. === WebDAV Interface === You can use the [[wikipedia:WebDAV|WebDAV]] interface to sync your data from a desktop application or you mobile device. Applications can use the main address of the web interface (see above) with your credentials and should be able to discover you data, but sometimes they have limitations and you need to specify a full ugly link ; in this case you can find the link in the interface, either on the resource to access or in your personal settings page. ==== Files ==== * Desktop: ** remote drive (synchronous): use XFCE/Gigolo or GNOME/Nautilus ** synchronize (asynchronous): use the [https://nextcloud.com/install/#install-clients sync] utility (no Debian package yet) * Mobile Devices: ** Android: use the [https://nextcloud.com/install/#install-clients NextCloud] app (available on [http://f-droid.org/ F-Droid]) to synchronize files ==== Contacts ==== * Desktop: synchronize with GNOME/Evolution * Mobile Devices: ** Android: the '''DAVdroid''' app (available on [http://f-droid.org/ F-Droid]) works well * Webmail: ** Webdesk (Horde): does not work ** webmail (RoundCube): works nicely with the newest webmail (RoundCube) (see in Settings->Preferences->CardDAV) ==== Calendars ==== * Desktop: synchronize with GNOME/Evolution * Mobile Devices: ** Android: the '''DAVdroid''' app (available on [http://f-droid.org/ F-Droid]) works well * Webmail: ** Webdesk (Horde): does not work ** webmail (RoundCube): should work but it does not seem to parse events properly even if there's no errors (see in Settings->Preferences->Calendar and the Provider field) ==== Tasks ==== It may be provided by your calendar application. * Desktop: ??? * Mobile Devices: ** Android: the '''DAVdroid'' app for synchronization and '''OpenTasks''' for UI work well (both available on [http://f-droid.org/ F-Droid]) ** Webdesk (Horde): ??? ** webmail (RoundCube): ??? ==== Notes ==== * Desktop: ??? * Mobile Devices: ** Android: the '''Notes''' app (available on [http://f-droid.org/ F-Droid]) works but seem to have some bugs (like duplicate saving, to be investigated) ==== Web Bookmarks ==== * Desktop: ** Firefox: the [https://addons.mozilla.org/en-US/firefox/addon/floccus/ Floccus] app works; it creates a special bookmark in ''Other Bookmarks'' called ''Owncloud'' (I don't think renaming would not break things); the sync happens every 25 minutes, so be patient ** Chromium: the [https://github.com/marcelklehr/floccus/releases/ Floccus] app is untested * Mobile Devices: ** Android: * the '''Nextcloud Bookmarks''' app on F-Droid works well * the '''save to Nextcloud Bookmarks''' app on F-Droid is supposed to work but… == Documentation == * ''NextCloud'' section in the [https://docs.nextcloud.com/ Documentation Page] == Technical Details == This service is made using: * [https://nextcloud.com/ NextCloud] 6afcfb519951b0f64da7113ecb1eb29695710507 507 502 2017-09-02T16:25:13Z Duck 2 /* Tasks */ wikitext text/x-wiki {{Template:Service | description = The StuffCloud service is a webservice used to access, sync, and share your personal data. Currently you can: * store your files and share them with people inside and outside DuckCorp (and in-place view/edit of certain extensions directly from the web interface) * manage your contacts * manage your calendars * manage your tasks * manage your notes * manage your web bookmarks (with browser Sync) * backup/restore your SMS * create your own groups (circles) | prerequisite = | account = global | ipv6 = true | security_notes = This service is secure but beware when sharing your data to other people. }} {{warning}} Remember not to use this service to store illegal or non-free data. == Access == === Web Interface === Use this URL in your browser: https://stuff.milkypond.org/ Then you can setup your contacts, calendars, and store files. === WebDAV Interface === You can use the [[wikipedia:WebDAV|WebDAV]] interface to sync your data from a desktop application or you mobile device. Applications can use the main address of the web interface (see above) with your credentials and should be able to discover you data, but sometimes they have limitations and you need to specify a full ugly link ; in this case you can find the link in the interface, either on the resource to access or in your personal settings page. ==== Files ==== * Desktop: ** remote drive (synchronous): use XFCE/Gigolo or GNOME/Nautilus ** synchronize (asynchronous): use the [https://nextcloud.com/install/#install-clients sync] utility (no Debian package yet) * Mobile Devices: ** Android: use the [https://nextcloud.com/install/#install-clients NextCloud] app (available on [http://f-droid.org/ F-Droid]) to synchronize files ==== Contacts ==== * Desktop: synchronize with GNOME/Evolution * Mobile Devices: ** Android: the '''DAVdroid''' app (available on [http://f-droid.org/ F-Droid]) works well * Webmail: ** Webdesk (Horde): does not work ** webmail (RoundCube): works nicely with the newest webmail (RoundCube) (see in Settings->Preferences->CardDAV) ==== Calendars ==== * Desktop: synchronize with GNOME/Evolution * Mobile Devices: ** Android: the '''DAVdroid''' app (available on [http://f-droid.org/ F-Droid]) works well * Webmail: ** Webdesk (Horde): does not work ** webmail (RoundCube): should work but it does not seem to parse events properly even if there's no errors (see in Settings->Preferences->Calendar and the Provider field) ==== Tasks ==== It may be provided by your calendar application. * Desktop: ??? * Mobile Devices: ** Android: the '''DAVdroid''' app for synchronization and '''OpenTasks''' for UI work well (both available on [http://f-droid.org/ F-Droid]) ** Webdesk (Horde): ??? ** webmail (RoundCube): ??? ==== Notes ==== * Desktop: ??? * Mobile Devices: ** Android: the '''Notes''' app (available on [http://f-droid.org/ F-Droid]) works but seem to have some bugs (like duplicate saving, to be investigated) ==== Web Bookmarks ==== * Desktop: ** Firefox: the [https://addons.mozilla.org/en-US/firefox/addon/floccus/ Floccus] app works; it creates a special bookmark in ''Other Bookmarks'' called ''Owncloud'' (I don't think renaming would not break things); the sync happens every 25 minutes, so be patient ** Chromium: the [https://github.com/marcelklehr/floccus/releases/ Floccus] app is untested * Mobile Devices: ** Android: * the '''Nextcloud Bookmarks''' app on F-Droid works well * the '''save to Nextcloud Bookmarks''' app on F-Droid is supposed to work but… == Documentation == * ''NextCloud'' section in the [https://docs.nextcloud.com/ Documentation Page] == Technical Details == This service is made using: * [https://nextcloud.com/ NextCloud] 1a61bbed07a547aebcb7443dde9d29f9305a9e05 512 507 2017-09-02T16:36:50Z Duck 2 /* Web Bookmarks */ wikitext text/x-wiki {{Template:Service | description = The StuffCloud service is a webservice used to access, sync, and share your personal data. Currently you can: * store your files and share them with people inside and outside DuckCorp (and in-place view/edit of certain extensions directly from the web interface) * manage your contacts * manage your calendars * manage your tasks * manage your notes * manage your web bookmarks (with browser Sync) * backup/restore your SMS * create your own groups (circles) | prerequisite = | account = global | ipv6 = true | security_notes = This service is secure but beware when sharing your data to other people. }} {{warning}} Remember not to use this service to store illegal or non-free data. == Access == === Web Interface === Use this URL in your browser: https://stuff.milkypond.org/ Then you can setup your contacts, calendars, and store files. === WebDAV Interface === You can use the [[wikipedia:WebDAV|WebDAV]] interface to sync your data from a desktop application or you mobile device. Applications can use the main address of the web interface (see above) with your credentials and should be able to discover you data, but sometimes they have limitations and you need to specify a full ugly link ; in this case you can find the link in the interface, either on the resource to access or in your personal settings page. ==== Files ==== * Desktop: ** remote drive (synchronous): use XFCE/Gigolo or GNOME/Nautilus ** synchronize (asynchronous): use the [https://nextcloud.com/install/#install-clients sync] utility (no Debian package yet) * Mobile Devices: ** Android: use the [https://nextcloud.com/install/#install-clients NextCloud] app (available on [http://f-droid.org/ F-Droid]) to synchronize files ==== Contacts ==== * Desktop: synchronize with GNOME/Evolution * Mobile Devices: ** Android: the '''DAVdroid''' app (available on [http://f-droid.org/ F-Droid]) works well * Webmail: ** Webdesk (Horde): does not work ** webmail (RoundCube): works nicely with the newest webmail (RoundCube) (see in Settings->Preferences->CardDAV) ==== Calendars ==== * Desktop: synchronize with GNOME/Evolution * Mobile Devices: ** Android: the '''DAVdroid''' app (available on [http://f-droid.org/ F-Droid]) works well * Webmail: ** Webdesk (Horde): does not work ** webmail (RoundCube): should work but it does not seem to parse events properly even if there's no errors (see in Settings->Preferences->Calendar and the Provider field) ==== Tasks ==== It may be provided by your calendar application. * Desktop: ??? * Mobile Devices: ** Android: the '''DAVdroid''' app for synchronization and '''OpenTasks''' for UI work well (both available on [http://f-droid.org/ F-Droid]) ** Webdesk (Horde): ??? ** webmail (RoundCube): ??? ==== Notes ==== * Desktop: ??? * Mobile Devices: ** Android: the '''Notes''' app (available on [http://f-droid.org/ F-Droid]) works but seem to have some bugs (like duplicate saving, to be investigated) ==== Web Bookmarks ==== * Desktop: ** Firefox: the [https://addons.mozilla.org/en-US/firefox/addon/floccus/ Floccus] app works; it creates a special bookmark in ''Other Bookmarks'' called ''Owncloud'' (I don't think renaming would not break things); the sync happens every 25 minutes, so be patient ** Chromium: the [https://github.com/marcelklehr/floccus/releases/ Floccus] app is untested * Mobile Devices: ** Android: *** the '''Nextcloud Bookmarks''' app on F-Droid works well *** the '''save to Nextcloud Bookmarks''' app on F-Droid is supposed to work but… == Documentation == * ''NextCloud'' section in the [https://docs.nextcloud.com/ Documentation Page] == Technical Details == This service is made using: * [https://nextcloud.com/ NextCloud] 689eb7a1827229b57de02ba9c59f5131259f59e6 515 512 2017-09-02T16:38:42Z Duck 2 /* Web Bookmarks */ wikitext text/x-wiki {{Template:Service | description = The StuffCloud service is a webservice used to access, sync, and share your personal data. Currently you can: * store your files and share them with people inside and outside DuckCorp (and in-place view/edit of certain extensions directly from the web interface) * manage your contacts * manage your calendars * manage your tasks * manage your notes * manage your web bookmarks (with browser Sync) * backup/restore your SMS * create your own groups (circles) | prerequisite = | account = global | ipv6 = true | security_notes = This service is secure but beware when sharing your data to other people. }} {{warning}} Remember not to use this service to store illegal or non-free data. == Access == === Web Interface === Use this URL in your browser: https://stuff.milkypond.org/ Then you can setup your contacts, calendars, and store files. === WebDAV Interface === You can use the [[wikipedia:WebDAV|WebDAV]] interface to sync your data from a desktop application or you mobile device. Applications can use the main address of the web interface (see above) with your credentials and should be able to discover you data, but sometimes they have limitations and you need to specify a full ugly link ; in this case you can find the link in the interface, either on the resource to access or in your personal settings page. ==== Files ==== * Desktop: ** remote drive (synchronous): use XFCE/Gigolo or GNOME/Nautilus ** synchronize (asynchronous): use the [https://nextcloud.com/install/#install-clients sync] utility (no Debian package yet) * Mobile Devices: ** Android: use the [https://nextcloud.com/install/#install-clients NextCloud] app (available on [http://f-droid.org/ F-Droid]) to synchronize files ==== Contacts ==== * Desktop: synchronize with GNOME/Evolution * Mobile Devices: ** Android: the '''DAVdroid''' app (available on [http://f-droid.org/ F-Droid]) works well * Webmail: ** Webdesk (Horde): does not work ** webmail (RoundCube): works nicely with the newest webmail (RoundCube) (see in Settings->Preferences->CardDAV) ==== Calendars ==== * Desktop: synchronize with GNOME/Evolution * Mobile Devices: ** Android: the '''DAVdroid''' app (available on [http://f-droid.org/ F-Droid]) works well * Webmail: ** Webdesk (Horde): does not work ** webmail (RoundCube): should work but it does not seem to parse events properly even if there's no errors (see in Settings->Preferences->Calendar and the Provider field) ==== Tasks ==== It may be provided by your calendar application. * Desktop: ??? * Mobile Devices: ** Android: the '''DAVdroid''' app for synchronization and '''OpenTasks''' for UI work well (both available on [http://f-droid.org/ F-Droid]) ** Webdesk (Horde): ??? ** webmail (RoundCube): ??? ==== Notes ==== * Desktop: ??? * Mobile Devices: ** Android: the '''Notes''' app (available on [http://f-droid.org/ F-Droid]) works but seem to have some bugs (like duplicate saving, to be investigated) ==== Web Bookmarks ==== * Desktop: ** Firefox: the [https://addons.mozilla.org/en-US/firefox/addon/floccus/ Floccus] app works; it creates a special bookmark in ''Other Bookmarks'' called ''Owncloud'' (I don't think renaming would not break things); the sync happens every 25 minutes, so be patient ** Chromium: the [https://github.com/marcelklehr/floccus/releases/ Floccus] app is untested * Mobile Devices: ** Android: *** the '''Nextcloud Bookmarks''' app (available on [http://f-droid.org/ F-Droid]) works well *** the '''save to Nextcloud Bookmarks''' app (available on [http://f-droid.org/ F-Droid]) is supposed to work but does not seem to connect… == Documentation == * ''NextCloud'' section in the [https://docs.nextcloud.com/ Documentation Page] == Technical Details == This service is made using: * [https://nextcloud.com/ NextCloud] c06d9fb5e094237198b2b06f2a37832bb09e2d6d 0 65 476 405 2017-07-03T17:00:01Z Duck 2 /* Using the Android Application */ wikitext text/x-wiki {{Template:Service | description = News feeds reader through a web interface. | prerequisite = | account = global | ipv6 = true | security_notes = This service is secure except if you don't check the website certificate properly (like on Android, see below). }} == Access == === Using a Web Browser === You can connect to the web interface using the following URL: https://gossip.duckcorp.org/ === Using the Android Application === You need the official ttrss application, see: https://play.google.com/store/apps/details?id=org.fox.ttrss (at least another unofficial applications exists made by Nils Braden, but it doesn't work well, TLS certificates problems) Unfortunately the application available on [http://f-droid.org/ F-Droid] is Nils' one and does not work. So if you do not have the Google Play Store on your phone (which is recommended for security and privacy), you may fetch this application using the [https://apk-dl.com/ APK Downloader]. To unlock all the features you will need the Google Play Store to be able to pay, sorry. You might ask a friend or have a dirty phone (like an old one for this kind of infrequent uses) to retrieve the APK (hint: '''Apk Extractor''' and '''SD Scanner''' can help you). The special app you need to get and install just once is: https://play.google.com/store/apps/details?id=org.fox.ttrss.key&rdid=org.fox.ttrss.key You need to connect once through your web browser to activate the web API, which is needed by the Android application: look in Preferences -> Advanced -> Enable external API. Then you can configure your application: * URL: https://gossip.duckcorp.org/ * Login/Password * Accept any SSL certificate: '''False''' * HTTP authentication Login/Password: repeat Login/Password === Sharing News === You can share interesting news: * by mail (but there is no link to your address book) * by URL: these ones are public, meaning there is no need to authenticate to use them, so you can give them away to anybody == Technical Details == This service is made using: * [http://tt-rss.org/ Tiny Tiny RSS] d8a30d7b25e79d0c55db76896e742f8c469b62d0 6 78 479 2017-07-17T19:09:28Z Duck 2 generated by the GraphViz [[Special:Version#Installed_extensions|extension]] from the [[File:File graph GraphVizExtensionDummy dot.gif]] page wikitext text/x-wiki [[Category:GraphViz]][[Category:GraphViz dot]] d1f9cf68e993d59c3c9ce3627f507a743ad6138b 6 79 480 2017-07-17T19:09:28Z Duck 2 generated by the GraphViz [[Special:Version#Installed_extensions|extension]] from the [[File:File graph GraphVizExtensionDummy dot.gif]] page wikitext text/x-wiki [[Category:GraphViz]][[Category:GraphViz dot]] d1f9cf68e993d59c3c9ce3627f507a743ad6138b 6 80 481 2017-07-17T19:09:28Z Duck 2 generated by the GraphViz [[Special:Version#Installed_extensions|extension]] from the [[File:File graph GraphVizExtensionDummy dot.gif]] page wikitext text/x-wiki [[Category:GraphViz]][[Category:GraphViz dot]] d1f9cf68e993d59c3c9ce3627f507a743ad6138b 0 31 482 439 2017-07-17T19:09:34Z Duck 2 wikitext text/x-wiki <graphviz renderer="fdp"> graph DcMap { label = "DuckCorp Architecture"; fontsize = 13; overlap = false; splines = true; edge [fontsize=10.0]; style = bold; node [fontsize=10.0]; labelloc = "t"; internet [label="Internet", fontsize=14, shape=tripleoctagon]; hivane [label="Hivane\nNetwork", fontsize=14, shape=house]; hivane -- internet [label="Hivane\nTransit", style=dashed]; subgraph cluster_hq { label = "DuckCorp HQ (DuckLand)"; color = green; labeljust = "l"; elwing [label="Elwing", URL="DcArchitecture/Elwing"]; daneel [label="Daneel", URL="DcArchitecture/Daneel"]; earendil [label="Eärendil\n(DOWN)", URL="DcArchitecture/Eärendil"]; modem_dc [label="ADSL Modem", shape=box]; sw_dc [label="Switch", shape=box]; sw_dc -- {elwing earendil daneel}; elwing -- {modem_dc}; subgraph cluster_hurdfr { label = "HurdFr (DuckLand part)"; URL = "http://www.hurdfr.org/"; color = darkviolet; labeljust = "l"; amroth [label="Amroth\n(DOWN)", URL="DcArchitecture/Amroth"]; } amroth -- sw_dc; } cluster_hq -- hivane [label="Nerim / Hivane\nADSL", style=dashed]; subgraph cluster_alionis { label = "Alionis Suite\n(Villebon Datacenter)"; URL = "http://maps.google.com/maps/ms?ie=UTF8&hl=en&msa=0&msid=105368272885926046620.0004600d15bf1a76aa1a9&t=h&z=15"; color = black; labeljust = "l"; orfeo [label="Orfeo", URL="DcArchitecture/Orfeo"]; } cluster_alionis -- hivane [label="Hivane / Alionis\nPeering", style=dashed]; subgraph cluster_hivane_virtu { label = "Hivane Virtual Hosting"; color = orange; labeljust = "l"; toushirou [label="Tōshirō\n(VM)", URL="DcArchitecture/Tōshirō"]; jinta [label="Jinta\n(VM)", URL="DcArchitecture/Jinta"]; } cluster_hivane_virtu -- hivane [style=dashed]; subgraph cluster_nerim { label = "Nerim Suite\n(Equinix PA3 Datacenter)"; color = blue; labeljust = "l"; thorfinn [label="Thorfinn\n(Nerim Root VDS)", URL="DcArchitecture/Thorfinn"]; } cluster_nerim -- hivane [label="Nerim / Hivane\nPeering", style=dashed]; subgraph cluster_arnal { label = "Arnal's Lair\n(Japan)"; color = violet; labeljust = "l"; korutopi [label="Korutopi\n(LXC)", URL="DcArchitecture/Korutopi"]; } cluster_arnal -- internet [style=dashed]; } </graphviz> 88aa4f54e2b238c5e029832786b0e85e11ac3b59 0 55 499 395 2017-07-29T15:04:09Z Duck 2 /* Technical Details */ wikitext text/x-wiki {{Template:Service | description = [[wikipedia:Irc|IRC]] (Internet Relay Chat) is a chat system. We have our own internal network, formerly used to contact administrators and discuss with other users. Even is not advertise widely, external people may join the network, so you can invite your friend. | prerequisite = | account = | ipv6 = true | security_notes = Your messages are secured if you connect using the secure port(s), but you need to ensure the recipient uses a secure connection too ; this can be achieved using chanmode +S (see below). {{warning}} Unfortunately, due to a bug in the software (see {{dc-projects|233}}), the link between our servers is not yet fully secured, but you can work around this problem if you talk only to people connected to the same server as yourself. }} == Access == === Using an IRC Software === To connect you need and IRC client, like for example: * [http://irssi.org/ Irssi] * [http://www.pidgin.im Pidgin] * [http://weechat.org/ WeeChat] You need to configure these parameters: * host: irc.milkypond.org * port: ** 6680 (if you want a secure connection using SSL/TLS) ** 6667 or 6669 (because 6667 is sometimes filtered) No password is needed to connect. === Using a Web Interface === Use the following URL: https://irconweb.milkypond.org/ == Official Channels == * #MilkyPond: main channel used to meet with other users and friends and ask general questions * #DuckCorp: contact with DuckCorp Administrators and technical discussions * #News: news feeds on IRC (deprecated but still working) == Contacting IRC Administrators == In case of problems on IRC you can find connected administrators using this command (mind the idle time): /QUOTE STATS p Beware IRC Administrators may not be DuckCorp Administrators. == Features == === Commands === You can see available commands using this command: /QUOTE HELP You can get help about a particular command using this command: /QUOTE HELP &lt;command&gt; ==== Additional Commands for IRC Administrators ==== All special commands are listed in the Oper MOTD. === User Modes === You can see available channel modes using this command: /QUOTE HELP UMODE ==== Mode +g ==== (partial note from the ircd-ratbox documentation) When a client is set +g, that user will be in "Caller ID" mode. Any user that messages a +g client will receive a notice saying that they are in +g (server side ignore) mode. The target client (who is set +g) will also receive a notice saying that so and so messaged them, and that they are in +g mode. The target of the message will only receive one notification per minute, from any client, in order to help prevent flooding. The sender will '''not''' have the rate limit, and will receive a notice saying the target is in +g mode every time they send a message. Note that this behavior is similar to the way AWAY messages are done. There are numerous benefits for both opers and regular users, including the ability to stop spambot messages from ever reaching your client, stopping private message and CTCP floods, and being able to sit on IRC in privacy. One question that arises is how to message specific users, while blocking out everyone else. The command ACCEPT is your answer. To add a user to your accept list, issue the raw command: /QUOTE ACCEPT &lt;nick&gt;,&lt;nick&gt;,&lt;nick&gt;,… That user will now be able to send messages to your client until the association is broken. Associations break in one of the following situations: when an accepted user QUIT's (or is on the other side of a split), you QUIT, or the accepted user changes their nick. The reason why a remote user's nick change will remove them from your accept list is so that you cannot track a user after they changed their nick. Viewing the accept list is also very easy. Issue the raw command: /QUOTE ACCEPT * Removing a user from your accept list is also simple. Issue the command: /QUOTE ACCEPT -&lt;nick&gt; === Channel Modes === You can see available channel modes using this command: /QUOTE HELP CMODE These extra modes are also available: * +r - registered - Users must be registered with services to JOIN * +S - ssl only - Requires SSL/TLS connections to join === IRC Services === To help not loose your favorite nick or channel, the IRC Services can register them so you're still in control. It also helps manage channel with a variety of tools. Look at the user introduction manual in the documentation below. List of Services: * ALIS: search available channels * USERSERV: register an account List of Services available with an account (see USERSERV): * NICKSERV: register nicknames * CHANSERV: register and manage channels * MEMOSERV: send and receive memos from other registered users To get help on each service commands, use the following command: /QUOTE &lt;service&gt; HELP ==== Additional Services for IRC Administrators ==== (exact privileges depends on trust and delegation) * OPERSERV: superadmin commands * JUPESERV: manage "jupes" (fake connections to prevent unwanted links) * GLOBAL: messaging all users * BANSERV: managing global bans * OPERBOT: manage the OperBot * WATCHSERV: spy on service commands (only available via DCC) You also may be able to access services via DCC CHAT, which is handy when a flood occurs, using: /DCC CHAT operserv == Documentation == * [http://docs.ratbox.org/svc_userintro.shtml IRC Services Introduction] == Technical Details == This service is made using: * [http://www.ratbox.org/ ircd-ratbox] * [http://services.ratbox.org/ ratbox-services] * [https://thelounge.github.io/ The Lounge] (Web UI) c595eb18cfd7fa2abd4c3b1b5a30929565c35837 0 53 524 387 2017-09-02T16:41:52Z Duck 2 /* Folders */ wikitext text/x-wiki {{Template:Service | description = The file repository is a general-purpose file exchange method. You push files into it and they are kept until you remove them. You may also share them with a other people. | prerequisite = You need to ask an administrator for an account if you want to push your own files, but you don't need anything if you just want to retrieve files from the public folders. | account = global-reg | ipv6 = true | security_notes = This service is secure. }} {{warning}} Remember not to use this service to store illegal or non-free data. == Access == You need a FTP client software to access this service, for example: * on GNU/*: filezilla or lftp * on MacOS: CyberDuck * on Windows: filezilla Most browsers should also work for read access. The publics folders are available for read access using this URL: ftp://ftp.duckcorp.org/ If you want to push files, you need to authenticate with SSL/TLS using this URL: ftps://ftps.duckcorp.org/ You may also access files directly on Toushirou in ''/ftp/ftp.duckcorp.org/'' if you have a [[Services/Shell|shell access]]. == Folders == Summary of important folders for write access: * private ('''DEPRECATED'''): restricted folders, for users or groups of users; ask an administrator if you need private folders * public: folders which can be read by everybody (accessible directly without authentication on ftp://ftp.duckcorp.org/) * repository: upload folders for the [[Services/SoftwareRepository|software repository]] facility * sites: folders for hosted websites content == Documentation == * generic documentation on [[wikipedia:Ftp|FTP]] == Technical Details == This service is made using: * [http://proftpd.org/ ProFTPD] ad789af8cf49c062082b0d37279077fab9c08e6b 0 75 527 456 2017-09-02T16:48:11Z Duck 2 wikitext text/x-wiki {{Template:Service | description = A few VCS tools are available to DC users. | prerequisite = Write access is currently limited to people having a shell account. No prerequisite for read access. | account = global-reg | ipv6 = true | security_notes = This service is secure. }} == Access == Use the following URL: https://vcs.duckcorp.org/ === Git === * Direct SSH access: <tt>ssh://login@vcs.duckcorp.org/srv/vcs/git/...</tt> * [https://vcs-git.duckcorp.org/ Git via HTTP (read-only)] * Git via Git protocol using <tt>git://vcs-git.duckcorp.org/...</tt> to access <tt>/vcs/git/...</tt> * [https://vcs-git-viewer.duckcorp.org/ Git browser] f4ce4e2cc40cb8d6e312329a7f1d834ff060ec6f 530 527 2017-09-02T16:51:31Z Duck 2 /* Access */ wikitext text/x-wiki {{Template:Service | description = A few VCS tools are available to DC users. | prerequisite = Write access is currently limited to people having a shell account. No prerequisite for read access. | account = global-reg | ipv6 = true | security_notes = This service is secure. }} == Access == Use the following URL: https://vcs.duckcorp.org/ Various VCS are possible: git, Mercurial, SVN, Bazaar… === Git === * Direct SSH access: <tt>ssh://login@vcs.duckcorp.org/srv/vcs/git/...</tt> * [https://vcs-git.duckcorp.org/ Git via HTTP (read-only)] * Git via Git protocol using <tt>git://vcs-git.duckcorp.org/...</tt> to access <tt>/vcs/git/...</tt> * [https://vcs-git-viewer.duckcorp.org/ Git browser] 7f21ff489b249f27a3c186c425e9dd6883dd0c09 596 530 2017-09-30T13:27:05Z Duck 2 wikitext text/x-wiki {{Template:Service | description = A few VCS tools are available to DC users. | prerequisite = Write access is currently limited to people having a shell account. No prerequisite for read access. | account = global-reg | ipv6 = true | security_notes = This service is secure. }} == Access == Use the following URL to access public repositories: https://vcs.duckcorp.org/ If you have [[Services/Shell|shell access]]: * public repositories are available in ''/srv/vcs/'' on ''vcs.duckcorp.org'' * you can create private repositories at will in your home directory * you can ask for a project-specific space in ''/srv/projects/'' on ''vcs.duckcorp.org'' and store the project private repositories in it == Managing a Repository == Ask an administrator to create a new repository. Various VCS are possible: git, Mercurial, SVN, Bazaar… If you have [[Services/Shell|shell access]], then you will be able to manage your own === Git === * Direct SSH access: <tt>ssh://login@vcs.duckcorp.org/srv/vcs/git/...</tt> * [https://vcs-git.duckcorp.org/ Git via HTTP (read-only)] * Git via Git protocol using <tt>git://vcs-git.duckcorp.org/...</tt> to access <tt>/vcs/git/...</tt> * [https://vcs-git-viewer.duckcorp.org/ Git browser] 15772560b02aa5a7e2fd81b6474456d04a5fb591 599 596 2017-09-30T13:30:31Z Duck 2 wikitext text/x-wiki {{Template:Service | description = A few VCS tools are available to DC users. | prerequisite = Write access is currently limited to people having a shell account. No prerequisite for read access. | account = global-reg | ipv6 = true | security_notes = This service is secure. }} == Access == Use the following URL to access public repositories: https://vcs.duckcorp.org/ Various VCS are possible: git, Mercurial, SVN, Bazaar… If you have [[Services/Shell|shell access]], public repositories are also available in ''/srv/vcs/'' on ''vcs.duckcorp.org'' == Managing a Repository == If you have [[Services/Shell|shell access]]: * ask an administrator if you need a space for public repositories * you can create private repositories at will in your home directory * ask an administrator if you need a project-specific space in ''/srv/projects/'' on ''vcs.duckcorp.org'' to store the project private repositories in it === Git === * Direct SSH access: <tt>ssh://login@vcs.duckcorp.org/srv/vcs/git/...</tt> * [https://vcs-git.duckcorp.org/ Git via HTTP (read-only)] * Git via Git protocol using <tt>git://vcs-git.duckcorp.org/...</tt> to access <tt>/vcs/git/...</tt> * [https://vcs-git-viewer.duckcorp.org/ Git browser] 6e360a16449c07e97265d6907459f6db8532a264 0 48 536 225 2017-09-02T16:55:43Z Duck 2 wikitext text/x-wiki Besides critical system and services data, most of users data are backuped up too. Data you can expect being saved: * mails, along with antispam learning data and SIEVE filters * shared services configurations and personnal data (webmail, projects, jabber, web stats, VCS…) * web data (hosted websites) * FTP data * /home on all machines where users can have shell access A few files or directory names are globally excluded from backup: * cache * .Trash In your personnal data, you can choose to exclude directories (and their children), either because you don't want us to copy your data elsewhere, or because it is not needed (allowing us to save data on the backup system). To do that, you simply need to create a ''.nobackup'' empty file inside the directories to ignore, nothing more. The backup system would detect it and skip the whole directory over. 1ffd7eeeaf48bbd018c73b3349489c7f114e9e29 0 64 539 350 2017-09-02T17:12:33Z Duck 2 /* Access */ wikitext text/x-wiki {{Template:Service | description = This service allows to keep your machine on time, by being synchronized with a remote time server. The later may itself be synchronized with a better time server and so on. The last one (stratum 1) uses an accurate source of time (stratum 0), like an atomic or GPS clock, and distribute it over the Internet. | prerequisite = | account = | ipv6 = true | security_notes = There is no big security concern except you can't be sure you're talking to our NTP server (no DTLS support). }} == Access == === On a personal computer === You need a NTP software to synchronize your machine. On Debian you can install it easily using: apt-get install chrony You then need to edit the configuration file ''/etc/chrony/chrony.conf'' to add this line: server ntp.duckcorp.org iburst prefer And then restart the service: service chrony restart === On a server === You need a NTP software to synchronize your machine. On Debian you can install it easily using: apt-get install ntp You then need to edit the configuration file ''/etc/ntp.conf'' to add this line: server ntp.duckcorp.org iburst prefer And then restart the service: service ntp restart == NTP Pool == Our server is also part of the [http://www.pool.ntp.org/en/ NTP Pool Project]. If you use servers named like ''*.pool.ntp.org'', then you may use our server sometimes. It is often used by vendors and GNU/* distributions. == Documentation == * generic documentation on [[wikipedia:Network_Time_Protocol|NTP]] == Technical Details == This service is made using: * [http://www.ntp.org/ NTP daemon] 51b2629f803d53bbf2ab58ac82a31508530e145e 542 539 2017-09-02T17:13:49Z Duck 2 /* Technical Details */ wikitext text/x-wiki {{Template:Service | description = This service allows to keep your machine on time, by being synchronized with a remote time server. The later may itself be synchronized with a better time server and so on. The last one (stratum 1) uses an accurate source of time (stratum 0), like an atomic or GPS clock, and distribute it over the Internet. | prerequisite = | account = | ipv6 = true | security_notes = There is no big security concern except you can't be sure you're talking to our NTP server (no DTLS support). }} == Access == === On a personal computer === You need a NTP software to synchronize your machine. On Debian you can install it easily using: apt-get install chrony You then need to edit the configuration file ''/etc/chrony/chrony.conf'' to add this line: server ntp.duckcorp.org iburst prefer And then restart the service: service chrony restart === On a server === You need a NTP software to synchronize your machine. On Debian you can install it easily using: apt-get install ntp You then need to edit the configuration file ''/etc/ntp.conf'' to add this line: server ntp.duckcorp.org iburst prefer And then restart the service: service ntp restart == NTP Pool == Our server is also part of the [http://www.pool.ntp.org/en/ NTP Pool Project]. If you use servers named like ''*.pool.ntp.org'', then you may use our server sometimes. It is often used by vendors and GNU/* distributions. == Documentation == * generic documentation on [[wikipedia:Network_Time_Protocol|NTP]] == Technical Details == This service is made using: * [https://chrony.tuxfamily.org/ Chrony daemon] * [http://www.ntp.org/ NTP daemon] 51fdd433cdec452ce10327344836c8214a20417a 0 49 545 458 2017-09-04T13:11:20Z Duck 2 /* Using a Web Interface */ wikitext text/x-wiki {{Template:Service | description = Available services: * multiple email addresses (mailboxes+aliases or redirections) based on the ''milkypond.org'' (or maybe ''duckcorp.org'') domain * roaming accounts to be able to send emails wherever you are If you want email addresses using you own domain(s), see the [[Services/MailHosting|mail hosting service]]. | prerequisite = | account = global-reg | ipv6 = true | security_notes = Access to the mail services are fully secured, and to your data, nevertheless most mail exchange on the Internet are not. Complete security can be achieved using signed and encrypted mail (see [[wikipedia:Pretty_Good_Privacy|OpenPGP]] and [[wikipedia:S/MIME|S/MIME]]) }} == Access == === Using a Mail Reader === You can retrieve your mails, in case of a real mailbox, using either: * IMAP+TLS (TCP 143) / IMAPS (TCP 993) on imap.duckcorp.org * or POP3+TLS (TCP 110) / POP3S (TCP 995) on pop.duckcorp.org The IMAP protocol is recommended over POP3, as it provides many interesting features. If you want to download all your mails absolutely at home, loosing the ability to read your mail from anywhere on the planet, you can do that with IMAP too (look at your mail client settings). You can use our servers to send mails out too via smtp.duckcorp.org using: * SMTP+TLS (TCP 25) / SMTPS (TCP 465) * and SASL authentication === Using a Web Interface === A [https://webmail.duckcorp.org/ webmail interface] is available. == Antivirus and Antispam == Mails stored on our server are checked upon arrival for viruses and SPAMs. Mail redirected to a third party mailbox are not, not to mess with the strategy of the the final destination (which could arm learning greatly). Mails being viruses are suppressed automatically upon arrival. Once in a week, an extra antivirus check is done on all hosted mailboxes, to remove viruses not detected at the time it arrived (our antivirus database is updated daily), so you may see such mail disappear from your mailbox, don't fear. SPAMs are more difficult to detect, and it is an error-prone process, so we chose to use a learning software instead of using a global database. On the bright side of things, you would never loose mails and the software should be able to learn what is a SPAM from '''your''' point of view (which has proved to differ slightly between our users), but on the grey side you will have to teach him regularly to avoid errors. When your account is created, it acts like an empty headed body letting everything through, but after a few weeks of teaching it is able to recognize most of your habits and block a lot of annoying SPAM. === Web Interface === The web interface is an easy way to view your mail history, changes your settings, and more. It is available using this URL: https://spamfilter.duckcorp.org/ ==== User Settings ==== You can yourself setup a few parameters in the ''Preferences'' page of the [https://spamfilter.duckcorp.org/ web interface], mostly: * how the system should train: ** TEFT (''On every new message scanned by the filter''): useful to learn very quickly especially on a new mailbox or when you've got tons of spam on your addresses, but you need to train it regulary (daily is better) or it will learn wrong (very quickly too !) ** TOE (''Only when the filter makes a mistake''): slow learning, but if you don't have time for training very often or go on long holidays without internet access this mode will give you a stable behavior ** TUM (''Only with new data or if the filter makes a mistake''): trade-off between the two previous modes, learn quite fast and not too demanding, adapts better to new SPAMs then TOE * filter sensitivity: you can ask the system to be more or less aggressive * message handling: see [[#Delivery Mode|delivery mode]] below * ''Disable DSPAM filtering'': you may switch off filtering at your own risk We strongly recommend using TEFT with daily training for a few weeks then switching to TUM. If you need to go away for a long time, switching to TOE is recommended. Using the quarantine feature is also a safe choice, as the web interface is quite easy to use. === Delivery Mode === ==== Quarantine ==== With the ''message handling'' setting set to ''Quarantine the message'' (see [[#User Settings|user preferences]]), then your SPAMs will not go into your mailbox but stay in this stagging area. These mails are kept by the system until you decide their fate. Through the ''Quarantine'' page of the web interface, you can list these mails and: * free legitimate mails wrongly considered as SPAM by the system * delete real SPAMs if the system was right about them (freeing useful space) In this mode, you need to flush your quarantine once in a while. ==== Delivered with Special Header (default, recommended) ==== With the ''message handling'' setting set to ''Deliver the message normally with a X-DSPAM-Result header'', mails are delivered normally, but with a special field added to your mail headers (not always visible depending on your mail client and its configuration). This is quite handy if you prefer SPAMs arranged in a specific folder. You may use then the provided [[#Mail Filtering |filtering system]] to sort them properly, or configure your eMail client. ==== Delivered with Modified Subject (not recommended) ==== With the ''message handling'' setting set to ''Tag the Subject header with'', mails are delivered normally, but with a modified title to alert you this is a SPAM (which is a tad ugly). This mode is really not clean and not recommended, but it exist for historical purposes, so you might still use it if you really wish to. === Retraining === Teaching the system what is SPAM and HAM (non-SPAM) is called ''retraining''. ==== Retraining using the Special ''Junk'' Folder (default, recommended) ==== If you have of create a folder named ''Junk'', then it is automatically magic: * if you drop mail into it, it is automatically retrained as SPAM * if you move it out of it, it is automatically retrained as HAM * with time, certain old mails automatically expire, see below To use this folder properly, SPAMs '''must''' be delivered in the ''Junk'' folder automatically, so you can move them out in case of error. If using the default settings, you just need to subscribe to this folder in your mail software (this folder is always auto-created). If you are using different setting, you need to select the [[#Delivered with Special Header|delivery mode using a special header]], and use the provided [[#Mail Filtering|filtering system]] to drop them in the ''Junk'' folder ('''Do not use your mail software for this filtering, this is horribly inefficient and might alter the learning badly'''). Automatic expiration logic, based on delivery time (and not the mail timestamp): * deleted mails are purged after 1 day * read mails without an important flag are purge after 7 days * unread mails without an important flag are purge after 30 days If you use the ''incoming_spam'' [[#Global_Rules|global rule]], then SPAMs newly discovered by the system are flagged as important, which means these mails will never by purged until you review it and decide to delete them or mark them as not important. Custom rules might play with this flag and achieve an automatic selection. ==== Retraining via Web Interface ==== Use the [https://spamfilter.duckcorp.org/ web interface] to retrain from errors in the ''History'' page. If you are using the ''quarantine'', then freed mails will automatically be retrained as HAM. ==== Retraining via Mail ==== Resend SPAMs to [mailto:dc-spam@duckcorp.org dc-spam@duckcorp.org] and HAM (non-SPAM) to [mailto:dc-ham@duckcorp.org dc-ham@duckcorp.org]. {{warning}} PLEASE TAKE CARE to use the ''resend'' function of your mailer and never use ''forward'', which would result in '''yourself''' being considered as SPAM or HAM. == Mail Filtering == With your favourite mail client, you can probably filter your mails in proper folders already. Nevertheless, this can be an annoying operation: * blocking you mail client for a long time if you have to process plenty of mails * downloading each mail information, and sometimes content (depending on your filters), is lenghty too, and cost much bandwidth * syncing filters across your machines (home desktop, laptop, office machine…) is a pain in the ass * processing only when you're online prevents triggering actions in a timely manner (automatic redirect, vacation messages…), and running a machine 24/7 with a mail client polling new mails every 30s is not a solution We provide a much better way to do this using the [[wikipedia:Sieve_(mail_filtering_language)|SIEVE]] filters. Shortly, SIEVE is a language dedicated to expressing mail filters (also called ''rules''). Our server is able to process your mails according to these filters as soon as they arrive. You then don't have to care about them anymore, and may use light mail clients or webmails when you're not on your machine with your favourite software. === Rules Configuration === You can express sort/reject/vacation/… filters using these rules, as the capabilities are very rich. Several softwares support managing SIEVE rules: * Icedove/Thunderbird: *: using the SIEVE extension (in ''xul-ext-sieve'' Debian package), it provides a rules editor (for power-users) * Horde (Ingo): *: provides an easy to use web interface *: this webmail has been made available [https://webdesk.duckcorp.org/ here] * Squirrelmail: *: coupled with the Avelsieve extension, provides an easy to use web interface *: this webmail has been made available [https://webmail-sm.duckcorp.org/ here] * Roundcube: *: coupled with the sieverules extension, provides an easy to use web interface *: this webmail has been made available [https://webmail-rc.duckcorp.org/ here] * sieve-connect: *: provides a CLI to upload/download/activate your rules files *: this tool is available on [[Services/Shell|shell hosts]] (tell us if you know more software supporting this feature) To push your filters on the server, a dedicated protocol exists: MANAGESIEVE (TCP 4190) on ''sieve.duckcorp.org''. Our webmails are already configured to use it, but it you use sieve-connect from our hosts or your own mail software, you'll need these parameters. You can read more info about SIEVE here: * supported SIEVE features on our server: http://pigeonhole.dovecot.org/ * http://www.fastmail.fm/docs/sieve/ * http://sieve.info/ === Default Rules === The default settings (since 2112-02-11) are to use the global ''incoming_spam'' rule and the [[#Delivered with Special Header|delivery using a special header]], in order to provide a simple default configuration for most users. All other mails will end-up in your ''Inbox'' folder and you may then sort them by yourself. If you create your own rules, the default rules won't apply anymore, so power-users can replace the default behavior completely to achieve what they really need. === Global Rules === Global rules are provided to ease configuration on specific filters. They can easily be included in your own configuration. Available rules: * ''incoming_spam'': *: SPAMs will automatically be delivered in the ''Junk'' folder and marked as ''important'' *: you need to use the [[#Delivered with Special Header|delivery using a special header]] for this rule to have any effect If you write your own custom rules, here is an example on how to use one of them: require ["include"]; include :global "&lt;rule-name&gt;"; == Fetching eMails from an External Mailbox == {{todo}} == Shared/Public Folders == You may need to share mails or messages with friends or people you do stuff with (in a project or association). Depending on your needs, two solutions are possible: * share some of your own private folders, thus called ''shared folders'' * manage a special folder hierarchy, called ''public folders'' (even if they may not be accessible to everyone) *: if you need one, ask an administrator; the namespace name can be freely chosen but must be unambiguous and is subject to approval === Namespaces === Through IMAP, or our webmails internally using IMAP, it is possible to partition the folder hierarchy into ''namespaces''. Traditionally you are using the root namespace for your private folders. Additional namespaces can be created and will appear among your own folders or separate, depending on your mail client's choice of representation. To avoid name clashes, we decided to prefix all additional namespace names with a '''#'''. Since 2011-05-14, the following extra namespaces are created and reserved: * #Shared, containing all folders other users decided to share with you * #MilkyPond, containing public MP/DC informational mailboxes you may subscribe at will === Folders Permissions === Using IMAP, it is possible to setup rights (read only, write allowed…) to your own folders in order to share them with other users, or group of users. Public folders are owned by no-one, and must be created by the administrators. Once your request is accepted we will delegate its administration to your care. It can then can be managed like shared folders. === Software Support === Client mail softwares support: * Horde: *: support namespaces, shared folders configurable via ''Options->Share Folders'' menu but no ACLs for public folders * RoundCube: *: support namespaces, shared and public folders configurable via ''Settings->Folders'', selecting a folder then using the ''Sharing'' tab * Icedove/Thunderbird: *: support namespaces, shared and public folders configurable via folder selection and ''Tools->Imap-ACL'' menu action Most other softwares have namespace support only, so you should be able to use shared/public folders you have rights on but not configure them yourself (tell us if you know more software supporting this feature). == Limitations == === Maximum Mail Size === Mail you send or receive are limited to '''10MB'''. If you need to transmit much bigger data, then a mail transport is not appropriate, you'd better use a file sharing method instead. === Quotas === Even if it would be nice to live without it, we had to establish quotas to force people sort their mails out once in a while and delete useless things instead of leaving an ever-growing mess behind. The default quota is '''512MB''' which is not that big but should match needs of most users. This said, you may ask us for more and there's no reason we would refuse a reasonable demand. == Technical Details == This service is made using: * [http://www.postfix.org/ Postfix] * [http://dovecot.org/ Dovecot] * [http://dspam.sourceforge.net DSPAM] * [http://johannes.sipsolutions.net/Projects/dovecot-antispam dovecot-antispam] * [https://projects.duckcorp.org/projects/spoolinger Spoolinger] * [http://www.horde.org/ Horde] * [http://www.squirrelmail.org/ SquirrelMail] * [http://www.roundcube.net/ RoundCube] 2e1bcd2971da08cfbfaaaca4b403c4f5190ccd8d 575 545 2017-09-30T13:12:29Z Duck 2 /* Maximum Mail Size */ wikitext text/x-wiki {{Template:Service | description = Available services: * multiple email addresses (mailboxes+aliases or redirections) based on the ''milkypond.org'' (or maybe ''duckcorp.org'') domain * roaming accounts to be able to send emails wherever you are If you want email addresses using you own domain(s), see the [[Services/MailHosting|mail hosting service]]. | prerequisite = | account = global-reg | ipv6 = true | security_notes = Access to the mail services are fully secured, and to your data, nevertheless most mail exchange on the Internet are not. Complete security can be achieved using signed and encrypted mail (see [[wikipedia:Pretty_Good_Privacy|OpenPGP]] and [[wikipedia:S/MIME|S/MIME]]) }} == Access == === Using a Mail Reader === You can retrieve your mails, in case of a real mailbox, using either: * IMAP+TLS (TCP 143) / IMAPS (TCP 993) on imap.duckcorp.org * or POP3+TLS (TCP 110) / POP3S (TCP 995) on pop.duckcorp.org The IMAP protocol is recommended over POP3, as it provides many interesting features. If you want to download all your mails absolutely at home, loosing the ability to read your mail from anywhere on the planet, you can do that with IMAP too (look at your mail client settings). You can use our servers to send mails out too via smtp.duckcorp.org using: * SMTP+TLS (TCP 25) / SMTPS (TCP 465) * and SASL authentication === Using a Web Interface === A [https://webmail.duckcorp.org/ webmail interface] is available. == Antivirus and Antispam == Mails stored on our server are checked upon arrival for viruses and SPAMs. Mail redirected to a third party mailbox are not, not to mess with the strategy of the the final destination (which could arm learning greatly). Mails being viruses are suppressed automatically upon arrival. Once in a week, an extra antivirus check is done on all hosted mailboxes, to remove viruses not detected at the time it arrived (our antivirus database is updated daily), so you may see such mail disappear from your mailbox, don't fear. SPAMs are more difficult to detect, and it is an error-prone process, so we chose to use a learning software instead of using a global database. On the bright side of things, you would never loose mails and the software should be able to learn what is a SPAM from '''your''' point of view (which has proved to differ slightly between our users), but on the grey side you will have to teach him regularly to avoid errors. When your account is created, it acts like an empty headed body letting everything through, but after a few weeks of teaching it is able to recognize most of your habits and block a lot of annoying SPAM. === Web Interface === The web interface is an easy way to view your mail history, changes your settings, and more. It is available using this URL: https://spamfilter.duckcorp.org/ ==== User Settings ==== You can yourself setup a few parameters in the ''Preferences'' page of the [https://spamfilter.duckcorp.org/ web interface], mostly: * how the system should train: ** TEFT (''On every new message scanned by the filter''): useful to learn very quickly especially on a new mailbox or when you've got tons of spam on your addresses, but you need to train it regulary (daily is better) or it will learn wrong (very quickly too !) ** TOE (''Only when the filter makes a mistake''): slow learning, but if you don't have time for training very often or go on long holidays without internet access this mode will give you a stable behavior ** TUM (''Only with new data or if the filter makes a mistake''): trade-off between the two previous modes, learn quite fast and not too demanding, adapts better to new SPAMs then TOE * filter sensitivity: you can ask the system to be more or less aggressive * message handling: see [[#Delivery Mode|delivery mode]] below * ''Disable DSPAM filtering'': you may switch off filtering at your own risk We strongly recommend using TEFT with daily training for a few weeks then switching to TUM. If you need to go away for a long time, switching to TOE is recommended. Using the quarantine feature is also a safe choice, as the web interface is quite easy to use. === Delivery Mode === ==== Quarantine ==== With the ''message handling'' setting set to ''Quarantine the message'' (see [[#User Settings|user preferences]]), then your SPAMs will not go into your mailbox but stay in this stagging area. These mails are kept by the system until you decide their fate. Through the ''Quarantine'' page of the web interface, you can list these mails and: * free legitimate mails wrongly considered as SPAM by the system * delete real SPAMs if the system was right about them (freeing useful space) In this mode, you need to flush your quarantine once in a while. ==== Delivered with Special Header (default, recommended) ==== With the ''message handling'' setting set to ''Deliver the message normally with a X-DSPAM-Result header'', mails are delivered normally, but with a special field added to your mail headers (not always visible depending on your mail client and its configuration). This is quite handy if you prefer SPAMs arranged in a specific folder. You may use then the provided [[#Mail Filtering |filtering system]] to sort them properly, or configure your eMail client. ==== Delivered with Modified Subject (not recommended) ==== With the ''message handling'' setting set to ''Tag the Subject header with'', mails are delivered normally, but with a modified title to alert you this is a SPAM (which is a tad ugly). This mode is really not clean and not recommended, but it exist for historical purposes, so you might still use it if you really wish to. === Retraining === Teaching the system what is SPAM and HAM (non-SPAM) is called ''retraining''. ==== Retraining using the Special ''Junk'' Folder (default, recommended) ==== If you have of create a folder named ''Junk'', then it is automatically magic: * if you drop mail into it, it is automatically retrained as SPAM * if you move it out of it, it is automatically retrained as HAM * with time, certain old mails automatically expire, see below To use this folder properly, SPAMs '''must''' be delivered in the ''Junk'' folder automatically, so you can move them out in case of error. If using the default settings, you just need to subscribe to this folder in your mail software (this folder is always auto-created). If you are using different setting, you need to select the [[#Delivered with Special Header|delivery mode using a special header]], and use the provided [[#Mail Filtering|filtering system]] to drop them in the ''Junk'' folder ('''Do not use your mail software for this filtering, this is horribly inefficient and might alter the learning badly'''). Automatic expiration logic, based on delivery time (and not the mail timestamp): * deleted mails are purged after 1 day * read mails without an important flag are purge after 7 days * unread mails without an important flag are purge after 30 days If you use the ''incoming_spam'' [[#Global_Rules|global rule]], then SPAMs newly discovered by the system are flagged as important, which means these mails will never by purged until you review it and decide to delete them or mark them as not important. Custom rules might play with this flag and achieve an automatic selection. ==== Retraining via Web Interface ==== Use the [https://spamfilter.duckcorp.org/ web interface] to retrain from errors in the ''History'' page. If you are using the ''quarantine'', then freed mails will automatically be retrained as HAM. ==== Retraining via Mail ==== Resend SPAMs to [mailto:dc-spam@duckcorp.org dc-spam@duckcorp.org] and HAM (non-SPAM) to [mailto:dc-ham@duckcorp.org dc-ham@duckcorp.org]. {{warning}} PLEASE TAKE CARE to use the ''resend'' function of your mailer and never use ''forward'', which would result in '''yourself''' being considered as SPAM or HAM. == Mail Filtering == With your favourite mail client, you can probably filter your mails in proper folders already. Nevertheless, this can be an annoying operation: * blocking you mail client for a long time if you have to process plenty of mails * downloading each mail information, and sometimes content (depending on your filters), is lenghty too, and cost much bandwidth * syncing filters across your machines (home desktop, laptop, office machine…) is a pain in the ass * processing only when you're online prevents triggering actions in a timely manner (automatic redirect, vacation messages…), and running a machine 24/7 with a mail client polling new mails every 30s is not a solution We provide a much better way to do this using the [[wikipedia:Sieve_(mail_filtering_language)|SIEVE]] filters. Shortly, SIEVE is a language dedicated to expressing mail filters (also called ''rules''). Our server is able to process your mails according to these filters as soon as they arrive. You then don't have to care about them anymore, and may use light mail clients or webmails when you're not on your machine with your favourite software. === Rules Configuration === You can express sort/reject/vacation/… filters using these rules, as the capabilities are very rich. Several softwares support managing SIEVE rules: * Icedove/Thunderbird: *: using the SIEVE extension (in ''xul-ext-sieve'' Debian package), it provides a rules editor (for power-users) * Horde (Ingo): *: provides an easy to use web interface *: this webmail has been made available [https://webdesk.duckcorp.org/ here] * Squirrelmail: *: coupled with the Avelsieve extension, provides an easy to use web interface *: this webmail has been made available [https://webmail-sm.duckcorp.org/ here] * Roundcube: *: coupled with the sieverules extension, provides an easy to use web interface *: this webmail has been made available [https://webmail-rc.duckcorp.org/ here] * sieve-connect: *: provides a CLI to upload/download/activate your rules files *: this tool is available on [[Services/Shell|shell hosts]] (tell us if you know more software supporting this feature) To push your filters on the server, a dedicated protocol exists: MANAGESIEVE (TCP 4190) on ''sieve.duckcorp.org''. Our webmails are already configured to use it, but it you use sieve-connect from our hosts or your own mail software, you'll need these parameters. You can read more info about SIEVE here: * supported SIEVE features on our server: http://pigeonhole.dovecot.org/ * http://www.fastmail.fm/docs/sieve/ * http://sieve.info/ === Default Rules === The default settings (since 2112-02-11) are to use the global ''incoming_spam'' rule and the [[#Delivered with Special Header|delivery using a special header]], in order to provide a simple default configuration for most users. All other mails will end-up in your ''Inbox'' folder and you may then sort them by yourself. If you create your own rules, the default rules won't apply anymore, so power-users can replace the default behavior completely to achieve what they really need. === Global Rules === Global rules are provided to ease configuration on specific filters. They can easily be included in your own configuration. Available rules: * ''incoming_spam'': *: SPAMs will automatically be delivered in the ''Junk'' folder and marked as ''important'' *: you need to use the [[#Delivered with Special Header|delivery using a special header]] for this rule to have any effect If you write your own custom rules, here is an example on how to use one of them: require ["include"]; include :global "&lt;rule-name&gt;"; == Fetching eMails from an External Mailbox == {{todo}} == Shared/Public Folders == You may need to share mails or messages with friends or people you do stuff with (in a project or association). Depending on your needs, two solutions are possible: * share some of your own private folders, thus called ''shared folders'' * manage a special folder hierarchy, called ''public folders'' (even if they may not be accessible to everyone) *: if you need one, ask an administrator; the namespace name can be freely chosen but must be unambiguous and is subject to approval === Namespaces === Through IMAP, or our webmails internally using IMAP, it is possible to partition the folder hierarchy into ''namespaces''. Traditionally you are using the root namespace for your private folders. Additional namespaces can be created and will appear among your own folders or separate, depending on your mail client's choice of representation. To avoid name clashes, we decided to prefix all additional namespace names with a '''#'''. Since 2011-05-14, the following extra namespaces are created and reserved: * #Shared, containing all folders other users decided to share with you * #MilkyPond, containing public MP/DC informational mailboxes you may subscribe at will === Folders Permissions === Using IMAP, it is possible to setup rights (read only, write allowed…) to your own folders in order to share them with other users, or group of users. Public folders are owned by no-one, and must be created by the administrators. Once your request is accepted we will delegate its administration to your care. It can then can be managed like shared folders. === Software Support === Client mail softwares support: * Horde: *: support namespaces, shared folders configurable via ''Options->Share Folders'' menu but no ACLs for public folders * RoundCube: *: support namespaces, shared and public folders configurable via ''Settings->Folders'', selecting a folder then using the ''Sharing'' tab * Icedove/Thunderbird: *: support namespaces, shared and public folders configurable via folder selection and ''Tools->Imap-ACL'' menu action Most other softwares have namespace support only, so you should be able to use shared/public folders you have rights on but not configure them yourself (tell us if you know more software supporting this feature). == Limitations == === Maximum Mail Size === Mail you send or receive are limited to '''20MB'''. If you need to transmit much bigger data, then a mail transport is not appropriate, you'd better use a file sharing method instead. === Quotas === Even if it would be nice to live without it, we had to establish quotas to force people sort their mails out once in a while and delete useless things instead of leaving an ever-growing mess behind. The default quota is '''512MB''' which is not that big but should match needs of most users. This said, you may ask us for more and there's no reason we would refuse a reasonable demand. == Technical Details == This service is made using: * [http://www.postfix.org/ Postfix] * [http://dovecot.org/ Dovecot] * [http://dspam.sourceforge.net DSPAM] * [http://johannes.sipsolutions.net/Projects/dovecot-antispam dovecot-antispam] * [https://projects.duckcorp.org/projects/spoolinger Spoolinger] * [http://www.horde.org/ Horde] * [http://www.squirrelmail.org/ SquirrelMail] * [http://www.roundcube.net/ RoundCube] 53e25bd25b9cf7749c2be4d90a8bb9794c297253 0 33 548 455 2017-09-29T18:23:23Z Duck 2 typos wikitext text/x-wiki DuckCorp is built and maintained by volunteers, mostly with their own money. The services are totaly free of charge for all users, but you may wish to contribute to help us keep it working well and improve. == How to Contribute ? == You can help us with: * sponsoring: if you can host a machine and/or provide connectivity * equipements: see the list of possible improvements below * money: you can send us money which will be used in the association: ** by check (see the duckcorp.org whois for Duck's postal address, or ask him by mail or IRC) ** by Paypal to duck@duckcorp.org == What can you Contribute ? == Here are ideas on which to contribute: * [[DcExpenses#Regular_Expenses|regular expenses]] * [???] buy a new machine, to provide: VMs, more services redondancy, ... (needed hardware not yet evaluated, more on this later) * [~120€] add a battery backup unit for Toushirou's 3ware card (for more data security, as datacenters tends to be less and less reliable) * [??? (quite expensive)] change Orfeo's backplane to have 4 disks slot instead of 2, and add 2 new disks (in a new RAID 1 array), planned at least 120GB capacity (2.5″ 10000 RPM SAS, like the other ones) (can be bought anywhere, but proprietary braquets needed) == List of Previous Contributions == Only pure financial contributions are listed here; equipments and sponsored purchases are listed on the [[DcExpenses|DuckCorp expenses page]]. {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Amount !! Donor !! Comments |- | 2014-11-24 || 15€ || Clawfire || via Paypal, commission paid by donnor |- | 2014-07-14 || 15€ || Clawfire || via Paypal, commission paid by donnor |- | 2013-09-22 || 100$ USD || Damien || via Paypal => 69€ |- | 2011-01-10 || 500€ || AnonymousDonor1 || |- | 2010-05-16 || 42€ || Chloé || |} Note: early contributions in the CoinNetwork project are not taken into account, as most information is lost. f7c37dbfc419fc7757ae0ff472170047c732d0d6 553 548 2017-09-29T18:26:27Z Duck 2 update possible expense list wikitext text/x-wiki DuckCorp is built and maintained by volunteers, mostly with their own money. The services are totaly free of charge for all users, but you may wish to contribute to help us keep it working well and improve. == How to Contribute ? == You can help us with: * sponsoring: if you can host a machine and/or provide connectivity * equipements: see the list of possible improvements below * money: you can send us money which will be used in the association: ** by check (see the duckcorp.org whois for Duck's postal address, or ask him by mail or IRC) ** by Paypal to duck@duckcorp.org == What can you Contribute ? == Here are ideas on which to contribute: * [[DcExpenses#Regular_Expenses|regular expenses]] * [https://projects.duckcorp.org/issues/537 Toushirou and Orfeo are getting old] * [???] buy a new machine, to provide: VMs, more services redondancy, ... (needed hardware not yet evaluated, more on this later) == List of Previous Contributions == Only pure financial contributions are listed here; equipments and sponsored purchases are listed on the [[DcExpenses|DuckCorp expenses page]]. {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Amount !! Donor !! Comments |- | 2014-11-24 || 15€ || Clawfire || via Paypal, commission paid by donnor |- | 2014-07-14 || 15€ || Clawfire || via Paypal, commission paid by donnor |- | 2013-09-22 || 100$ USD || Damien || via Paypal => 69€ |- | 2011-01-10 || 500€ || AnonymousDonor1 || |- | 2010-05-16 || 42€ || Chloé || |} Note: early contributions in the CoinNetwork project are not taken into account, as most information is lost. a6e5e1570cc888596c379a2bd149576c305284e0 556 553 2017-09-29T18:31:41Z Duck 2 wikitext text/x-wiki DuckCorp is built and maintained by volunteers, mostly with their own money. The services are totaly free of charge for all users, but you may wish to contribute to help us keep it working well and improve. == How to Contribute ? == You can help us with: * sponsoring: if you can host a machine and/or provide connectivity * equipments: see the list of possible improvements below * money: you can send us money which will be used in the association: ** by check (see the duckcorp.org whois for Duck's postal address, or ask him by mail or IRC) ** by account transfer to Duck's account in France or Japan ** by Paypal to duck@duckcorp.org == What can you Contribute ? == Here are ideas on which to contribute: * [[DcExpenses#Regular_Expenses|regular expenses]] * [https://projects.duckcorp.org/issues/537 Toushirou and Orfeo are getting old] * [???] buy a new machine, to provide: VMs, more services redondancy, ... (needed hardware not yet evaluated, more on this later) == List of Previous Contributions == Only pure financial contributions are listed here; equipments and sponsored purchases are listed on the [[DcExpenses|DuckCorp expenses page]]. {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Amount !! Donor !! Comments |- | 2014-11-24 || 15€ || Clawfire || via Paypal, commission paid by donnor |- | 2014-07-14 || 15€ || Clawfire || via Paypal, commission paid by donnor |- | 2013-09-22 || 100$ USD || Damien || via Paypal => 69€ |- | 2011-01-10 || 500€ || AnonymousDonor1 || |- | 2010-05-16 || 42€ || Chloé || |} Note: early contributions in the CoinNetwork project are not taken into account, as most information is lost. 6eeb4392d6da016ca7cae513a8ab11760f1f9311 0 32 563 454 2017-09-29T18:53:43Z Duck 2 wikitext text/x-wiki Let's be transparent about money too. Pure financial contributions are not listed here, but in the [[DcDonation|donation page]]. == Regular Expenses == This does not account for external sponsorship, but contributions by members. {| class="wikitable" style="text-align: center; width: 100%;" ! Object !! Amount !! Sponsor !! Comments |- | DuckCorp DNS domain || ~7€/year (since 2014-07)<br/><del>~15€/year</del> || Duck |- | MilkyPond DNS domain || ~7€/year (since 2014-07)<br/><del>~15€/year</del> || Rtp |- | Toushirou's housing || 41.56€/month || Duck || collocation with Sam (considering network switch and APC powerswitch shared rack space) |} Note: private Internet connections involved in DuckCorp's services are not taken into account. Thorfinn was once hosted on a VM coupled with the Internet offer, this was not mentioned either. == Exceptional Expenses == Note: this does not take into account expenses before 2006 because most historical data were lost. Note: machines, VMs, or containers hosted privately and involved in Duckcorp's services are not fully taken into account as owners kindly provided for their well being; this includes (by order of appearance): * Elwing (Duck): services reduced starting from 2010 * Daneel (Duck): in need of resurrection * Korutopi (Arnau): currently experiencing difficulties * Nicecity (Pilou) === Improvement Expenses === {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Object !! Amount !! Sponsor !! Comments |- | 2012-05-09 || more memory for Toushirou (2*2GB) || ~60€ || Pilou || PC2-6400 instead of PC2-5300/5400 (see replacement memory details) |- | 2007-10 || replacement server (Orfeo-NG) || 1210€ || Duck || Sun Fire X4100 |- | 2007-05 || new server (Toushirou) || 1709.08€ || Duck || Supermicro PDSMI+ / Core 2 Duo E6600 / 2GB PC5400 / 3ware 9550SX4LP / 4x HD SATA II 250GB |} === Failure Expenses === {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Object !! Amount !! Sponsor !! Comments |- | 2017-??-?? || disks replacement || ???JPY || Arnau || still not stable, controller suspected to have problems |- | 2010-05-22 || replacement memory for Toushirou (2*2GB) || 105€ || Duck || PC2-5300/5400 2*2GB memory in a correct brand could not be found anymore, so we had to take PC2-6400 instead |- | 2010-01-06 || spare disk || 73€ || Duck || avoided tragedy when both disks in Daneel died at one week interval |- | 2007-09-29 || replacement server (Daneel-ng) || 534.90€ || Duck || machine too old and previous disk died horribly |- | 2006-01 || 300GB HD for Daneel (backup) || || AnonymousDonor1 || replaced since then |} === Other Expenses === {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Object !! Amount !! Sponsor !! Comments |- | 2010-06-29 || taxi || 26.20€ || Duck || Nerim bought Sivit, moving Toushirou to their new suite at Equinix PA3 (CBV->STD) |} 19907334ef6b2a4b9cad36ae4b91aa750017151f 0 47 568 448 2017-09-29T18:56:16Z Duck 2 wikitext text/x-wiki Here is the list of '''current''' DuckCorp's administrators. These are the only people which have full access to the system (even if we may delegate nonsensitive things to trusted parties, but you'll always be warned of such changes). == Active administrators == * Duck: *: Full Name: Marc Dequènes *: GPG Key Fingerprint: 7297 2A83 E526 453D F288 5F81 55E9 F9F7 AC1C 443F *: (old: 6ADD 5093 AC6D 1072 C912 9000 B1CC D972 9026 7086) * Pilou: *: Full Name: Pierre-Louis Bonicoli *: GPG Key Fingerprint: 2B1E DB5E ABEB 0483 AA50 15B3 13FA 63E9 3F25 BB1F == Fallback administrators == * Arnau: *: Full Name: Arnaud Fontaine *: GPG Key Fingerprint: 43B5 1C2A AAD3 E0D4 9ACF 8F59 97C2 C6AB 313C 7B03 *: (old: D792 B8A5 A567 B001 C342 2613 BDF2 A220 5E36 19D3) da334106184cfee0195b71805500fe0c8c466e9f 0 38 571 186 2017-09-29T18:57:19Z Duck 2 /* Usage */ wikitext text/x-wiki We are working to give users more control on their own resources, but it is a difficult task. We are working on a tool, but it is still heavily work in progress. It works correctly, but its skill is currently limited to a few tasks. == Requirements == This tool is accessible through a mail interface (later, we might add other types of frontends), and does care about security and privacy. You need to get a GPG/PGP key, and get it registered in a safe manner in our database (contact an administrator for this). If you hate english, you might also ask an administration to change your language preferences. The mail should be RFC3156-compliant, and should not use the combined method (inline signing, like with mailcrypt) described in chapter 6.2 of this RFC (not supported yet). == Usage == Once it is done, you just need to send a signed mail to "MilkyPond Administration Officer" <banya@milkypond.org> with a list of commands in the body. Empty lines and comments (lines starting with "#") are ignored. The subject is purely informational, for you to identify the reply to the corresponding demand. As you may send '''secret''' information in the mail, you would like to hide it. Use Banya's key (fingerprint: D0CC BBA5 5460 719D 515C 11E6 E770 C685 EF41 0567), signed by the DuckCorp Administrators, for encryption. This is an optional, but recommended, feature. == Available Languages == * en * fr The setting follow the RFC 2616 Accept-Language field syntax. == Available Commands == === DNS management === Beware to properly update the serial! Available commands: * DNS INFO : to get the list of DNS zones you can manage (and probably more in the future) * DNS GET ZONE &lt;zone&gt; : to get the DNS &lt;zone&gt; content (attached in the reply) * DNS SET ZONE &lt;zone&gt; @&lt;i&gt; : to replace the current DNS &lt;zone&gt; content with the &lt;i&gt;st/nd/rd/th attachment (text/plain accepted only) : the zone syntax is checked before replacement Notes for signed zones: * the support for signed zone is basic, no specific information or possibility to setup any parameter yet * the fetched zone (with the GET command) does not reflect the real serial, as the signer process update the serial automatically when resigning the zone, so you need to ask for the current serial with the following command: host -t soa <zone> == Project Info == Please see https://projects.duckcorp.org/projects/cyborghood. b427d4498b7df74bb105b7523ffd63e23a6e5cb1 574 571 2017-09-29T18:57:58Z Duck 2 Protected "[[UserMagicalInterface]]" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite)) wikitext text/x-wiki We are working to give users more control on their own resources, but it is a difficult task. We are working on a tool, but it is still heavily work in progress. It works correctly, but its skill is currently limited to a few tasks. == Requirements == This tool is accessible through a mail interface (later, we might add other types of frontends), and does care about security and privacy. You need to get a GPG/PGP key, and get it registered in a safe manner in our database (contact an administrator for this). If you hate english, you might also ask an administration to change your language preferences. The mail should be RFC3156-compliant, and should not use the combined method (inline signing, like with mailcrypt) described in chapter 6.2 of this RFC (not supported yet). == Usage == Once it is done, you just need to send a signed mail to "MilkyPond Administration Officer" <banya@milkypond.org> with a list of commands in the body. Empty lines and comments (lines starting with "#") are ignored. The subject is purely informational, for you to identify the reply to the corresponding demand. As you may send '''secret''' information in the mail, you would like to hide it. Use Banya's key (fingerprint: D0CC BBA5 5460 719D 515C 11E6 E770 C685 EF41 0567), signed by the DuckCorp Administrators, for encryption. This is an optional, but recommended, feature. == Available Languages == * en * fr The setting follow the RFC 2616 Accept-Language field syntax. == Available Commands == === DNS management === Beware to properly update the serial! Available commands: * DNS INFO : to get the list of DNS zones you can manage (and probably more in the future) * DNS GET ZONE &lt;zone&gt; : to get the DNS &lt;zone&gt; content (attached in the reply) * DNS SET ZONE &lt;zone&gt; @&lt;i&gt; : to replace the current DNS &lt;zone&gt; content with the &lt;i&gt;st/nd/rd/th attachment (text/plain accepted only) : the zone syntax is checked before replacement Notes for signed zones: * the support for signed zone is basic, no specific information or possibility to setup any parameter yet * the fetched zone (with the GET command) does not reflect the real serial, as the signer process update the serial automatically when resigning the zone, so you need to ask for the current serial with the following command: host -t soa <zone> == Project Info == Please see https://projects.duckcorp.org/projects/cyborghood. b427d4498b7df74bb105b7523ffd63e23a6e5cb1 0 66 584 381 2017-09-30T13:19:21Z Duck 2 wikitext text/x-wiki {{Template:Service | description = A project management and issue tracking software is a tool intended to help organize projects (not only computer science related projects), from various aspects: scheduling, planning, communication, tracking, documentation… | prerequisite = You may need to ask a project administrator for membership to access certain projects and resources, but can already login with your global account. A few projects may be public, which means you (or outsiders) can access most information without authenticating (and maybe even add some). | account = global-reg | ipv6 = true | security_notes = This service is secure. }} == Access == Use the following URL and login: https://projects.duckcorp.org/ == Managing a Project == Ask an administrator if you need a project created. You will be set a Manager and will be able to manage your project settings and members. This can be coupled with a [[Services/VCS|VCS access]]. == Documentation == * [http://www.redmine.org/guide Help Page] * generic documentation on [[wikipedia:Project_management_software|Project management software]] == Technical Details == This service is made using: * [http://www.redmine.org/ Redmine] b3c36e681da472ff96dd27a7d1ac1df3e1acd947 587 584 2017-09-30T13:19:49Z Duck 2 /* Managing a Project */ wikitext text/x-wiki {{Template:Service | description = A project management and issue tracking software is a tool intended to help organize projects (not only computer science related projects), from various aspects: scheduling, planning, communication, tracking, documentation… | prerequisite = You may need to ask a project administrator for membership to access certain projects and resources, but can already login with your global account. A few projects may be public, which means you (or outsiders) can access most information without authenticating (and maybe even add some). | account = global-reg | ipv6 = true | security_notes = This service is secure. }} == Access == Use the following URL and login: https://projects.duckcorp.org/ == Managing a Project == Ask an administrator if you need a project created. You will be set as Manager and will be able to manage your project settings and members. This can be coupled with a [[Services/VCS|VCS access]]. == Documentation == * [http://www.redmine.org/guide Help Page] * generic documentation on [[wikipedia:Project_management_software|Project management software]] == Technical Details == This service is made using: * [http://www.redmine.org/ Redmine] ec141deca435d03d1cbfc9b4f69c2e4394746fe9 0 50 602 438 2017-09-30T13:31:51Z Duck 2 /* Access */ wikitext text/x-wiki {{Template:Service | description = Remote [[wikipedia:Shell_(computing)|shell]] to a DuckCorp machine. | prerequisite = You need to ask an administrator for an account, but we need to know you well-enough to ensure you are trustable. This is '''not''' a VIP requirement, but such an access can be very dangerous and we don't know any other way to avoid a disaster, sorry. You also need to provide a RSA/DSA public key (see ''ssh-keygen''). | account = global-reg | ipv6 = true | security_notes = This service is secure. }} == Access == Via SSH with a RSA/ECDSA/ED25519 key on the following hosts: (ED25519 recommended) * thorfinn.duckcorp.org (prefered for lengthy sessions, like screens) * toushirou.duckcorp.org (mostly useful to manage Web/FTP data) Via SSH+[http://mosh.mit.edu/ Mosh], with the same hosts and conditions defined above. On Debian you can use the ''mosh'' package to get the client application and do ''mosh &lt;server&gt;''. On Android, the [http://dan.drown.org/android/mosh/ patched IrssiConnectbot from ddrown] is known to work as well. === Locked behind a firewall === If you are obliged to go through a firewall (at work for eg), you can try a few things to through and end-up on Toushirou (and can bounce on Thorfinn then). First, if you know there is a proxy, or direct access does not work, you may be able to find the firewall host and port in the browser configuration. If there is none, then the proxy may be transparent (hidden) and you can try a direct SSH access using ''portal.duckcorp.org'' on port ''443''. If it does not work, you can try using a tool to wrap SSH through the firewall. From a terminal the ''corkscrew'' (Debian has a package of the same name) tool car be used with the following SSH configuration (in ''~/.ssh/config''): Host portal.duckcorp.org ProxyCommand /usr/bin/corkscrew &lt;proxy-host&gt; &lt;proxy-port&gt; %h %p and connect with: ssh portal.duckcorp.org == Available Resources == The following resources are available and will remain until we advertise a scheduled removal. If you miss something you can send us a request. === Locales === {{warning}} warning for Mosh users: Mosh only supports UTF-8 locales * br_FR.UTF-8 * en_GB.UTF-8 * en_US.UTF-8 * fr_FR.UTF-8 * ja_JP.EUC-JP * ja_JP.UTF-8 === Shells === * dash * bash * zsh * ksh * tcsh === Programs === * aspell (with same support as system locales) * dict * emacs * graphviz * imagemagick * irssi (with plugins and scripts) * latex (full TeXlive) * p7zip * rsync * screen * sieve-connect * unar * unison * vim * w3m * weechat (with plugins and scripts) Additional tools: * [[Services/VCS|VCS tools]] == Technical Details == This service is made using: * [http://www.openssh.org/ OpenSSH] * [http://mosh.mit.edu/ Mosh] 1ed7d5a3e9e07356b35cc0c0946d32fa140b7e6b 607 602 2017-09-30T13:37:40Z Duck 2 /* Available Resources */ wikitext text/x-wiki {{Template:Service | description = Remote [[wikipedia:Shell_(computing)|shell]] to a DuckCorp machine. | prerequisite = You need to ask an administrator for an account, but we need to know you well-enough to ensure you are trustable. This is '''not''' a VIP requirement, but such an access can be very dangerous and we don't know any other way to avoid a disaster, sorry. You also need to provide a RSA/DSA public key (see ''ssh-keygen''). | account = global-reg | ipv6 = true | security_notes = This service is secure. }} == Access == Via SSH with a RSA/ECDSA/ED25519 key on the following hosts: (ED25519 recommended) * thorfinn.duckcorp.org (prefered for lengthy sessions, like screens) * toushirou.duckcorp.org (mostly useful to manage Web/FTP data) Via SSH+[http://mosh.mit.edu/ Mosh], with the same hosts and conditions defined above. On Debian you can use the ''mosh'' package to get the client application and do ''mosh &lt;server&gt;''. On Android, the [http://dan.drown.org/android/mosh/ patched IrssiConnectbot from ddrown] is known to work as well. === Locked behind a firewall === If you are obliged to go through a firewall (at work for eg), you can try a few things to through and end-up on Toushirou (and can bounce on Thorfinn then). First, if you know there is a proxy, or direct access does not work, you may be able to find the firewall host and port in the browser configuration. If there is none, then the proxy may be transparent (hidden) and you can try a direct SSH access using ''portal.duckcorp.org'' on port ''443''. If it does not work, you can try using a tool to wrap SSH through the firewall. From a terminal the ''corkscrew'' (Debian has a package of the same name) tool car be used with the following SSH configuration (in ''~/.ssh/config''): Host portal.duckcorp.org ProxyCommand /usr/bin/corkscrew &lt;proxy-host&gt; &lt;proxy-port&gt; %h %p and connect with: ssh portal.duckcorp.org == Available Resources == The following resources are available and will remain until we advertise a scheduled removal. If you miss something you can send us a request. === Locales === {{warning}} warning for Mosh users: Mosh only supports UTF-8 locales * br_FR.UTF-8 * en_GB.UTF-8 * en_US.UTF-8 * fr_FR.UTF-8 * ja_JP.EUC-JP * ja_JP.UTF-8 === Shells === * dash * bash * zsh * ksh * tcsh === Programs === * aspell (with same support as system locales) * dict * emacs * graphviz * imagemagick * irssi (with plugins and scripts) * latex (full TeXlive on Thorfinn, limited installation on Toushirou) * p7zip * rsync * screen * sieve-connect * unar * unison * vim * w3m * weechat (with plugins and scripts) (and probably a few others we forgot to mention) Additional tools: * [[Services/VCS|VCS tools]] === Spaces === The following spaces are available: * your home * ask an administrator if you need a project-specific space in /srv/projects/ on Toushirou * ask an administrator if you need a space for public VCS repositories on _vcs.duckcorp.org_ (Toushirou) * ask an administrator if you need a space (personal or project) on the public FTP (private FTP spaces are ***OBSOLETE***) == Technical Details == This service is made using: * [http://www.openssh.org/ OpenSSH] * [http://mosh.mit.edu/ Mosh] 2881995b3de9ad956d3f70b77b9433975333bafb 0 51 610 337 2017-09-30T13:39:50Z Duck 2 /* Full Hosting */ wikitext text/x-wiki {{Template:Service | description = Available services: * full hosting (MX1) on our servers * fallback retention (MX2) on our servers or, at your choice, partner servers (currently via Hivane) | prerequisite = You need to buy a domain from a [[wikipedia:Domain_name_registrar|registrar]], setup a DNS (can be [[Services/DNS|hosted here]] too), and ask an administrator to configure this service. | account = global-reg | ipv6 = true | security_notes = See the [[Services/Mail|eMail service]]'s security notes. }} == Full Hosting == You can have multiple email addresses which can be: * real mailboxes * redirections towards internal or third party addresses * wildcards (***DISCOURAGED***, bring a lot of SPAM in) based on your domains or sub-domains. Have a look at our [[Services/Mail|complete set of mail services]]. == Fallback retention == The current retention period on our servers is 2 weeks, but can be temporary or permanently increased if needed. Mails flowing back to your primary server can be protected using TLS with certificate verification if you wish. Antivirus and antispam filtering are not applied to relayed mails, so we do not mess with your prefered strategy on your primary server, nevertheless basic checks (EHLO, DNS…) and RBL scoring are done to avoid accepting tons of SPAMs. == Technical Details == See the [[Services/Mail#Technical_Details|eMail service page]]. 6210b13de72e8f045094b9ef71f13d9c3f007742 0 71 617 419 2017-09-30T13:59:43Z Duck 2 /* Access */ wikitext text/x-wiki {{Template:Service | description = Minecraft-like game, which is an old-looking building game | prerequisite = | account = local | ipv6 = false | security_notes = This service does not contain sensitive data. }} == Access == Install the Minetest client, like this on Debian: apt-get install minetest '''NEWCOMERS''' Ask an administrator for the first-time password. Login using the instructions below, a username of your choice, and this password. In game, you can then set your personal password in the menu (press ESC). When you login the next time, use your personal password instead. Launch the game and connect to the server using: * hostname: minetest.duckcorp.org * port: UDP 30000 (default) * username * password == Documentation == * [http://wiki.minetest.net/Main_Page Community Wiki] == Technical Details == This service is made using: * [http://www.minetest.net/ Minetest] 1a133093f2796c4269e6ba7cdd73d445890191fe 0 138 622 2017-09-30T14:38:55Z Duck 2 Created page with "{{Template:Service | description = SQL Databases, for websites and various applications. | prerequisite = | account = global-reg | ipv6 = true | security_notes = Access to the..." wikitext text/x-wiki {{Template:Service | description = SQL Databases, for websites and various applications. | prerequisite = | account = global-reg | ipv6 = true | security_notes = Access to the databases is secure. }} == Access == === Command Line Interface === ==== PostgreSQL ==== You need a client CLI tool to connect to the database. On Debian you can install it easily using: apt-get install postgresql-client You can login to the following nodes: * db-postgresql-1.duckcorp.org To learn how to use this tool, please look at the [https://www.postgresql.org/docs/9.6/static/tutorial-accessdb.html]. ==== MariaDB (MySQL-compatible) ==== You need a client CLI tool to connect to the database. On Debian you can install it easily using: apt-get install mariadb-client (on older systems you can install the _mysql-client_ package instead) You can login to the following nodes: * db-mysql-1.duckcorp.org mysql -u &lt;user&gt; &lt;database&gt; To learn how to use this tool, please look at the [https://mariadb.com/kb/en/library/a-mariadb-primer/ documentation]. === Web SQL Manager === Each database can be accessed and managed using a (simpler) web interface: https://db.duckcorp.org/ == Technical Details == This service is made using: * [PostgreSQL https://www.postgresql.org/] * [MariaDB https://mariadb.org/] 6c02a854f5cddf1f9a4d50da9de3bddbfb6ebe0a 0 138 629 622 2017-09-30T14:54:46Z Duck 2 wikitext text/x-wiki {{Template:Service | description = SQL Databases, for websites and various applications. | prerequisite = | account = global-reg | ipv6 = true | security_notes = Access to the databases is secure. }} == Access == === Command Line Interface === ==== PostgreSQL ==== You need a client CLI tool to connect to the database. On Debian you can install it easily using: apt-get install postgresql-client You can login to the following nodes: * db-postgresql-1.duckcorp.org To learn how to use this tool, please look at the [https://www.postgresql.org/docs/9.6/static/tutorial-accessdb.html]. ==== MariaDB (MySQL-compatible) ==== You need a client CLI tool to connect to the database. On Debian you can install it easily using: apt-get install mariadb-client (on older systems you can install the _mysql-client_ package instead) You can login to the following nodes: * db-mysql-1.duckcorp.org mysql -u &lt;user&gt; &lt;database&gt; To learn how to use this tool, please look at the [https://mariadb.com/kb/en/library/a-mariadb-primer/ documentation]. === Web SQL Manager === Each database can be accessed and managed using a (simpler) web interface: https://db.duckcorp.org/ == User Accounts == User Accounts are handy to manage your databases. This is handy to prepare and alter schema, repair problems, and do operations the application accounts are not allowed to do. You need to ask an administrator to create your account. ==== PostgreSQL ==== You can connect using your LDAP credentials. ==== MariaDB (MySQL-compatible) ==== You need separate credentials to log into your account. We [https://projects.duckcorp.org/issues/58 plan to add LDAP support]. == Application Accounts & Databases == To ensure security each project of one or more related database will use a specific account to connect. You need to ask an administrator to create application accounts. It is recommended, if the application support it, to restrict the application account permissions on the database; for example to disallow modification of the database schema. These operations are only meant for migrations and maintenance and should be done using your user account, or a dedicated administration application account. == Technical Details == This service is made using: * [PostgreSQL https://www.postgresql.org/] * [MariaDB https://mariadb.org/] f8648c46f2937415de6e0d802b7d99217eb6f160 0 149 644 2017-10-01T14:05:19Z Duck 2 Created page with "{{Template:Service | description = A few VCS tools are available to DC users. | prerequisite = You would need a shell access, FTP access or VCS repository | account = global-..." wikitext text/x-wiki {{Template:Service | description = A few VCS tools are available to DC users. | prerequisite = You would need a shell access, FTP access or VCS repository | account = global-reg | ipv6 = true | security_notes = This service is secure. }} == Access == Web hosting happens on Toushirou. Available methods: * using a [[Services/Shell|shell account]] is you already have one; if not, you might ask for one, but this is not easily granted for security reasons * using a [[Services/VCS|VCS repository]] * using an [[Services/FTP|FTP account]] is also possible but we try to deprecate this method. == Available Languages == == Website Generation == == Technical Details == This service is made using: * [https://httpd.apache.org/ Apache Httpd] deeeb286c1031fbffdd1202df1d41feb95ca1039 649 644 2017-10-01T14:32:40Z Duck 2 wikitext text/x-wiki {{Template:Service | description = Web sites and applications hosting for DC users. | prerequisite = You would need a shell access, FTP access or VCS repository | account = global-reg | ipv6 = true | security_notes = This service is secured using HTTPS. The remaining non-HTTPS websites are being upgraded. }} == Access == Web hosting happens on Toushirou. Available methods: * using a [[Services/Shell|shell account]] is you already have one; if not, you might ask for one, but this is not easily granted for security reasons * using a [[Services/VCS|VCS repository]] * using an [[Services/FTP|FTP account]] is also possible but we try to deprecate this method. == Available Protocols == All websites are using HTTPS, with HTTP redirecting to HTTPs for security and privacy. Except if there is a very good reason, HTTP-only or without redirection is not an option. All websites are also available via HTTP2, with the only exception being sites relying on Apache indexes because of [https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850947 this bug]. == Available Languages == == Website Generation == == Technical Details == This service is made using: * [https://httpd.apache.org/ Apache Httpd] c8aca132086f60afaa592373c9971fa3f98519dd 652 649 2017-10-01T14:38:52Z Duck 2 /* Available Languages */ wikitext text/x-wiki {{Template:Service | description = Web sites and applications hosting for DC users. | prerequisite = You would need a shell access, FTP access or VCS repository | account = global-reg | ipv6 = true | security_notes = This service is secured using HTTPS. The remaining non-HTTPS websites are being upgraded. }} == Access == Web hosting happens on Toushirou. Available methods: * using a [[Services/Shell|shell account]] is you already have one; if not, you might ask for one, but this is not easily granted for security reasons * using a [[Services/VCS|VCS repository]] * using an [[Services/FTP|FTP account]] is also possible but we try to deprecate this method. == Available Protocols == All websites are using HTTPS, with HTTP redirecting to HTTPs for security and privacy. Except if there is a very good reason, HTTP-only or without redirection is not an option. All websites are also available via HTTP2, with the only exception being sites relying on Apache indexes because of [https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850947 this bug]. == Available Languages == We currently support these langages: * Python 2.7 and 3.5, and WSGI applications * Ruby 2.3, and Rack-enabled (Rails…) applications * Perl 5.24 * PHP 7.0 * NodeJS 4.8 applications Java applications are not an option, but we may consider other languages though. If you need libraries and tools installed, please contact an administrator. == Website Generation == == Technical Details == This service is made using: * [https://httpd.apache.org/ Apache Httpd] ee00078c7599a3f3ce7d9030b3fb7f8ea795e044 655 652 2017-10-01T14:46:37Z Duck 2 /* Website Generation */ wikitext text/x-wiki {{Template:Service | description = Web sites and applications hosting for DC users. | prerequisite = You would need a shell access, FTP access or VCS repository | account = global-reg | ipv6 = true | security_notes = This service is secured using HTTPS. The remaining non-HTTPS websites are being upgraded. }} == Access == Web hosting happens on Toushirou. Available methods: * using a [[Services/Shell|shell account]] is you already have one; if not, you might ask for one, but this is not easily granted for security reasons * using a [[Services/VCS|VCS repository]] * using an [[Services/FTP|FTP account]] is also possible but we try to deprecate this method. == Available Protocols == All websites are using HTTPS, with HTTP redirecting to HTTPs for security and privacy. Except if there is a very good reason, HTTP-only or without redirection is not an option. All websites are also available via HTTP2, with the only exception being sites relying on Apache indexes because of [https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850947 this bug]. == Available Languages == We currently support these langages: * Python 2.7 and 3.5, and WSGI applications * Ruby 2.3, and Rack-enabled (Rails…) applications * Perl 5.24 * PHP 7.0 * NodeJS 4.8 applications Java applications are not an option, but we may consider other languages though. If you need libraries and tools installed, please contact an administrator. == Website Database == SQL databases are available, please look at this [[Services/SQL|corner of the documentation]]. If the database node is hosted on Toushirou, then you may use UNIX socket access for increased performances. == Website Generation == If you have shell access, then you can handle this yourself, setup hooks/crontabs/… as needed. Contact us if you need help. If you don't have a shell access and your application needs to be generated, please ask an administrator. It may be possible to use a hook or crontab (not involving uncontrolled code for security reasons). == Technical Details == This service is made using: * [https://httpd.apache.org/ Apache Httpd] 95100bfc7dff745435395038a84aec7f08b75ab8 658 655 2017-10-01T14:52:25Z Duck 2 wikitext text/x-wiki {{Template:Service | description = Web sites and applications hosting for DC users. | prerequisite = You would need a shell access, FTP access or VCS repository | account = global-reg | ipv6 = true | security_notes = This service is secured using HTTPS. The remaining non-HTTPS websites are being upgraded. }} == Access == Web hosting happens on Toushirou. Available methods: * using a [[Services/Shell|shell account]] is you already have one; if not, you might ask for one, but this is not easily granted for security reasons * using a [[Services/VCS|VCS repository]] * using an [[Services/FTP|FTP account]] is also possible but we try to deprecate this method. == Available Protocols == All websites are using HTTPS, with HTTP redirecting to HTTPs for security and privacy. Except if there is a very good reason, HTTP-only or without redirection is not an option. All websites are also available via HTTP2, with the only exception being sites relying on Apache indexes because of [https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850947 this bug]. == Available Languages == We currently support these langages: * Python 2.7 and 3.5, and WSGI applications * Ruby 2.3, and Rack-enabled (Rails…) applications * Perl 5.24 * PHP 7.0 * NodeJS 4.8 applications Java applications are not an option, but we may consider other languages though. If you need libraries and tools installed, please contact an administrator. == Website Database == SQL databases are available, please look at this [[Services/SQL|corner of the documentation]]. If the database node is hosted on Toushirou, then you may use UNIX socket access for increased performances. == Website Generation == If you have shell access, then you can handle this yourself, setup hooks/crontabs/… as needed. Contact us if you need help. If you don't have a shell access and your application needs to be generated, please ask an administrator. It may be possible to use a hook or crontab (not involving uncontrolled code for security reasons). == Website Stats == Visitors statistics and various other metrics can be made available; this is not activated by default though, please contact an administrator if you wish so. Then you would be able to access the [https://webstats.duckcorp.org/ Stats service] using your LDAP credentials. == Technical Details == This service is made using: * [https://httpd.apache.org/ Apache Httpd] * [https://piwik.org/ Piwik] fb0f405edf315985ab25d116bcffbccc31fa75f3 759 658 2018-12-19T07:32:56Z Duck 2 wikitext text/x-wiki {{Template:Service | description = Web sites and applications hosting for DC users. | prerequisite = You would need a shell access, FTP access or VCS repository | account = global-reg | ipv6 = true | security_notes = This service is secured using HTTPS. The remaining non-HTTPS websites are being upgraded. }} == Access == Web hosting happens on Toushirou. Available methods: * using a [[Services/Shell|shell account]] is you already have one; if not, you might ask for one, but this is not easily granted for security reasons * using a [[Services/VCS|VCS repository]] * using an [[Services/FTP|FTP account]] is also possible but we try to deprecate this method. == Available Protocols == All websites are using HTTPS, with HTTP redirecting to HTTPs for security and privacy. Except if there is a very good reason, HTTP-only or without redirection is not an option. All websites are also available via HTTP2, with the only exception being sites relying on Apache indexes because of [https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850947 this bug]. == Available Languages == We currently support these langages: * Python 2.7 and 3.5, and WSGI applications * Ruby 2.3, and Rack-enabled (Rails…) applications * Perl 5.24 * PHP 7.0 * NodeJS 4.8 applications Java applications are not an option, but we may consider other languages though. If you need libraries and tools installed, please contact an administrator. == Website Database == SQL databases are available, please look at this [[Services/SQL|corner of the documentation]]. If the database node is hosted on Toushirou, then you may use UNIX socket access for increased performances. == Website Generation == If you have shell access, then you can handle this yourself, setup hooks/crontabs/… as needed. Contact us if you need help. If you don't have a shell access and your application needs to be generated, please ask an administrator. It may be possible to use a hook or crontab (not involving uncontrolled code for security reasons). == Technical Details == This service is made using: * [https://httpd.apache.org/ Apache Httpd] * [https://piwik.org/ Piwik] 556e8fbc218c5139ab5a410b0aec7f81a66b4199 803 759 2020-04-08T04:31:12Z Duck 2 /* Available Languages */ wikitext text/x-wiki {{Template:Service | description = Web sites and applications hosting for DC users. | prerequisite = You would need a shell access, FTP access or VCS repository | account = global-reg | ipv6 = true | security_notes = This service is secured using HTTPS. The remaining non-HTTPS websites are being upgraded. }} == Access == Web hosting happens on Toushirou. Available methods: * using a [[Services/Shell|shell account]] is you already have one; if not, you might ask for one, but this is not easily granted for security reasons * using a [[Services/VCS|VCS repository]] * using an [[Services/FTP|FTP account]] is also possible but we try to deprecate this method. == Available Protocols == All websites are using HTTPS, with HTTP redirecting to HTTPs for security and privacy. Except if there is a very good reason, HTTP-only or without redirection is not an option. All websites are also available via HTTP2, with the only exception being sites relying on Apache indexes because of [https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850947 this bug]. == Available Languages == We currently support these langages: * Python 2.7 and 3.7, and WSGI applications * Ruby 2.5, and Rack-enabled (Rails…) applications * Perl 5.28 * PHP 7.3 * NodeJS 10.15 applications Java applications are not an option, but we may consider other languages though. If you need libraries and tools installed, please contact an administrator. == Website Database == SQL databases are available, please look at this [[Services/SQL|corner of the documentation]]. If the database node is hosted on Toushirou, then you may use UNIX socket access for increased performances. == Website Generation == If you have shell access, then you can handle this yourself, setup hooks/crontabs/… as needed. Contact us if you need help. If you don't have a shell access and your application needs to be generated, please ask an administrator. It may be possible to use a hook or crontab (not involving uncontrolled code for security reasons). == Technical Details == This service is made using: * [https://httpd.apache.org/ Apache Httpd] * [https://piwik.org/ Piwik] ae11a2540d18f10915adaedea4896b7694e3acc9 804 803 2020-04-08T04:31:26Z Duck 2 /* Technical Details */ wikitext text/x-wiki {{Template:Service | description = Web sites and applications hosting for DC users. | prerequisite = You would need a shell access, FTP access or VCS repository | account = global-reg | ipv6 = true | security_notes = This service is secured using HTTPS. The remaining non-HTTPS websites are being upgraded. }} == Access == Web hosting happens on Toushirou. Available methods: * using a [[Services/Shell|shell account]] is you already have one; if not, you might ask for one, but this is not easily granted for security reasons * using a [[Services/VCS|VCS repository]] * using an [[Services/FTP|FTP account]] is also possible but we try to deprecate this method. == Available Protocols == All websites are using HTTPS, with HTTP redirecting to HTTPs for security and privacy. Except if there is a very good reason, HTTP-only or without redirection is not an option. All websites are also available via HTTP2, with the only exception being sites relying on Apache indexes because of [https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850947 this bug]. == Available Languages == We currently support these langages: * Python 2.7 and 3.7, and WSGI applications * Ruby 2.5, and Rack-enabled (Rails…) applications * Perl 5.28 * PHP 7.3 * NodeJS 10.15 applications Java applications are not an option, but we may consider other languages though. If you need libraries and tools installed, please contact an administrator. == Website Database == SQL databases are available, please look at this [[Services/SQL|corner of the documentation]]. If the database node is hosted on Toushirou, then you may use UNIX socket access for increased performances. == Website Generation == If you have shell access, then you can handle this yourself, setup hooks/crontabs/… as needed. Contact us if you need help. If you don't have a shell access and your application needs to be generated, please ask an administrator. It may be possible to use a hook or crontab (not involving uncontrolled code for security reasons). == Technical Details == This service is made using: * [https://httpd.apache.org/ Apache Httpd] bc0848a8b7727a34755af691aa655af562042c67 0 75 663 599 2017-10-01T15:31:36Z Duck 2 wikitext text/x-wiki {{Template:Service | description = A few VCS tools are available to DC users. | prerequisite = Write access is currently limited to people having a shell account. No prerequisite for read access. | account = global-reg | ipv6 = true | security_notes = This service is secure. }} == Access == Use the following URL to access public repositories: https://vcs.duckcorp.org/ Various VCS are possible: git, Mercurial, SVN, Bazaar… If you have [[Services/Shell|shell access]], public repositories are also available in ''/srv/vcs/'' on ''vcs.duckcorp.org'' == Managing a Repository == If you have [[Services/Shell|shell access]]: * ask an administrator if you need a space for public repositories * you can create private repositories at will in your home directory * ask an administrator if you need a project-specific space in ''/srv/projects/'' on ''vcs.duckcorp.org'' to store the project private repositories in it For the following steps, ask an administrator if you don't have shell access. === Git === A Git repository needs to be a ''bare'' repository, created like this: mkdir myrepo.git cd myrepo.git git init --bare A public repository should have a proper short description defined. Either edit the ''description'' file into the bare repository. To activate access via the Git protocol, you need to activate it: cd myrepo.git touch git-daemon-export-ok To activate access via the HTTP protocol, you need to enable updating the Git internal references: cd myrepo.git mv hooks/post-update.sample hooks/post-update Access methods sumup: * Direct SSH access: <tt>ssh://login@vcs.duckcorp.org/srv/vcs/git/...</tt> * [https://vcs-git.duckcorp.org/ Git via HTTP (read-only)] * Git via Git protocol using <tt>git://vcs-git.duckcorp.org/...</tt> to access <tt>/vcs/git/...</tt> * [https://vcs-git-viewer.duckcorp.org/ Git browser] 7023e118e604e03f218c47ba9523978ca5440cb9 0 70 666 460 2018-03-03T08:44:06Z Duck 2 wikitext text/x-wiki {{Template:Service | description = Automatically find a changing (dynamic) IP address (home address for example) using this service. | prerequisite = | account = local | ipv6 = true | security_notes = This service is secured using TLS, web certificates and a specific account (separate from your main account). }} == Access == To use this service, ask for an account to an administrator. For each IP you need to track, you should provide with (explanations follows): * secondary account suffix (characters allowed: letters, numbers) * hostname suffix (characters allowed: letters, numbers, dash) The secondary account prefix is used to create your secondary account name, based on your main account name. If your main account is called ''toto'' and the secondary account prefix is called ''home'', then the secondary account name would be ''toto-home''. It is used as service username in the configuration, and along with a password, identify yourself as owner of the DNS entry. The hostname prefix is used to create the DNS entry for your host. If you use ''house'' as prefix, then the DNS entry would be ''toto-house.ddns.duckcorp.org''. It is possible to have multiple DNS names associated with the same account. So you could have another prefix ''manor'' and the additional DNS entry would be ''toto-manor.ddns.duckcorp.org''. === Installation on Debian === Currently the software is not packaged, so a few manual steps are needed. Install the dependencies: apt-get install kwalify ruby-curb ruby-safe-yaml ruby-log4r Install the Software: cd /opt git clone https://vcs-git.duckcorp.org/duckcorp/ddns.git cd ddns ruby setup.rb config --bindir=bin --rbdir=lib --datadir=data --sysconfdir=conf --localstatedir=var --shebang=never ruby setup.rb setup mkdir -p conf/ddns var/log/ddns === Configuration on Debian === Create ''/opt/ddns/conf/ddns/myip.conf'' containing: --- url: "https://myip.duckcorp.org/" timeout: 3 Create ''/opt/ddns/conf/ddns/client.conf'' containing: --- log: path: "./var/log/ddns/" regip: url: "https://ddns.duckcorp.org/" user: <secondary-account-name> passwd: <secondary-account-password> timeout: 3 profiles: <dns-entry>: ipv4: auto ipv6: auto and replace fields into angle brackets using your own credentials and DNS info. The ''profiles'' block can hold as many DNS entries as you need; they may not be on the same site though. You can find more information on the various configuration parameters on the [https://projects.duckcorp.org/projects/ddns/wiki/Configuration#RegIP-client-ddns-client DDNS project wiki]. == Technical Details == This service is made using: * [https://projects.duckcorp.org/projects/ddns DDNS] bc4a911b7e01e0c88b9451f91be298196920b18f 0 53 669 524 2018-04-28T05:44:39Z Duck 2 wikitext text/x-wiki {{Template:Service | description = The file repository is a general-purpose file exchange method. You push files into it and they are kept until you remove them. You may also share them with a other people. | prerequisite = You need to ask an administrator for an account if you want to push your own files, but you don't need anything if you just want to retrieve files from the public folders. | account = global-reg | ipv6 = true | security_notes = This service is secure. }} {{warning}} Remember not to use this service to store illegal or non-free data. == Access == You need a FTP client software to access this service, for example: * on GNU/*: filezilla or ftp-ssl * on MacOS: CyberDuck * on Windows: filezilla Most browsers should also work for read access. {{warning}} Certain softwares do not work well with an encrypted connection (TLS); in this case it is better to look for one with security in mind The publics folders are available for read access using this URL: ftp://ftp.duckcorp.org/ If you want to push files, you need to authenticate with SSL/TLS using this URL: ftps://ftps.duckcorp.org/ You may also access files directly on Toushirou in ''/ftp/ftp.duckcorp.org/'' if you have a [[Services/Shell|shell access]]. == Folders == Summary of important folders for write access: * private ('''DEPRECATED'''): restricted folders, for users or groups of users * public: folders which can be read by everybody (accessible directly without authentication on ftp://ftp.duckcorp.org/) * repository: upload folders for the [[Services/SoftwareRepository|software repository]] facility * sites: folders for hosted websites content == Documentation == * generic documentation on [[wikipedia:Ftp|FTP]] == Technical Details == This service is made using: * [http://proftpd.org/ ProFTPD] bed0326e20119065ae77c4bd8a1a7068847a2188 0 39 678 533 2018-04-28T05:49:53Z Duck 2 removed services wikitext text/x-wiki Here is a short overview of the services provided by DuckCorp. Our services are supervised and important data are [[Services/Backup|saved regularly]]. {{warning}} [[Services/Security|Notes about security !]] {| class="wikitable" style="text-align: center; width: 100%;" |+ Available Services |- ! Category !! colspan="2" | Service !! Access !! Status !! Description |- | Entertainment || colspan="2" | [[Games/Minetest|Minetest]] || public/users || {{status_ok}} || style="text-align: left;" | Minecraft-like game |- | rowspan="6" | Communication || rowspan="2" | Mail || [[Services/Mail|eMails]] || users || {{status_ok}} || style="text-align: left;" | Mail boxes with anti-spam/anti-virus, filtering…, or mail redirections |- | [[Services/ML|Mailing-Lists]] || users || {{status_ok}} || style="text-align: left;" | Distribution lists for mails |- | rowspan="3" | IRC || [[Services/IRC|IRC Network]] || public || {{status_ok}} || style="text-align: left;" | MilkyPond Chat Network using a dedicated software or a Web-interface |- | [[Services/IRC-Bouncer|IRC Bouncer]] || users || {{status_ok}} || style="text-align: left;" | IRC proxy (IRC server relaying IRC communications, keeping connections open and remembering logs) |- | [[Services/IRC-IM-GW|IRC to IM gateway]] || users || {{status_ok}} || style="text-align: left;" | Communication to multiple instant messaging networks through a unified IRC-like interface |- | XMPP (Jabber) || [[Services/XMPP|XMPP Network]] || users || {{status_ok}} || style="text-align: left;" | Global Chat Network (inter-communication between many [[wikipedia:Xmpp#History|well-known public IM services]]) |- | rowspan="4" | Sharing || colspan="2" | [[Services/Gallery|Media Gallery]] || public/users || {{status_down}} || style="text-align: left;" | Photo and video gallery |- | colspan="2" | [[Services/Wiki|Wiki]] || public/users || {{status_ok}} || style="text-align: left;" | Documentation, technical knowledge, useful tips… |- | colspan="2" | [[Services/StuffCloud|StuffCloud]] || public/users || {{status_ok}} || style="text-align: left;" | Personal data store (contacts, calendars, files…) with syncing/sharing capabilities |- | colspan="2" | [[Services/FTP|File Repository]] || public/users || {{status_ok}} || style="text-align: left;" | Generic file sharing system (using FTP) |- | rowspan="3" | Utilities || colspan="2" | [[Services/WebFeeds|News WebReader]] || users || {{status_ok}} || style="text-align: left;" | News feeds reader through a web interface |- | colspan="2" | [[Services/NTP|Time Server]] || public || {{status_ok}} || style="text-align: left;" | System used to automatically setup time on your machines |- | colspan="2" | [[Services/Dico|Dictionary Server]] || public || {{status_ok}} || style="text-align: left;" | Words searching system via a dedicated software (using the DICT protocol) or a Web-interface |- | rowspan="6" | Development || colspan="2" | [[Services/Projects|Project Management & Issue Tracking]] || public/users || {{status_ok}} || style="text-align: left;" | Tool intended to help organize projects |- | rowspan="2" | Code || [[Services/VCS|VCS]] || public/users || {{status_ok}} || style="text-align: left;" | Code/configuration versioning tools (Git, SVN, Baz, Bzr…) |- | [[Services/CodeReview|Code Review]] || public/users || {{status_down}} || style="text-align: left;" | Tool intended to help improve software quality |- | rowspan="2" | Databases || [[Services/SQL|SQL]] || users || {{status_ok}} || style="text-align: left;" | SQL server (PostgreSQL or MySQL) |- | [[Services/LDAP|LDAP]] || users || {{status_ok}} || style="text-align: left;" | LDAP server (OpenLDAP) |- | colspan="2" | [[Services/SoftwareRepository|Software Repository]] || public/users || {{status_ok}} || style="text-align: left;" | Software repository, to provide custom packages (think Debian debs) or installation media (thinks DVDs) |- | rowspan="7" | Hosting || rowspan="2" | Hostnames Directory || [[Services/DNS|DNS]] || users || {{status_ok}} || style="text-align: left;" | Domain Name System (NS1/NS2, DNSSEC…) |- | [[Services/DDNS|Dynamic DNS]] || users || {{status_ok}} || style="text-align: left;" | Dynamic DNS entries, for places where IPs are dynamic and not under your control |- | rowspan="2" | Mail || [[Services/MailHosting|Mail Domains]] || users || {{status_ok}} || style="text-align: left;" | Mail hosting (MX1/MX2) |- | [[Services/MLHosting|Mailing-Lists]] || users || {{status_ok}} || style="text-align: left;" | Distribution lists for mail domains |- | colspan="2" | [[Services/WebHosting|Web Sites/Applications]] || users || {{status_ok}} || style="text-align: left;" | Web pages using HTML/XHTML, CSS, JS, and various server-side programming languages (SSI, PHP, Perl, Python, Ruby…), and statistics (analytics data/reports) |- | colspan="2" | [[Services/XMPPHosting|XMPP Domains]] || users || {{status_ok}} || style="text-align: left;" | XMPP Node for a custom domain |- | colspan="2" | [[Services/Shell|Shell]] || trusted || {{status_ok}} || style="text-align: left;" | Useful for website administration, development, run custom scripts, persistent applications for text-mode geeks… |- | Network || colspan="2" | [[Services/IPv6-Broker|IPv6 tunnels]] || users || {{status_down}} || style="text-align: left;" | Access to the IPv6 world through an IPv4 connection |} == TODO == * in Services/Wiki: https://wiki.duckcorp.org/ * Radio … b556e407395323b3a5412d78cb01693c04b576f6 699 678 2018-04-29T13:46:23Z Duck 2 wikitext text/x-wiki Here is a short overview of the services provided by DuckCorp. Our services are supervised and important data are [[Services/Backup|saved regularly]]. {{warning}} [[Services/Security|Notes about security !]] {| class="wikitable" style="text-align: center; width: 100%;" |+ Available Services |- ! Category !! colspan="2" | Service !! Access !! Status !! Description |- | Entertainment || colspan="2" | [[Games/Minetest|Minetest]] || public/users || {{status_ok}} || style="text-align: left;" | Minecraft-like game |- | rowspan="5" | Communication || rowspan="2" | Mail || [[Services/Mail|eMails]] || users || {{status_ok}} || style="text-align: left;" | Mail boxes with anti-spam/anti-virus, filtering…, or mail redirections |- | [[Services/ML|Mailing-Lists]] || users || {{status_ok}} || style="text-align: left;" | Distribution lists for mails |- | rowspan="2" | IRC || [[Services/IRC|IRC Network]] || public || {{status_ok}} || style="text-align: left;" | MilkyPond Chat Network using a dedicated software or a Web-interface |- | [[Services/IRC-Bouncer|IRC Bouncer]] || users || {{status_ok}} || style="text-align: left;" | IRC proxy (IRC server relaying IRC communications, keeping connections open and remembering logs) |- | XMPP (Jabber) || [[Services/XMPP|XMPP Network]] || users || {{status_ok}} || style="text-align: left;" | Global Chat Network (inter-communication between many [[wikipedia:Xmpp#History|well-known public IM services]]) |- | rowspan="4" | Sharing || colspan="2" | [[Services/Gallery|Media Gallery]] || public/users || {{status_down}} || style="text-align: left;" | Photo and video gallery |- | colspan="2" | [[Services/Wiki|Wiki]] || public/users || {{status_ok}} || style="text-align: left;" | Documentation, technical knowledge, useful tips… |- | colspan="2" | [[Services/StuffCloud|StuffCloud]] || public/users || {{status_ok}} || style="text-align: left;" | Personal data store (contacts, calendars, files…) with syncing/sharing capabilities |- | colspan="2" | [[Services/FTP|File Repository]] || public/users || {{status_ok}} || style="text-align: left;" | Generic file sharing system (using FTP) |- | rowspan="3" | Utilities || colspan="2" | [[Services/WebFeeds|News WebReader]] || users || {{status_ok}} || style="text-align: left;" | News feeds reader through a web interface |- | colspan="2" | [[Services/NTP|Time Server]] || public || {{status_ok}} || style="text-align: left;" | System used to automatically setup time on your machines |- | colspan="2" | [[Services/Dico|Dictionary Server]] || public || {{status_ok}} || style="text-align: left;" | Words searching system via a dedicated software (using the DICT protocol) or a Web-interface |- | rowspan="6" | Development || colspan="2" | [[Services/Projects|Project Management & Issue Tracking]] || public/users || {{status_ok}} || style="text-align: left;" | Tool intended to help organize projects |- | rowspan="2" | Code || [[Services/VCS|VCS]] || public/users || {{status_ok}} || style="text-align: left;" | Code/configuration versioning tools (Git, SVN, Baz, Bzr…) |- | [[Services/CodeReview|Code Review]] || public/users || {{status_down}} || style="text-align: left;" | Tool intended to help improve software quality |- | rowspan="2" | Databases || [[Services/SQL|SQL]] || users || {{status_ok}} || style="text-align: left;" | SQL server (PostgreSQL or MySQL) |- | [[Services/LDAP|LDAP]] || users || {{status_ok}} || style="text-align: left;" | LDAP server (OpenLDAP) |- | colspan="2" | [[Services/SoftwareRepository|Software Repository]] || public/users || {{status_ok}} || style="text-align: left;" | Software repository, to provide custom packages (think Debian debs) or installation media (thinks DVDs) |- | rowspan="7" | Hosting || rowspan="2" | Hostnames Directory || [[Services/DNS|DNS]] || users || {{status_ok}} || style="text-align: left;" | Domain Name System (NS1/NS2, DNSSEC…) |- | [[Services/DDNS|Dynamic DNS]] || users || {{status_ok}} || style="text-align: left;" | Dynamic DNS entries, for places where IPs are dynamic and not under your control |- | rowspan="2" | Mail || [[Services/MailHosting|Mail Domains]] || users || {{status_ok}} || style="text-align: left;" | Mail hosting (MX1/MX2) |- | [[Services/MLHosting|Mailing-Lists]] || users || {{status_ok}} || style="text-align: left;" | Distribution lists for mail domains |- | colspan="2" | [[Services/WebHosting|Web Sites/Applications]] || users || {{status_ok}} || style="text-align: left;" | Web pages using HTML/XHTML, CSS, JS, and various server-side programming languages (SSI, PHP, Perl, Python, Ruby…), and statistics (analytics data/reports) |- | colspan="2" | [[Services/XMPPHosting|XMPP Domains]] || users || {{status_ok}} || style="text-align: left;" | XMPP Node for a custom domain |- | colspan="2" | [[Services/Shell|Shell]] || trusted || {{status_ok}} || style="text-align: left;" | Useful for website administration, development, run custom scripts, persistent applications for text-mode geeks… |- | Network || colspan="2" | [[Services/IPv6-Broker|IPv6 tunnels]] || users || {{status_down}} || style="text-align: left;" | Access to the IPv6 world through an IPv4 connection |} == TODO == * in Services/Wiki: https://wiki.duckcorp.org/ * Radio … a96b4065db22ae9904d105c04068d857d30eec07 794 699 2019-05-07T18:10:15Z Duck 2 wikitext text/x-wiki Here is a short overview of the services provided by DuckCorp. Our services are supervised and important data are [[Services/Backup|saved regularly]]. {{warning}} [[Services/Security|Notes about security !]] {| class="wikitable" style="text-align: center; width: 100%;" |+ Available Services |- ! Category !! colspan="2" | Service !! Access !! Status !! Description |- | Entertainment || colspan="2" | [[Games/Minetest|Minetest]] || public/users || {{status_ok}} || style="text-align: left;" | Minecraft-like game |- | rowspan="5" | Communication || rowspan="2" | Mail || [[Services/Mail|eMails]] || users || {{status_ok}} || style="text-align: left;" | Mail boxes with anti-spam/anti-virus, filtering…, or mail redirections |- | [[Services/ML|Mailing-Lists]] || users || {{status_ok}} || style="text-align: left;" | Distribution lists for mails |- | rowspan="2" | IRC || [[Services/IRC|IRC Network]] || public || {{status_ok}} || style="text-align: left;" | MilkyPond Chat Network using a dedicated software or a Web-interface |- | [[Services/IRC-Bouncer|IRC Bouncer]] || users || {{status_ok}} || style="text-align: left;" | IRC proxy (IRC server relaying IRC communications, keeping connections open and remembering logs) |- | XMPP (Jabber) || [[Services/XMPP|XMPP Network]] || users || {{status_ok}} || style="text-align: left;" | Global Chat Network (inter-communication between many [[wikipedia:Xmpp#History|well-known public IM services]]) |- | rowspan="4" | Sharing || colspan="2" | [[Services/Gallery|Media Gallery]] || public/users || {{status_down}} || style="text-align: left;" | Photo and video gallery |- | colspan="2" | [[Services/Wiki|Wiki]] || public/users || {{status_ok}} || style="text-align: left;" | Documentation, technical knowledge, useful tips… |- | colspan="2" | [[Services/StuffCloud|StuffCloud]] || public/users || {{status_ok}} || style="text-align: left;" | Personal data store (contacts, calendars, files…) with syncing/sharing capabilities |- | colspan="2" | [[Services/FTP|File Repository]] || public/users || {{status_ok}} || style="text-align: left;" | Generic file sharing system (using FTP) |- | rowspan="3" | Utilities || colspan="2" | [[Services/WebFeeds|News WebReader]] || users || {{status_ok}} || style="text-align: left;" | News feeds reader through a web interface |- | colspan="2" | [[Services/NTP|Time Server]] || public || {{status_ok}} || style="text-align: left;" | System used to automatically setup time on your machines |- | colspan="2" | [[Services/Dico|Dictionary Server]] || public || {{status_ok}} || style="text-align: left;" | Words searching system via a dedicated software (using the DICT protocol) or a Web-interface |- | rowspan="6" | Development || colspan="2" | [[Services/Projects|Project Management & Issue Tracking]] || public/users || {{status_ok}} || style="text-align: left;" | Tool intended to help organize projects |- | rowspan="2" | Code || [[Services/VCS|VCS]] || public/users || {{status_ok}} || style="text-align: left;" | Code/configuration versioning tools (Git, SVN, Baz, Bzr…) |- | [[Services/CodeReview|Code Review]] || public/users || {{status_down}} || style="text-align: left;" | Tool intended to help improve software quality |- | rowspan="2" | Databases || [[Services/SQL|SQL]] || users || {{status_ok}} || style="text-align: left;" | SQL server (PostgreSQL or MySQL) |- | [[Services/LDAP|LDAP]] || users || {{status_ok}} || style="text-align: left;" | LDAP server (OpenLDAP) |- | colspan="2" | [[Services/SoftwareRepository|Software Repository]] || public/users || {{status_ok}} || style="text-align: left;" | Software repository, to provide custom packages (think Debian debs) or installation media (thinks DVDs) |- | rowspan="7" | Hosting || rowspan="2" | Hostnames Directory || [[Services/DNS|DNS]] || users || {{status_ok}} || style="text-align: left;" | Domain Name System (NS1/NS2, DNSSEC…) |- | [[Services/DDNS|Dynamic DNS]] || users || {{status_ok}} || style="text-align: left;" | Dynamic DNS entries, for places where IPs are dynamic and not under your control |- | rowspan="2" | Mail || [[Services/MailHosting|Mail Domains]] || users || {{status_ok}} || style="text-align: left;" | Mail hosting (MX1/MX2) |- | [[Services/MLHosting|Mailing-Lists]] || users || {{status_ok}} || style="text-align: left;" | Distribution lists for mail domains |- | colspan="2" | [[Services/WebHosting|Web Sites/Applications]] || users || {{status_ok}} || style="text-align: left;" | Web pages using HTML/XHTML, CSS, JS, and various server-side programming languages (SSI, PHP, Perl, Python, Ruby…), and statistics (analytics data/reports) |- | colspan="2" | [[Services/XMPPHosting|XMPP Domains]] || users || {{status_ok}} || style="text-align: left;" | XMPP Node for a custom domain |- | colspan="2" | [[Services/Shell|Shell]] || trusted || {{status_ok}} || style="text-align: left;" | Useful for website administration, development, run custom scripts, persistent applications for text-mode geeks… |} == TODO == * in Services/Wiki: https://wiki.duckcorp.org/ * Radio … b01a586c40e6ff0da1b90c9bd4048c1d23599fcb 805 794 2020-04-08T04:32:02Z Duck 2 wikitext text/x-wiki Here is a short overview of the services provided by DuckCorp. Our services are supervised and important data are [[Services/Backup|saved regularly]]. {{warning}} [[Services/Security|Notes about security !]] {| class="wikitable" style="text-align: center; width: 100%;" |+ Available Services |- ! Category !! colspan="2" | Service !! Access !! Status !! Description |- | rowspan="5" | Communication || rowspan="2" | Mail || [[Services/Mail|eMails]] || users || {{status_ok}} || style="text-align: left;" | Mail boxes with anti-spam/anti-virus, filtering…, or mail redirections |- | [[Services/ML|Mailing-Lists]] || users || {{status_ok}} || style="text-align: left;" | Distribution lists for mails |- | rowspan="2" | IRC || [[Services/IRC|IRC Network]] || public || {{status_ok}} || style="text-align: left;" | MilkyPond Chat Network using a dedicated software or a Web-interface |- | [[Services/IRC-Bouncer|IRC Bouncer]] || users || {{status_ok}} || style="text-align: left;" | IRC proxy (IRC server relaying IRC communications, keeping connections open and remembering logs) |- | XMPP (Jabber) || [[Services/XMPP|XMPP Network]] || users || {{status_ok}} || style="text-align: left;" | Global Chat Network (inter-communication between many [[wikipedia:Xmpp#History|well-known public IM services]]) |- | rowspan="4" | Sharing || colspan="2" | [[Services/Gallery|Media Gallery]] || public/users || {{status_down}} || style="text-align: left;" | Photo and video gallery |- | colspan="2" | [[Services/Wiki|Wiki]] || public/users || {{status_ok}} || style="text-align: left;" | Documentation, technical knowledge, useful tips… |- | colspan="2" | [[Services/StuffCloud|StuffCloud]] || public/users || {{status_ok}} || style="text-align: left;" | Personal data store (contacts, calendars, files…) with syncing/sharing capabilities |- | colspan="2" | [[Services/FTP|File Repository]] || public/users || {{status_ok}} || style="text-align: left;" | Generic file sharing system (using FTP) |- | rowspan="3" | Utilities || colspan="2" | [[Services/WebFeeds|News WebReader]] || users || {{status_ok}} || style="text-align: left;" | News feeds reader through a web interface |- | colspan="2" | [[Services/NTP|Time Server]] || public || {{status_ok}} || style="text-align: left;" | System used to automatically setup time on your machines |- | colspan="2" | [[Services/Dico|Dictionary Server]] || public || {{status_ok}} || style="text-align: left;" | Words searching system via a dedicated software (using the DICT protocol) or a Web-interface |- | rowspan="6" | Development || colspan="2" | [[Services/Projects|Project Management & Issue Tracking]] || public/users || {{status_ok}} || style="text-align: left;" | Tool intended to help organize projects |- | rowspan="2" | Code || [[Services/VCS|VCS]] || public/users || {{status_ok}} || style="text-align: left;" | Code/configuration versioning tools (Git, SVN, Baz, Bzr…) |- | [[Services/CodeReview|Code Review]] || public/users || {{status_down}} || style="text-align: left;" | Tool intended to help improve software quality |- | rowspan="2" | Databases || [[Services/SQL|SQL]] || users || {{status_ok}} || style="text-align: left;" | SQL server (PostgreSQL or MySQL) |- | [[Services/LDAP|LDAP]] || users || {{status_ok}} || style="text-align: left;" | LDAP server (OpenLDAP) |- | colspan="2" | [[Services/SoftwareRepository|Software Repository]] || public/users || {{status_ok}} || style="text-align: left;" | Software repository, to provide custom packages (think Debian debs) or installation media (thinks DVDs) |- | rowspan="7" | Hosting || rowspan="2" | Hostnames Directory || [[Services/DNS|DNS]] || users || {{status_ok}} || style="text-align: left;" | Domain Name System (NS1/NS2, DNSSEC…) |- | [[Services/DDNS|Dynamic DNS]] || users || {{status_ok}} || style="text-align: left;" | Dynamic DNS entries, for places where IPs are dynamic and not under your control |- | rowspan="2" | Mail || [[Services/MailHosting|Mail Domains]] || users || {{status_ok}} || style="text-align: left;" | Mail hosting (MX1/MX2) |- | [[Services/MLHosting|Mailing-Lists]] || users || {{status_ok}} || style="text-align: left;" | Distribution lists for mail domains |- | colspan="2" | [[Services/WebHosting|Web Sites/Applications]] || users || {{status_ok}} || style="text-align: left;" | Web pages using HTML/XHTML, CSS, JS, and various server-side programming languages (SSI, PHP, Perl, Python, Ruby…) |- | colspan="2" | [[Services/XMPPHosting|XMPP Domains]] || users || {{status_ok}} || style="text-align: left;" | XMPP Node for a custom domain |- | colspan="2" | [[Services/Shell|Shell]] || trusted || {{status_ok}} || style="text-align: left;" | Useful for website administration, development, run custom scripts, persistent applications for text-mode geeks… |} == TODO == * in Services/Wiki: https://wiki.duckcorp.org/ * Radio … be81a8e1be4e6f4d0ee46b2057d498a42c315b68 0 32 687 563 2018-04-28T06:41:43Z Duck 2 wikitext text/x-wiki Let's be transparent about money too. Pure financial contributions are not listed here, but in the [[DcDonation|donation page]]. == Regular Expenses == This does not account for external sponsorship, but contributions by members. {| class="wikitable" style="text-align: center; width: 100%;" ! Object !! Amount !! Sponsor !! Comments |- | DuckCorp DNS domain || ~7€/year (since 2014-07)<br/><del>~15€/year</del> || Duck |- | MilkyPond DNS domain || ~7€/year (since 2014-07)<br/><del>~15€/year</del> || Rtp |- | Toushirou's housing || 41.56€/month || Duck || collocation with Sam (considering network switch and APC powerswitch shared rack space) |} Note: private Internet connections involved in DuckCorp's services are not taken into account. Thorfinn was once hosted on a VM coupled with the Internet offer, this was not mentioned either. == Exceptional Expenses == Note: this does not take into account expenses before 2006 because most historical data were lost. Note: machines, VMs, or containers hosted privately and involved in Duckcorp's services are not fully taken into account as owners kindly provided for their well being; this includes (by order of appearance): * Elwing (Duck): services reduced starting from 2010, and restarted in 2018 (see #637) * Daneel (Duck): in need of resurrection but was useful for backup and admin stuff * Korutopi (Arnau): stopped in 2018 butvery useful for backup and monitoring * Nicecity (Pilou): experiencing difficulties, backup and monitoring === Improvement Expenses === {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Object !! Amount !! Sponsor !! Comments |- | 2018-04-25 || more memory for Elwing (2*8GB) || 18770円 || Duck || see #637 |- | 2018-04-11 || disks for Toushirou-NG || 241.12€ || Duck || 2*500GB SSD |- | 2012-05-09 || more memory for Toushirou (2*2GB) || ~60€ || Pilou || PC2-6400 instead of PC2-5300/5400 (see replacement memory details) |- | 2007-10 || replacement server (Orfeo-NG) || 1210€ || Duck || Sun Fire X4100 |- | 2007-05 || new server (Toushirou) || 1709.08€ || Duck || Supermicro PDSMI+ / Core 2 Duo E6600 / 2GB PC5400 / 3ware 9550SX4LP / 4x HD SATA II 250GB |} === Failure Expenses === {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Object !! Amount !! Sponsor !! Comments |- | 2017-??-?? || disks replacement || ???JPY || Arnau || still not stable, controller suspected to have problems |- | 2010-05-22 || replacement memory for Toushirou (2*2GB) || 105€ || Duck || PC2-5300/5400 2*2GB memory in a correct brand could not be found anymore, so we had to take PC2-6400 instead |- | 2010-01-06 || spare disk || 73€ || Duck || avoided tragedy when both disks in Daneel died at one week interval |- | 2007-09-29 || replacement server (Daneel-ng) || 534.90€ || Duck || machine too old and previous disk died horribly |- | 2006-01 || 300GB HD for Daneel (backup) || || AnonymousDonor1 || replaced since then |} === Other Expenses === {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Object !! Amount !! Sponsor !! Comments |- | 2010-06-29 || taxi || 26.20€ || Duck || Nerim bought Sivit, moving Toushirou to their new suite at Equinix PA3 (CBV->STD) |} 2ff2f655d08c6d50537aa49e730c26f0517c8968 692 687 2018-04-28T06:45:24Z Duck 2 /* Improvement Expenses */ wikitext text/x-wiki Let's be transparent about money too. Pure financial contributions are not listed here, but in the [[DcDonation|donation page]]. == Regular Expenses == This does not account for external sponsorship, but contributions by members. {| class="wikitable" style="text-align: center; width: 100%;" ! Object !! Amount !! Sponsor !! Comments |- | DuckCorp DNS domain || ~7€/year (since 2014-07)<br/><del>~15€/year</del> || Duck |- | MilkyPond DNS domain || ~7€/year (since 2014-07)<br/><del>~15€/year</del> || Rtp |- | Toushirou's housing || 41.56€/month || Duck || collocation with Sam (considering network switch and APC powerswitch shared rack space) |} Note: private Internet connections involved in DuckCorp's services are not taken into account. Thorfinn was once hosted on a VM coupled with the Internet offer, this was not mentioned either. == Exceptional Expenses == Note: this does not take into account expenses before 2006 because most historical data were lost. Note: machines, VMs, or containers hosted privately and involved in Duckcorp's services are not fully taken into account as owners kindly provided for their well being; this includes (by order of appearance): * Elwing (Duck): services reduced starting from 2010, and restarted in 2018 (see #637) * Daneel (Duck): in need of resurrection but was useful for backup and admin stuff * Korutopi (Arnau): stopped in 2018 butvery useful for backup and monitoring * Nicecity (Pilou): experiencing difficulties, backup and monitoring === Improvement Expenses === {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Object !! Amount !! Sponsor !! Comments |- | 2018-04 || more memory for Elwing (2*8GB) || ??? || Arnau || see #637. previously used in Mirimoto for Korutopi |- | 2018-04-25 || more memory for Elwing (2*8GB) || 18770円 || Duck || see #637 |- | 2018-04-11 || disks for Toushirou-NG || 241.12€ || Duck || 2*500GB SSD |- | 2012-05-09 || more memory for Toushirou (2*2GB) || ~60€ || Pilou || PC2-6400 instead of PC2-5300/5400 (see replacement memory details) |- | 2007-10 || replacement server (Orfeo-NG) || 1210€ || Duck || Sun Fire X4100 |- | 2007-05 || new server (Toushirou) || 1709.08€ || Duck || Supermicro PDSMI+ / Core 2 Duo E6600 / 2GB PC5400 / 3ware 9550SX4LP / 4x HD SATA II 250GB |} === Failure Expenses === {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Object !! Amount !! Sponsor !! Comments |- | 2017-??-?? || disks replacement || ???JPY || Arnau || still not stable, controller suspected to have problems |- | 2010-05-22 || replacement memory for Toushirou (2*2GB) || 105€ || Duck || PC2-5300/5400 2*2GB memory in a correct brand could not be found anymore, so we had to take PC2-6400 instead |- | 2010-01-06 || spare disk || 73€ || Duck || avoided tragedy when both disks in Daneel died at one week interval |- | 2007-09-29 || replacement server (Daneel-ng) || 534.90€ || Duck || machine too old and previous disk died horribly |- | 2006-01 || 300GB HD for Daneel (backup) || || AnonymousDonor1 || replaced since then |} === Other Expenses === {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Object !! Amount !! Sponsor !! Comments |- | 2010-06-29 || taxi || 26.20€ || Duck || Nerim bought Sivit, moving Toushirou to their new suite at Equinix PA3 (CBV->STD) |} 5ff8312c1cc2b08b55977ecc14fb97ce938b20e9 720 692 2018-05-19T14:15:24Z Duck 2 /* Improvement Expenses */ wikitext text/x-wiki Let's be transparent about money too. Pure financial contributions are not listed here, but in the [[DcDonation|donation page]]. == Regular Expenses == This does not account for external sponsorship, but contributions by members. {| class="wikitable" style="text-align: center; width: 100%;" ! Object !! Amount !! Sponsor !! Comments |- | DuckCorp DNS domain || ~7€/year (since 2014-07)<br/><del>~15€/year</del> || Duck |- | MilkyPond DNS domain || ~7€/year (since 2014-07)<br/><del>~15€/year</del> || Rtp |- | Toushirou's housing || 41.56€/month || Duck || collocation with Sam (considering network switch and APC powerswitch shared rack space) |} Note: private Internet connections involved in DuckCorp's services are not taken into account. Thorfinn was once hosted on a VM coupled with the Internet offer, this was not mentioned either. == Exceptional Expenses == Note: this does not take into account expenses before 2006 because most historical data were lost. Note: machines, VMs, or containers hosted privately and involved in Duckcorp's services are not fully taken into account as owners kindly provided for their well being; this includes (by order of appearance): * Elwing (Duck): services reduced starting from 2010, and restarted in 2018 (see #637) * Daneel (Duck): in need of resurrection but was useful for backup and admin stuff * Korutopi (Arnau): stopped in 2018 butvery useful for backup and monitoring * Nicecity (Pilou): experiencing difficulties, backup and monitoring === Improvement Expenses === {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Object !! Amount !! Sponsor !! Comments |- | 2018-04 || more memory for Elwing (2*8GB) || ??? || Arnau || see #637. previously used in Mirimoto for Korutopi, unfortunately not working well |- | 2018-04-25 || more memory for Elwing (2*8GB) || 18770円 || Duck || see #637 |- | 2018-04-11 || disks for Toushirou-NG || 241.12€ || Duck || 2*500GB SSD |- | 2012-05-09 || more memory for Toushirou (2*2GB) || ~60€ || Pilou || PC2-6400 instead of PC2-5300/5400 (see replacement memory details) |- | 2007-10 || replacement server (Orfeo-NG) || 1210€ || Duck || Sun Fire X4100 |- | 2007-05 || new server (Toushirou) || 1709.08€ || Duck || Supermicro PDSMI+ / Core 2 Duo E6600 / 2GB PC5400 / 3ware 9550SX4LP / 4x HD SATA II 250GB |} === Failure Expenses === {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Object !! Amount !! Sponsor !! Comments |- | 2017-??-?? || disks replacement || ???JPY || Arnau || still not stable, controller suspected to have problems |- | 2010-05-22 || replacement memory for Toushirou (2*2GB) || 105€ || Duck || PC2-5300/5400 2*2GB memory in a correct brand could not be found anymore, so we had to take PC2-6400 instead |- | 2010-01-06 || spare disk || 73€ || Duck || avoided tragedy when both disks in Daneel died at one week interval |- | 2007-09-29 || replacement server (Daneel-ng) || 534.90€ || Duck || machine too old and previous disk died horribly |- | 2006-01 || 300GB HD for Daneel (backup) || || AnonymousDonor1 || replaced since then |} === Other Expenses === {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Object !! Amount !! Sponsor !! Comments |- | 2010-06-29 || taxi || 26.20€ || Duck || Nerim bought Sivit, moving Toushirou to their new suite at Equinix PA3 (CBV->STD) |} 499e6459741aff50ce22cf12aca49a146023e06b 726 720 2018-06-06T14:58:57Z Duck 2 wikitext text/x-wiki Let's be transparent about money too. Pure financial contributions are not listed here, but in the [[DcDonation|donation page]]. == Regular Expenses == This does not account for external sponsorship, but contributions by members. {| class="wikitable" style="text-align: center; width: 100%;" ! Object !! Amount !! Sponsor !! Comments |- | DuckCorp DNS domain || ~7€/year (since 2014-07)<br/><del>~15€/year</del> || Duck |- | MilkyPond DNS domain || ~7€/year (since 2014-07)<br/><del>~15€/year</del> || Rtp |- | Toushirou's housing || 41.56€/month || Duck || collocation with Sam (considering network switch and APC powerswitch shared rack space) |} Note: private Internet connections involved in DuckCorp's services are not taken into account. Thorfinn was once hosted on a VM coupled with the Internet offer, this was not mentioned either. == Exceptional Expenses == Note: this does not take into account expenses before 2006 because most historical data were lost. Note: machines, VMs, or containers hosted privately and involved in Duckcorp's services are not fully taken into account as owners kindly provided for their well being; this includes (by order of appearance): * Elwing (Duck): services reduced starting from 2010, and restarted in 2018 (see #637) * Daneel (Duck): in need of resurrection but was useful for backup and admin stuff * Korutopi (Arnau): stopped in 2018 butvery useful for backup and monitoring * Nicecity (Pilou): experiencing difficulties, backup and monitoring === Improvement Expenses === {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Object !! Amount !! Sponsor !! Comments |- | 2018-06 || 2 disks for new Toushirou || ??? || Pilou || |- | 2018-04 || more memory for Elwing (2*8GB) || ??? || Arnau || see #637. previously used in Mirimoto for Korutopi, unfortunately not working well |- | 2018-04-25 || more memory for Elwing (2*8GB) || 18770円 || Duck || see #637 |- | 2018-04-11 || disks for Toushirou-NG || 241.12€ || Duck || 2*500GB SSD |- | 2012-05-09 || more memory for Toushirou (2*2GB) || ~60€ || Pilou || PC2-6400 instead of PC2-5300/5400 (see replacement memory details) |- | 2007-10 || replacement server (Orfeo-NG) || 1210€ || Duck || Sun Fire X4100 |- | 2007-05 || new server (Toushirou) || 1709.08€ || Duck || Supermicro PDSMI+ / Core 2 Duo E6600 / 2GB PC5400 / 3ware 9550SX4LP / 4x HD SATA II 250GB |} === Failure Expenses === {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Object !! Amount !! Sponsor !! Comments |- | 2017-??-?? || disks replacement || ???JPY || Arnau || still not stable, controller suspected to have problems |- | 2010-05-22 || replacement memory for Toushirou (2*2GB) || 105€ || Duck || PC2-5300/5400 2*2GB memory in a correct brand could not be found anymore, so we had to take PC2-6400 instead |- | 2010-01-06 || spare disk || 73€ || Duck || avoided tragedy when both disks in Daneel died at one week interval |- | 2007-09-29 || replacement server (Daneel-ng) || 534.90€ || Duck || machine too old and previous disk died horribly |- | 2006-01 || 300GB HD for Daneel (backup) || || AnonymousDonor1 || replaced since then |} === Other Expenses === {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Object !! Amount !! Sponsor !! Comments |- | 2010-06-29 || taxi || 26.20€ || Duck || Nerim bought Sivit, moving Toushirou to their new suite at Equinix PA3 (CBV->STD) |} 0f5ed3c9c4a2a32919f1f2c085b959782186c73d 729 726 2018-06-06T15:04:14Z Duck 2 wikitext text/x-wiki Let's be transparent about money too. Pure financial contributions are not listed here, but in the [[DcDonation|donation page]]. == Regular Expenses == This does not account for external sponsorship, but contributions by members. {| class="wikitable" style="text-align: center; width: 100%;" ! Object !! Amount !! Sponsor !! Comments |- | DuckCorp DNS domain || ~7€/year (since 2014-07)<br/><del>~15€/year</del> || Duck |- | MilkyPond DNS domain || ~7€/year (since 2014-07)<br/><del>~15€/year</del> || Rtp |- | Toushirou's housing || 41.56€/month || Duck || collocation with Sam (considering network switch and APC powerswitch shared rack space) |} Note: private Internet connections involved in DuckCorp's services are not taken into account. Thorfinn was once hosted on a VM coupled with the Internet offer, this was not mentioned either. == Exceptional Expenses == Note: this does not take into account expenses before 2006 because most historical data were lost. Note: machines, VMs, or containers hosted privately and involved in Duckcorp's services are not fully taken into account as owners kindly provided for their well being; this includes (by order of appearance): * Elwing (Duck): services reduced starting from 2010, and restarted in 2018 (see #637) * Daneel (Duck): in need of resurrection but was useful for backup and admin stuff * Korutopi (Arnau): stopped in 2018 butvery useful for backup and monitoring * Nicecity (Pilou): experiencing difficulties, backup and monitoring === Improvement Expenses === {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Object !! Amount !! Sponsor !! Comments |- | 2018-06 || 3 disks for Toushirou-NG || ??? || Pilou || Western Digital Black Mobile 1To (WD10JPLX), RAID 1 with spare, see #614 |- | 2018-04 || more memory for Elwing || ??? || Arnau || 2*8GB, see #637. previously used in Mirimoto for Korutopi, unfortunately broken |- | 2018-04-25 || more memory for Elwing || 18770円 || Duck || 2*8GB, see #637 |- | 2018-04-11 || disks for Toushirou-NG || 241.12€ || Duck || 2*500GB SSD, see #614 |- | 2012-05-09 || more memory for Toushirou || ~60€ || Pilou || 2*2GB PC2-6400 instead of PC2-5300/5400 (see replacement memory details) |- | 2007-10 || replacement server (Orfeo-NG) || 1210€ || Duck || Sun Fire X4100 |- | 2007-05 || new server (Toushirou) || 1709.08€ || Duck || Supermicro PDSMI+ / Core 2 Duo E6600 / 2GB PC5400 / 3ware 9550SX4LP / 4x HD SATA II 250GB |} === Failure Expenses === {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Object !! Amount !! Sponsor !! Comments |- | 2017-??-?? || disks replacement || ???JPY || Arnau || still not stable, controller suspected to have problems |- | 2010-05-22 || replacement memory for Toushirou (2*2GB) || 105€ || Duck || PC2-5300/5400 2*2GB memory in a correct brand could not be found anymore, so we had to take PC2-6400 instead |- | 2010-01-06 || spare disk || 73€ || Duck || avoided tragedy when both disks in Daneel died at one week interval |- | 2007-09-29 || replacement server (Daneel-ng) || 534.90€ || Duck || machine too old and previous disk died horribly |- | 2006-01 || 300GB HD for Daneel (backup) || || AnonymousDonor1 || replaced since then |} === Other Expenses === {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Object !! Amount !! Sponsor !! Comments |- | 2010-06-29 || taxi || 26.20€ || Duck || Nerim bought Sivit, moving Toushirou to their new suite at Equinix PA3 (CBV->STD) |} b30a46fa56220d70ec1b6685da8fd56e1bca3044 739 729 2018-08-25T23:42:58Z Pilou 7 Western Digital Black Mobile weren't compatible (see http://dascomputerconsultants.com/HPCompaqServerDrives.htm), they have been replaced by WD Red wikitext text/x-wiki Let's be transparent about money too. Pure financial contributions are not listed here, but in the [[DcDonation|donation page]]. == Regular Expenses == This does not account for external sponsorship, but contributions by members. {| class="wikitable" style="text-align: center; width: 100%;" ! Object !! Amount !! Sponsor !! Comments |- | DuckCorp DNS domain || ~7€/year (since 2014-07)<br/><del>~15€/year</del> || Duck |- | MilkyPond DNS domain || ~7€/year (since 2014-07)<br/><del>~15€/year</del> || Rtp |- | Toushirou's housing || 41.56€/month || Duck || collocation with Sam (considering network switch and APC powerswitch shared rack space) |} Note: private Internet connections involved in DuckCorp's services are not taken into account. Thorfinn was once hosted on a VM coupled with the Internet offer, this was not mentioned either. == Exceptional Expenses == Note: this does not take into account expenses before 2006 because most historical data were lost. Note: machines, VMs, or containers hosted privately and involved in Duckcorp's services are not fully taken into account as owners kindly provided for their well being; this includes (by order of appearance): * Elwing (Duck): services reduced starting from 2010, and restarted in 2018 (see #637) * Daneel (Duck): in need of resurrection but was useful for backup and admin stuff * Korutopi (Arnau): stopped in 2018 butvery useful for backup and monitoring * Nicecity (Pilou): experiencing difficulties, backup and monitoring === Improvement Expenses === {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Object !! Amount !! Sponsor !! Comments |- | 2018-06 || 3 disks for Toushirou-NG || ??? || Pilou || Western Digital Red 1To (WD10JFCX), RAID 1 with spare, see #612 |- | 2018-04 || more memory for Elwing || ??? || Arnau || 2*8GB, see #637. previously used in Mirimoto for Korutopi, unfortunately broken |- | 2018-04-25 || more memory for Elwing || 18770円 || Duck || 2*8GB, see #637 |- | 2018-04-11 || disks for Toushirou-NG || 241.12€ || Duck || 2*500GB SSD, see #614 |- | 2012-05-09 || more memory for Toushirou || ~60€ || Pilou || 2*2GB PC2-6400 instead of PC2-5300/5400 (see replacement memory details) |- | 2007-10 || replacement server (Orfeo-NG) || 1210€ || Duck || Sun Fire X4100 |- | 2007-05 || new server (Toushirou) || 1709.08€ || Duck || Supermicro PDSMI+ / Core 2 Duo E6600 / 2GB PC5400 / 3ware 9550SX4LP / 4x HD SATA II 250GB |} === Failure Expenses === {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Object !! Amount !! Sponsor !! Comments |- | 2017-??-?? || disks replacement || ???JPY || Arnau || still not stable, controller suspected to have problems |- | 2010-05-22 || replacement memory for Toushirou (2*2GB) || 105€ || Duck || PC2-5300/5400 2*2GB memory in a correct brand could not be found anymore, so we had to take PC2-6400 instead |- | 2010-01-06 || spare disk || 73€ || Duck || avoided tragedy when both disks in Daneel died at one week interval |- | 2007-09-29 || replacement server (Daneel-ng) || 534.90€ || Duck || machine too old and previous disk died horribly |- | 2006-01 || 300GB HD for Daneel (backup) || || AnonymousDonor1 || replaced since then |} === Other Expenses === {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Object !! Amount !! Sponsor !! Comments |- | 2010-06-29 || taxi || 26.20€ || Duck || Nerim bought Sivit, moving Toushirou to their new suite at Equinix PA3 (CBV->STD) |} 366b7f76cd5f9a003f0c3433c8cd52d01f53296f 770 739 2019-01-11T12:14:15Z Duck 2 wikitext text/x-wiki Let's be transparent about money too. Pure financial contributions are not listed here, but in the [[DcDonation|donation page]]. == Regular Expenses == This does not account for external sponsorship, but contributions by members. {| class="wikitable" style="text-align: center; width: 100%;" ! Object !! Amount !! Sponsor !! Comments |- | DuckCorp DNS domain || ~7€/year (since 2014-07)<br/><del>~15€/year</del> || Duck |- | MilkyPond DNS domain || ~7€/year (since 2014-07)<br/><del>~15€/year</del> || Rtp |- | Toushirou's housing || 41.56€/month || Duck || collocation with Sam (considering network switch and APC powerswitch shared rack space) |} Note: private Internet connections involved in DuckCorp's services are not taken into account. Thorfinn was once hosted on a VM coupled with the Internet offer, this was not mentioned either. == Exceptional Expenses == Note: this does not take into account expenses before 2006 because most historical data were lost. Note: machines, VMs, or containers hosted privately and involved in Duckcorp's services are not fully taken into account as owners kindly provided for their well being; this includes (by order of appearance): * Elwing (Duck): services reduced starting from 2010, and restarted in 2018 (see #637) * Daneel (Duck): in need of resurrection; was useful for backup and admin stuff * Korutopi (Arnau): stopped in 2018; was very useful for backup and monitoring * Nicecity (Pilou): experiencing difficulties, backup and monitoring === Improvement Expenses === {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Object !! Amount !! Sponsor !! Comments |- | 2018-06 || 3 disks for Toushirou-NG || ??? || Pilou || Western Digital Red 1To (WD10JFCX), RAID 1 with spare, see #612 |- | 2018-04 || more memory for Elwing || ??? || Arnau || 2*8GB, see #637. previously used in Mirimoto for Korutopi, unfortunately broken |- | 2018-04-25 || more memory for Elwing || 18770円 || Duck || 2*8GB, see #637 |- | 2018-04-11 || disks for Toushirou-NG || 241.12€ || Duck || 2*500GB SSD, see #614 |- | 2012-05-09 || more memory for Toushirou || ~60€ || Pilou || 2*2GB PC2-6400 instead of PC2-5300/5400 (see replacement memory details) |- | 2007-10 || replacement server (Orfeo-NG) || 1210€ || Duck || Sun Fire X4100 |- | 2007-05 || new server (Toushirou) || 1709.08€ || Duck || Supermicro PDSMI+ / Core 2 Duo E6600 / 2GB PC5400 / 3ware 9550SX4LP / 4x HD SATA II 250GB |} === Failure Expenses === {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Object !! Amount !! Sponsor !! Comments |- | 2017-??-?? || disks replacement || ???JPY || Arnau || still not stable, controller suspected to have problems |- | 2010-05-22 || replacement memory for Toushirou (2*2GB) || 105€ || Duck || PC2-5300/5400 2*2GB memory in a correct brand could not be found anymore, so we had to take PC2-6400 instead |- | 2010-01-06 || spare disk || 73€ || Duck || avoided tragedy when both disks in Daneel died at one week interval |- | 2007-09-29 || replacement server (Daneel-ng) || 534.90€ || Duck || machine too old and previous disk died horribly |- | 2006-01 || 300GB HD for Daneel (backup) || || AnonymousDonor1 || replaced since then |} === Other Expenses === {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Object !! Amount !! Sponsor !! Comments |- | 2010-06-29 || taxi || 26.20€ || Duck || Nerim bought Sivit, moving Toushirou to their new suite at Equinix PA3 (CBV->STD) |} c9c11b3a78e96fe2fed2873c8cf6044b22f0708b 0 178 712 2018-05-02T17:12:50Z Duck 2 Created page with "{{Template:Service | description = Packages repository, currently Debian packages only. Provide fixes and backported packages for DuckCorp. Specific sections can be created fo..." wikitext text/x-wiki {{Template:Service | description = Packages repository, currently Debian packages only. Provide fixes and backported packages for DuckCorp. Specific sections can be created for users. No prerequisite for read access. | prerequisite = | account = local | ipv6 = true | security_notes = This service is secure. }} == Access == To install packages you can add the following in your '''/etc/apt/sources.list''': deb https://repository.duckcorp.org/debian stretch dc-net At the moment uploading is limited to users having shell access. == Sections == It is configured to allow these sections: * '''dc-net''': packages automatically available to DC machines * '''extra''': other packages for any other use (desktop, various user tools…) === Build for this Repository === To build for this repository you have to care about: * use a proper version numbering: ** '''~<suite>''' for backports ** '''~dc&lt;i&gt;''' / '''+dc&lt;i&gt;''' if there are DC-specific changes (the later can be appended to the backports suffix) * build with or without sources and orig tarball depending if this is your first upload to the DC repo or not ** for a first upload, or NUR, you will most likely use these sbuild options: -s -A --force-orig-source ** for subsequent uploads (except binary only for another architecture) you will most likely use these sbuild options: -A === Upload to this Repository === First, sign with your GPG key (using ''debsign''). You can upload using this <tt>dupload</tt> configuration snippet: # dupload does not support FTP TLS :-/ $cfg{'duckcorp'} = { fqdn => "toushirou.duckcorp.org", method => "scpb", incoming => "/srv/ftp/ftp.duckcorp.org/repository/dc-debian-incoming", # The dinstall on ftp-master sends emails itself dinstall_runs => 1, }; == Technical Details == This service is made using: * [http://mirrorer.alioth.debian.org/ reprepro] 5d28d19b83ad35f551ff3e9a9d9a4d0d64e014d6 717 712 2018-05-02T18:29:48Z Duck 2 wikitext text/x-wiki {{Template:Service | description = Packages repository, currently Debian packages only. Provide fixes and backported packages for DuckCorp. Specific sections can be created for users. No prerequisite for read access. | prerequisite = | account = local | ipv6 = true | security_notes = This service is secure. }} == Access == To install packages you can add the following in your '''/etc/apt/sources.list''': deb https://repository.duckcorp.org/debian stretch dc-net At the moment uploading is limited to users having shell access. == Sections == It is configured to allow these sections: * '''dc-net''': packages automatically available to DC machines * '''extra''': other packages for any other use (desktop, various user tools…) == Build for this Repository == To build for this repository you have to care about: * use a proper version numbering: ** '''~<suite>''' for backports ** '''~dc&lt;i&gt;''' / '''+dc&lt;i&gt;''' if there are DC-specific changes (the later can be appended to the backports suffix) * build with or without sources and orig tarball depending if this is your first upload to the DC repo or not ** for a first upload, or NUR, you will most likely use these sbuild options: -s -A --force-orig-source ** for subsequent uploads (except binary only for another architecture) you will most likely use these sbuild options: -A == Upload to this Repository == First, sign with your GPG key (using ''debsign''). You can upload using this <tt>dupload</tt> configuration snippet: # dupload does not support FTP TLS :-/ $cfg{'duckcorp'} = { fqdn => "toushirou.duckcorp.org", method => "scpb", incoming => "/srv/ftp/ftp.duckcorp.org/repository/dc-debian-incoming", # The dinstall on ftp-master sends emails itself dinstall_runs => 1, }; == Technical Details == This service is made using: * [http://mirrorer.alioth.debian.org/ reprepro] d6a7051d88dbe2e2e771ad67e19f1bf598b3472c 0 49 723 575 2018-06-06T11:29:28Z Duck 2 /* Retraining */ wikitext text/x-wiki {{Template:Service | description = Available services: * multiple email addresses (mailboxes+aliases or redirections) based on the ''milkypond.org'' (or maybe ''duckcorp.org'') domain * roaming accounts to be able to send emails wherever you are If you want email addresses using you own domain(s), see the [[Services/MailHosting|mail hosting service]]. | prerequisite = | account = global-reg | ipv6 = true | security_notes = Access to the mail services are fully secured, and to your data, nevertheless most mail exchange on the Internet are not. Complete security can be achieved using signed and encrypted mail (see [[wikipedia:Pretty_Good_Privacy|OpenPGP]] and [[wikipedia:S/MIME|S/MIME]]) }} == Access == === Using a Mail Reader === You can retrieve your mails, in case of a real mailbox, using either: * IMAP+TLS (TCP 143) / IMAPS (TCP 993) on imap.duckcorp.org * or POP3+TLS (TCP 110) / POP3S (TCP 995) on pop.duckcorp.org The IMAP protocol is recommended over POP3, as it provides many interesting features. If you want to download all your mails absolutely at home, loosing the ability to read your mail from anywhere on the planet, you can do that with IMAP too (look at your mail client settings). You can use our servers to send mails out too via smtp.duckcorp.org using: * SMTP+TLS (TCP 25) / SMTPS (TCP 465) * and SASL authentication === Using a Web Interface === A [https://webmail.duckcorp.org/ webmail interface] is available. == Antivirus and Antispam == Mails stored on our server are checked upon arrival for viruses and SPAMs. Mail redirected to a third party mailbox are not, not to mess with the strategy of the the final destination (which could arm learning greatly). Mails being viruses are suppressed automatically upon arrival. Once in a week, an extra antivirus check is done on all hosted mailboxes, to remove viruses not detected at the time it arrived (our antivirus database is updated daily), so you may see such mail disappear from your mailbox, don't fear. SPAMs are more difficult to detect, and it is an error-prone process, so we chose to use a learning software instead of using a global database. On the bright side of things, you would never loose mails and the software should be able to learn what is a SPAM from '''your''' point of view (which has proved to differ slightly between our users), but on the grey side you will have to teach him regularly to avoid errors. When your account is created, it acts like an empty headed body letting everything through, but after a few weeks of teaching it is able to recognize most of your habits and block a lot of annoying SPAM. === Web Interface === The web interface is an easy way to view your mail history, changes your settings, and more. It is available using this URL: https://spamfilter.duckcorp.org/ ==== User Settings ==== You can yourself setup a few parameters in the ''Preferences'' page of the [https://spamfilter.duckcorp.org/ web interface], mostly: * how the system should train: ** TEFT (''On every new message scanned by the filter''): useful to learn very quickly especially on a new mailbox or when you've got tons of spam on your addresses, but you need to train it regulary (daily is better) or it will learn wrong (very quickly too !) ** TOE (''Only when the filter makes a mistake''): slow learning, but if you don't have time for training very often or go on long holidays without internet access this mode will give you a stable behavior ** TUM (''Only with new data or if the filter makes a mistake''): trade-off between the two previous modes, learn quite fast and not too demanding, adapts better to new SPAMs then TOE * filter sensitivity: you can ask the system to be more or less aggressive * message handling: see [[#Delivery Mode|delivery mode]] below * ''Disable DSPAM filtering'': you may switch off filtering at your own risk We strongly recommend using TEFT with daily training for a few weeks then switching to TUM. If you need to go away for a long time, switching to TOE is recommended. Using the quarantine feature is also a safe choice, as the web interface is quite easy to use. === Delivery Mode === ==== Quarantine ==== With the ''message handling'' setting set to ''Quarantine the message'' (see [[#User Settings|user preferences]]), then your SPAMs will not go into your mailbox but stay in this stagging area. These mails are kept by the system until you decide their fate. Through the ''Quarantine'' page of the web interface, you can list these mails and: * free legitimate mails wrongly considered as SPAM by the system * delete real SPAMs if the system was right about them (freeing useful space) In this mode, you need to flush your quarantine once in a while. ==== Delivered with Special Header (default, recommended) ==== With the ''message handling'' setting set to ''Deliver the message normally with a X-DSPAM-Result header'', mails are delivered normally, but with a special field added to your mail headers (not always visible depending on your mail client and its configuration). This is quite handy if you prefer SPAMs arranged in a specific folder. You may use then the provided [[#Mail Filtering |filtering system]] to sort them properly, or configure your eMail client. ==== Delivered with Modified Subject (not recommended) ==== With the ''message handling'' setting set to ''Tag the Subject header with'', mails are delivered normally, but with a modified title to alert you this is a SPAM (which is a tad ugly). This mode is really not clean and not recommended, but it exist for historical purposes, so you might still use it if you really wish to. === Retraining === Teaching the system what is SPAM and HAM (non-SPAM) is called ''retraining''. If you have of create a folder named ''Junk'', then it is automatically magic: * if you drop mail into it, it is automatically retrained as SPAM * if you move it out of it, it is automatically retrained as HAM * with time, certain old mails automatically expire, see below To use this folder properly, SPAMs '''must''' be delivered in the ''Junk'' folder automatically, so you can move them out in case of error. If using the default settings, you just need to subscribe to this folder in your mail software (this folder is always auto-created). If you are using different setting, you need to select the [[#Delivered with Special Header|delivery mode using a special header]], and use the provided [[#Mail Filtering|filtering system]] to drop them in the ''Junk'' folder ('''Do not use your mail software for this filtering, this is horribly inefficient and might alter the learning badly'''). Automatic expiration logic, based on delivery time (and not the mail timestamp): * deleted mails are purged after 1 day * read mails without an important flag are purge after 7 days * unread mails without an important flag are purge after 30 days If you use the ''incoming_spam'' [[#Global_Rules|global rule]], then SPAMs newly discovered by the system are flagged as important, which means these mails will never by purged until you review it and decide to delete them or mark them as not important. Custom rules might play with this flag and achieve an automatic selection. == Mail Filtering == With your favourite mail client, you can probably filter your mails in proper folders already. Nevertheless, this can be an annoying operation: * blocking you mail client for a long time if you have to process plenty of mails * downloading each mail information, and sometimes content (depending on your filters), is lenghty too, and cost much bandwidth * syncing filters across your machines (home desktop, laptop, office machine…) is a pain in the ass * processing only when you're online prevents triggering actions in a timely manner (automatic redirect, vacation messages…), and running a machine 24/7 with a mail client polling new mails every 30s is not a solution We provide a much better way to do this using the [[wikipedia:Sieve_(mail_filtering_language)|SIEVE]] filters. Shortly, SIEVE is a language dedicated to expressing mail filters (also called ''rules''). Our server is able to process your mails according to these filters as soon as they arrive. You then don't have to care about them anymore, and may use light mail clients or webmails when you're not on your machine with your favourite software. === Rules Configuration === You can express sort/reject/vacation/… filters using these rules, as the capabilities are very rich. Several softwares support managing SIEVE rules: * Icedove/Thunderbird: *: using the SIEVE extension (in ''xul-ext-sieve'' Debian package), it provides a rules editor (for power-users) * Horde (Ingo): *: provides an easy to use web interface *: this webmail has been made available [https://webdesk.duckcorp.org/ here] * Squirrelmail: *: coupled with the Avelsieve extension, provides an easy to use web interface *: this webmail has been made available [https://webmail-sm.duckcorp.org/ here] * Roundcube: *: coupled with the sieverules extension, provides an easy to use web interface *: this webmail has been made available [https://webmail-rc.duckcorp.org/ here] * sieve-connect: *: provides a CLI to upload/download/activate your rules files *: this tool is available on [[Services/Shell|shell hosts]] (tell us if you know more software supporting this feature) To push your filters on the server, a dedicated protocol exists: MANAGESIEVE (TCP 4190) on ''sieve.duckcorp.org''. Our webmails are already configured to use it, but it you use sieve-connect from our hosts or your own mail software, you'll need these parameters. You can read more info about SIEVE here: * supported SIEVE features on our server: http://pigeonhole.dovecot.org/ * http://www.fastmail.fm/docs/sieve/ * http://sieve.info/ === Default Rules === The default settings (since 2112-02-11) are to use the global ''incoming_spam'' rule and the [[#Delivered with Special Header|delivery using a special header]], in order to provide a simple default configuration for most users. All other mails will end-up in your ''Inbox'' folder and you may then sort them by yourself. If you create your own rules, the default rules won't apply anymore, so power-users can replace the default behavior completely to achieve what they really need. === Global Rules === Global rules are provided to ease configuration on specific filters. They can easily be included in your own configuration. Available rules: * ''incoming_spam'': *: SPAMs will automatically be delivered in the ''Junk'' folder and marked as ''important'' *: you need to use the [[#Delivered with Special Header|delivery using a special header]] for this rule to have any effect If you write your own custom rules, here is an example on how to use one of them: require ["include"]; include :global "&lt;rule-name&gt;"; == Fetching eMails from an External Mailbox == {{todo}} == Shared/Public Folders == You may need to share mails or messages with friends or people you do stuff with (in a project or association). Depending on your needs, two solutions are possible: * share some of your own private folders, thus called ''shared folders'' * manage a special folder hierarchy, called ''public folders'' (even if they may not be accessible to everyone) *: if you need one, ask an administrator; the namespace name can be freely chosen but must be unambiguous and is subject to approval === Namespaces === Through IMAP, or our webmails internally using IMAP, it is possible to partition the folder hierarchy into ''namespaces''. Traditionally you are using the root namespace for your private folders. Additional namespaces can be created and will appear among your own folders or separate, depending on your mail client's choice of representation. To avoid name clashes, we decided to prefix all additional namespace names with a '''#'''. Since 2011-05-14, the following extra namespaces are created and reserved: * #Shared, containing all folders other users decided to share with you * #MilkyPond, containing public MP/DC informational mailboxes you may subscribe at will === Folders Permissions === Using IMAP, it is possible to setup rights (read only, write allowed…) to your own folders in order to share them with other users, or group of users. Public folders are owned by no-one, and must be created by the administrators. Once your request is accepted we will delegate its administration to your care. It can then can be managed like shared folders. === Software Support === Client mail softwares support: * Horde: *: support namespaces, shared folders configurable via ''Options->Share Folders'' menu but no ACLs for public folders * RoundCube: *: support namespaces, shared and public folders configurable via ''Settings->Folders'', selecting a folder then using the ''Sharing'' tab * Icedove/Thunderbird: *: support namespaces, shared and public folders configurable via folder selection and ''Tools->Imap-ACL'' menu action Most other softwares have namespace support only, so you should be able to use shared/public folders you have rights on but not configure them yourself (tell us if you know more software supporting this feature). == Limitations == === Maximum Mail Size === Mail you send or receive are limited to '''20MB'''. If you need to transmit much bigger data, then a mail transport is not appropriate, you'd better use a file sharing method instead. === Quotas === Even if it would be nice to live without it, we had to establish quotas to force people sort their mails out once in a while and delete useless things instead of leaving an ever-growing mess behind. The default quota is '''512MB''' which is not that big but should match needs of most users. This said, you may ask us for more and there's no reason we would refuse a reasonable demand. == Technical Details == This service is made using: * [http://www.postfix.org/ Postfix] * [http://dovecot.org/ Dovecot] * [http://dspam.sourceforge.net DSPAM] * [http://johannes.sipsolutions.net/Projects/dovecot-antispam dovecot-antispam] * [https://projects.duckcorp.org/projects/spoolinger Spoolinger] * [http://www.horde.org/ Horde] * [http://www.squirrelmail.org/ SquirrelMail] * [http://www.roundcube.net/ RoundCube] 7b6a719e6162180d5acf2b6a56bc6f0962167a45 734 723 2018-06-06T19:13:38Z Duck 2 wikitext text/x-wiki {{Template:Service | description = Available services: * multiple email addresses (mailboxes+aliases or redirections) based on the ''milkypond.org'' (or maybe ''duckcorp.org'') domain * roaming accounts to be able to send emails wherever you are If you want email addresses using you own domain(s), see the [[Services/MailHosting|mail hosting service]]. | prerequisite = | account = global-reg | ipv6 = true | security_notes = Access to the mail services are fully secured, and to your data, nevertheless most mail exchange on the Internet are not. Complete security can be achieved using signed and encrypted mail (see [[wikipedia:Pretty_Good_Privacy|OpenPGP]] and [[wikipedia:S/MIME|S/MIME]]) }} == Access == === Using a Mail Reader === You can retrieve your mails, in case of a real mailbox, using either: * IMAP+TLS (TCP 143) / IMAPS (TCP 993) on imap.duckcorp.org * or POP3+TLS (TCP 110) / POP3S (TCP 995) on pop.duckcorp.org The IMAP protocol is recommended over POP3, as it provides many interesting features. If you want to download all your mails absolutely at home, loosing the ability to read your mail from anywhere on the planet, you can do that with IMAP too (look at your mail client settings). You can use our servers to send mails out too via smtp.duckcorp.org using: * SMTP+TLS (TCP 25) / SMTPS (TCP 465) * and SASL authentication === Using a Web Interface === A [https://webmail.duckcorp.org/ webmail interface] is available. == Antivirus and Antispam == Mails stored on our server are checked upon arrival for viruses and SPAMs. Outgoing mails from our services are checked too. Mails being viruses are suppressed automatically upon arrival. Mails with a huge probability of being SPAM are destroyed too. Good mails and possibly spammy mails are delivered to your mailbox. SPAMs are more difficult to detect, and it is an error-prone process, so we chose to use a learning software instead of using a global database. After a few weeks of teaching it is able to recognize most of your habits and block a lot of annoying SPAM. === Probable SPAM Notification === Mails are delivered normally with a special field added (''X-Spam-Status'') to your mail headers (not always visible depending on your mail client and its configuration) indicating if the mail is a SPAM and its ''spamminess'' score. This is quite handy if you prefer SPAMs arranged in a specific folder. You may use then the provided [[#Mail Filtering |filtering system]] to sort them properly, or configure your eMail client. === Retraining === Teaching the system what is SPAM and HAM (non-SPAM) is called ''retraining''. If you have of create a folder named ''Junk'', then it is automatically magic: * if you drop mail into it, it is automatically retrained as SPAM * if you move it out of it, it is automatically retrained as HAM * with time, certain old mails automatically expire, see below To use this folder properly, SPAMs '''must''' be delivered in the ''Junk'' folder automatically, so you can move them out in case of error. You just need to subscribe to this folder in your mail software (this folder is always auto-created). It is not recommended to use your mail software for this filtering, this is horribly inefficient and you would have to set things up on each device and manually synchronize your settings. Automatic expiration logic, based on delivery time (and not the mail timestamp): * deleted mails are purged after 1 day * read mails without an important flag are purge after 7 days * unread mails without an important flag are purge after 30 days If you use the ''incoming_spam'' [[#Global_Rules|global rule]], then SPAMs newly discovered by the system are flagged as important, which means these mails will never by purged until you review it and decide to delete them or mark them as not important. Custom rules might play with this flag and achieve an automatic selection. == Mail Filtering == With your favourite mail client, you can probably filter your mails in proper folders already. Nevertheless, this can be an annoying operation: * blocking you mail client for a long time if you have to process plenty of mails * downloading each mail information, and sometimes content (depending on your filters), is lenghty too, and cost much bandwidth * syncing filters across your machines (home desktop, laptop, office machine…) is a pain in the ass * processing only when you're online prevents triggering actions in a timely manner (automatic redirect, vacation messages…), and running a machine 24/7 with a mail client polling new mails every 30s is not a solution We provide a much better way to do this using the [[wikipedia:Sieve_(mail_filtering_language)|SIEVE]] filters. Shortly, SIEVE is a language dedicated to expressing mail filters (also called ''rules''). Our server is able to process your mails according to these filters as soon as they arrive. You then don't have to care about them anymore, and may use light mail clients or webmails when you're not on your machine with your favourite software. === Rules Configuration === You can express sort/reject/vacation/… filters using these rules, as the capabilities are very rich. Several softwares support managing SIEVE rules: * Icedove/Thunderbird: *: using the SIEVE extension (in ''xul-ext-sieve'' Debian package), it provides a rules editor (for power-users) * Roundcube: *: coupled with the sieverules extension, provides an easy to use web interface *: this webmail has been made available [https://webmail.duckcorp.org/ here] * sieve-connect: *: provides a CLI to upload/download/activate your rules files *: this tool is available on [[Services/Shell|shell hosts]] (tell us if you know more software supporting this feature) To push your filters on the server, a dedicated protocol exists: MANAGESIEVE (TCP 4190) on ''sieve.duckcorp.org''. Our webmails are already configured to use it, but it you use sieve-connect from our hosts or your own mail software, you'll need these parameters. You can read more info about SIEVE here: * supported SIEVE features on our server: http://pigeonhole.dovecot.org/ * http://www.fastmail.fm/docs/sieve/ * http://sieve.info/ === Default Rules === The default settings (since 2112-02-11) are to use the global ''incoming_spam'' rule (see below), in order to provide a simple default configuration for most users. All other mails will end-up in your ''Inbox'' folder and you may then sort them by yourself. If you create your own rules, the default rules won't apply anymore, so power-users can replace the default behavior completely to achieve what they really need. === Global Rules === Global rules are provided to ease configuration on specific filters. They can easily be included in your own configuration. Available rules: * ''incoming_spam'': *: SPAMs will automatically be delivered in the ''Junk'' folder and marked as ''important'' If you write your own custom rules, here is an example on how to use one of them: require ["include"]; include :global "&lt;rule-name&gt;"; == Fetching eMails from an External Mailbox == {{todo}} == Shared/Public Folders == You may need to share mails or messages with friends or people you do stuff with (in a project or association). Depending on your needs, two solutions are possible: * share some of your own private folders, thus called ''shared folders'' * manage a special folder hierarchy, called ''public folders'' (even if they may not be accessible to everyone) *: if you need one, ask an administrator; the namespace name can be freely chosen but must be unambiguous and is subject to approval === Namespaces === Through IMAP, or our webmails internally using IMAP, it is possible to partition the folder hierarchy into ''namespaces''. Traditionally you are using the root namespace for your private folders. Additional namespaces can be created and will appear among your own folders or separate, depending on your mail client's choice of representation. To avoid name clashes, we decided to prefix all additional namespace names with a '''#'''. Since 2011-05-14, the following extra namespaces are created and reserved: * #Shared, containing all folders other users decided to share with you * #MilkyPond, containing public MP/DC informational mailboxes you may subscribe at will === Folders Permissions === Using IMAP, it is possible to setup rights (read only, write allowed…) to your own folders in order to share them with other users, or group of users. Public folders are owned by no-one, and must be created by the administrators. Once your request is accepted we will delegate its administration to your care. It can then can be managed like shared folders. === Software Support === Client mail softwares support: * Horde: *: support namespaces, shared folders configurable via ''Options->Share Folders'' menu but no ACLs for public folders * RoundCube: *: support namespaces, shared and public folders configurable via ''Settings->Folders'', selecting a folder then using the ''Sharing'' tab * Icedove/Thunderbird: *: support namespaces, shared and public folders configurable via folder selection and ''Tools->Imap-ACL'' menu action Most other softwares have namespace support only, so you should be able to use shared/public folders you have rights on but not configure them yourself (tell us if you know more software supporting this feature). == Limitations == === Maximum Mail Size === Mail you send or receive are limited to '''20MB'''. If you need to transmit much bigger data, then a mail transport is not appropriate, you'd better use a file sharing method instead. === Quotas === Even if it would be nice to live without it, we had to establish quotas to force people sort their mails out once in a while and delete useless things instead of leaving an ever-growing mess behind. The default quota is '''512MB''' which is not that big but should match needs of most users. This said, you may ask us for more and there's no reason we would refuse a reasonable demand. == Technical Details == This service is made using: * [https://www.postfix.org/ Postfix] * [https://dovecot.org/ Dovecot] * [https://johannes.sipsolutions.net/Projects/dovecot-antispam dovecot-antispam] * [https://projects.duckcorp.org/projects/spoolinger Spoolinger] * [https://rspamd.com/ Rspamd] * [https://www.roundcube.net/ RoundCube] adce47e25bf2c87243b29f5cd9015b597238183d 742 734 2018-12-06T03:19:11Z Duck 2 wikitext text/x-wiki {{Template:Service | description = Available services: * multiple email addresses (mailboxes+aliases or redirections) based on the ''milkypond.org'' (or maybe ''duckcorp.org'') domain * roaming accounts to be able to send emails wherever you are If you want email addresses using you own domain(s), see the [[Services/MailHosting|mail hosting service]]. | prerequisite = | account = global-reg | ipv6 = true | security_notes = Access to the mail services are fully secured, and to your data, nevertheless most mail exchange on the Internet are not. Complete security can be achieved using signed and encrypted mail (see [[wikipedia:Pretty_Good_Privacy|OpenPGP]] and [[wikipedia:S/MIME|S/MIME]]) }} == Access == === Using a Mail Reader === You can retrieve your mails, in case of a real mailbox, using either: * IMAP+TLS (TCP 143) / IMAPS (TCP 993) on imap.duckcorp.org * or POP3+TLS (TCP 110) / POP3S (TCP 995) on pop.duckcorp.org The IMAP protocol is recommended over POP3, as it provides many interesting features. If you want to download all your mails absolutely at home, loosing the ability to read your mail from anywhere on the planet, you can do that with IMAP too (look at your mail client settings). You can use our servers to send mails out too via smtp.duckcorp.org using: * SUBMISSION (TCP 587) which is the recommended way and has less chance to be filtered, or alternatively SMTP+TLS (TCP 25) / SMTPS (TCP 465) * and SASL authentication === Using a Web Interface === A [https://webmail.duckcorp.org/ webmail interface] is available. == Antivirus and Antispam == Mails stored on our server are checked upon arrival for viruses and SPAMs. Outgoing mails from our services are checked too. Mails being viruses are suppressed automatically upon arrival. Mails with a huge probability of being SPAM are destroyed too. Good mails and possibly spammy mails are delivered to your mailbox. SPAMs are more difficult to detect, and it is an error-prone process, so we chose to use a learning software instead of using a global database. After a few weeks of teaching it is able to recognize most of your habits and block a lot of annoying SPAM. === Probable SPAM Notification === Mails are delivered normally with a special field added (''X-Spam-Status'') to your mail headers (not always visible depending on your mail client and its configuration) indicating if the mail is a SPAM and its ''spamminess'' score. This is quite handy if you prefer SPAMs arranged in a specific folder. You may use then the provided [[#Mail Filtering |filtering system]] to sort them properly, or configure your eMail client. === Retraining === Teaching the system what is SPAM and HAM (non-SPAM) is called ''retraining''. If you have of create a folder named ''Junk'', then it is automatically magic: * if you drop mail into it, it is automatically retrained as SPAM * if you move it out of it, it is automatically retrained as HAM * with time, certain old mails automatically expire, see below To use this folder properly, SPAMs '''must''' be delivered in the ''Junk'' folder automatically, so you can move them out in case of error. You just need to subscribe to this folder in your mail software (this folder is always auto-created). It is not recommended to use your mail software for this filtering, this is horribly inefficient and you would have to set things up on each device and manually synchronize your settings. Automatic expiration logic, based on delivery time (and not the mail timestamp): * deleted mails are purged after 1 day * read mails without an important flag are purge after 7 days * unread mails without an important flag are purge after 30 days If you use the ''incoming_spam'' [[#Global_Rules|global rule]], then SPAMs newly discovered by the system are flagged as important, which means these mails will never by purged until you review it and decide to delete them or mark them as not important. Custom rules might play with this flag and achieve an automatic selection. == Mail Filtering == With your favourite mail client, you can probably filter your mails in proper folders already. Nevertheless, this can be an annoying operation: * blocking you mail client for a long time if you have to process plenty of mails * downloading each mail information, and sometimes content (depending on your filters), is lenghty too, and cost much bandwidth * syncing filters across your machines (home desktop, laptop, office machine…) is a pain in the ass * processing only when you're online prevents triggering actions in a timely manner (automatic redirect, vacation messages…), and running a machine 24/7 with a mail client polling new mails every 30s is not a solution We provide a much better way to do this using the [[wikipedia:Sieve_(mail_filtering_language)|SIEVE]] filters. Shortly, SIEVE is a language dedicated to expressing mail filters (also called ''rules''). Our server is able to process your mails according to these filters as soon as they arrive. You then don't have to care about them anymore, and may use light mail clients or webmails when you're not on your machine with your favourite software. === Rules Configuration === You can express sort/reject/vacation/… filters using these rules, as the capabilities are very rich. Several softwares support managing SIEVE rules: * Icedove/Thunderbird: *: using the SIEVE extension (in ''xul-ext-sieve'' Debian package), it provides a rules editor (for power-users) * Roundcube: *: coupled with the sieverules extension, provides an easy to use web interface *: this webmail has been made available [https://webmail.duckcorp.org/ here] * sieve-connect: *: provides a CLI to upload/download/activate your rules files *: this tool is available on [[Services/Shell|shell hosts]] (tell us if you know more software supporting this feature) To push your filters on the server, a dedicated protocol exists: MANAGESIEVE (TCP 4190) on ''sieve.duckcorp.org''. Our webmails are already configured to use it, but it you use sieve-connect from our hosts or your own mail software, you'll need these parameters. You can read more info about SIEVE here: * supported SIEVE features on our server: http://pigeonhole.dovecot.org/ * http://www.fastmail.fm/docs/sieve/ * http://sieve.info/ === Default Rules === The default settings (since 2112-02-11) are to use the global ''incoming_spam'' rule (see below), in order to provide a simple default configuration for most users. All other mails will end-up in your ''Inbox'' folder and you may then sort them by yourself. If you create your own rules, the default rules won't apply anymore, so power-users can replace the default behavior completely to achieve what they really need. === Global Rules === Global rules are provided to ease configuration on specific filters. They can easily be included in your own configuration. Available rules: * ''incoming_spam'': *: SPAMs will automatically be delivered in the ''Junk'' folder and marked as ''important'' If you write your own custom rules, here is an example on how to use one of them: require ["include"]; include :global "&lt;rule-name&gt;"; == Fetching eMails from an External Mailbox == {{todo}} == Shared/Public Folders == You may need to share mails or messages with friends or people you do stuff with (in a project or association). Depending on your needs, two solutions are possible: * share some of your own private folders, thus called ''shared folders'' * manage a special folder hierarchy, called ''public folders'' (even if they may not be accessible to everyone) *: if you need one, ask an administrator; the namespace name can be freely chosen but must be unambiguous and is subject to approval === Namespaces === Through IMAP, or our webmails internally using IMAP, it is possible to partition the folder hierarchy into ''namespaces''. Traditionally you are using the root namespace for your private folders. Additional namespaces can be created and will appear among your own folders or separate, depending on your mail client's choice of representation. To avoid name clashes, we decided to prefix all additional namespace names with a '''#'''. Since 2011-05-14, the following extra namespaces are created and reserved: * #Shared, containing all folders other users decided to share with you * #MilkyPond, containing public MP/DC informational mailboxes you may subscribe at will === Folders Permissions === Using IMAP, it is possible to setup rights (read only, write allowed…) to your own folders in order to share them with other users, or group of users. Public folders are owned by no-one, and must be created by the administrators. Once your request is accepted we will delegate its administration to your care. It can then can be managed like shared folders. === Software Support === Client mail softwares support: * RoundCube: *: support namespaces, shared and public folders configurable via ''Settings->Folders'', selecting a folder then using the ''Sharing'' tab * Icedove/Thunderbird: *: support namespaces, shared and public folders configurable via folder selection and ''Tools->Imap-ACL'' menu action Most other softwares have namespace support only, so you should be able to use shared/public folders you have rights on but not configure them yourself (tell us if you know more software supporting this feature). == Limitations == === Maximum Mail Size === Mail you send or receive are limited to '''20MB'''. If you need to transmit much bigger data, then a mail transport is not appropriate, you'd better use a file sharing method instead. === Quotas === Even if it would be nice to live without it, we had to establish quotas to force people sort their mails out once in a while and delete useless things instead of leaving an ever-growing mess behind. The default quota is '''512MB''' which is not that big but should match needs of most users. This said, you may ask us for more and there's no reason we would refuse a reasonable demand. == Technical Details == This service is made using: * [https://www.postfix.org/ Postfix] * [https://dovecot.org/ Dovecot] * [https://johannes.sipsolutions.net/Projects/dovecot-antispam dovecot-antispam] * [https://projects.duckcorp.org/projects/spoolinger Spoolinger] * [https://rspamd.com/ Rspamd] * [https://www.roundcube.net/ RoundCube] 303b053ddfe2de82ef3ea6b219fe784a113ba890 749 742 2018-12-06T09:05:57Z Duck 2 wikitext text/x-wiki {{Template:Service | description = Available services: * multiple email addresses (mailboxes+aliases or redirections) based on the ''milkypond.org'' (or maybe ''duckcorp.org'') domain * roaming accounts to be able to send emails wherever you are If you want email addresses using you own domain(s), see the [[Services/MailHosting|mail hosting service]]. | prerequisite = | account = global-reg | ipv6 = true | security_notes = Access to the mail services are fully secured, and to your data, nevertheless most mail exchange on the Internet are not. Complete security can be achieved using signed and encrypted mail (see [[wikipedia:Pretty_Good_Privacy|OpenPGP]] and [[wikipedia:S/MIME|S/MIME]]) }} == Access == === Using a Mail Reader === You can retrieve your mails, in case of a real mailbox, using either: * IMAP+TLS (TCP 143) / IMAPS (TCP 993) on imap.duckcorp.org * or POP3+TLS (TCP 110) / POP3S (TCP 995) on pop.duckcorp.org The IMAP protocol is recommended over POP3, as it provides many interesting features. If you want to download all your mails absolutely at home, loosing the ability to read your mail from anywhere on the planet, you can do that with IMAP too (look at your mail client settings). You can use our servers to send mails out too via smtp.duckcorp.org using: * SUBMISSION (TCP 587) which is the recommended way and has less chance to be filtered, or alternatively SMTP+TLS (TCP 25) / SMTPS (TCP 465) * and SASL authentication === Using a Web Interface === A [https://webmail.duckcorp.org/ webmail interface] is available. == Antivirus and Antispam == Mails stored on our server are checked upon arrival for viruses and SPAMs. Outgoing mails from our services are checked too. Mails being viruses are suppressed automatically upon arrival. Mails with a huge probability of being SPAM are destroyed too. Good mails and possibly spammy mails are delivered to your mailbox. SPAMs are more difficult to detect, and it is an error-prone process, so we chose to use a learning software instead of using a global database. After a few weeks of teaching it is able to recognize most of your habits and block a lot of annoying SPAM. === Probable SPAM Notification === Mails are delivered normally with a special field added (''X-Spam-Status'') to your mail headers (not always visible depending on your mail client and its configuration) indicating if the mail is a SPAM and its ''spamminess'' score. This is quite handy if you prefer SPAMs arranged in a specific folder. You may use then the provided [[#Mail Filtering |filtering system]] to sort them properly, or configure your eMail client. === Retraining === Teaching the system what is SPAM and HAM (non-SPAM) is called ''retraining''. If you have of create a folder named ''Junk'', then it is automatically magic: * if you drop mail into it, it is automatically retrained as SPAM * if you move it out of it, it is automatically retrained as HAM * with time, certain old mails automatically expire, see below To use this folder properly, SPAMs '''must''' be delivered in the ''Junk'' folder automatically, so you can move them out in case of error. You just need to subscribe to this folder in your mail software (this folder is always auto-created). It is not recommended to use your mail software for this filtering, this is horribly inefficient and you would have to set things up on each device and manually synchronize your settings. Automatic expiration logic, based on delivery time (and not the mail timestamp): * deleted mails are purged after 1 day * read mails without an important flag are purge after 7 days * unread mails without an important flag are purge after 30 days If you use the ''incoming_spam'' [[#Global_Rules|global rule]], then SPAMs newly discovered by the system are flagged as important, which means these mails will never by purged until you review it and decide to delete them or mark them as not important. Custom rules might play with this flag and achieve an automatic selection. == Mail Filtering == With your favourite mail client, you can probably filter your mails in proper folders already. Nevertheless, this can be an annoying operation: * blocking you mail client for a long time if you have to process plenty of mails * downloading each mail information, and sometimes content (depending on your filters), is lenghty too, and cost much bandwidth * syncing filters across your machines (home desktop, laptop, office machine…) is a pain in the ass * processing only when you're online prevents triggering actions in a timely manner (automatic redirect, vacation messages…), and running a machine 24/7 with a mail client polling new mails every 30s is not a solution We provide a much better way to do this using the [[wikipedia:Sieve_(mail_filtering_language)|SIEVE]] filters. Shortly, SIEVE is a language dedicated to expressing mail filters (also called ''rules''). Our server is able to process your mails according to these filters as soon as they arrive. You then don't have to care about them anymore, and may use light mail clients or webmails when you're not on your machine with your favourite software. === Rules Configuration === You can express sort/reject/vacation/… filters using these rules, as the capabilities are very rich. Several softwares support managing SIEVE rules: * Icedove/Thunderbird: *: using the SIEVE extension (in ''xul-ext-sieve'' Debian package), it provides a rules editor (for power-users) * Roundcube: *: coupled with the sieverules extension, provides an easy to use web interface *: this webmail has been made available [https://webmail.duckcorp.org/ here] * sieve-connect: *: provides a CLI to upload/download/activate your rules files *: this tool is available on [[Services/Shell|shell hosts]] (tell us if you know more software supporting this feature) To push your filters on the server, a dedicated protocol exists: MANAGESIEVE (TCP 4190) on ''sieve.duckcorp.org''. Our webmails are already configured to use it, but it you use sieve-connect from our hosts or your own mail software, you'll need these parameters. You can read more info about SIEVE here: * supported SIEVE features on our server: http://pigeonhole.dovecot.org/ * http://www.fastmail.fm/docs/sieve/ * http://sieve.info/ === Global Rules === Global rules are provided to ease configuration on specific filters. They can easily be included in your own configuration. Available rules: * ''incoming_spam'': *: SPAMs will automatically be delivered in the ''Junk'' folder and marked as ''important'' If you write your own custom rules, here is an example on how to use one of them: require ["include"]; include :global "&lt;rule-name&gt;"; === Default Rules === The default settings (since 2112-02-11) are to use the global ''incoming_spam'' rule (see below), in order to provide a simple default configuration for most users. All other mails will end-up in your ''Inbox'' folder and you may then sort them by yourself. If you create your own rules, the default rules won't apply anymore, so power-users can replace the default behavior completely to achieve what they really need. If you want to use the default behavior you can use: require ["include"]; include :global "incoming_spam"; You can also take advantage of the antispam spaminess score to use a different threshold like this: require ["fileinto", "spamtestplus", "relational", "comparator-i;ascii-numeric"]; # if SPAM score is >37% then move into the junk box if spamtest :percent :value "gt" :comparator "i;ascii-numeric" "37" { fileinto "Junk"; stop; } == Fetching eMails from an External Mailbox == {{todo}} == Shared/Public Folders == You may need to share mails or messages with friends or people you do stuff with (in a project or association). Depending on your needs, two solutions are possible: * share some of your own private folders, thus called ''shared folders'' * manage a special folder hierarchy, called ''public folders'' (even if they may not be accessible to everyone) *: if you need one, ask an administrator; the namespace name can be freely chosen but must be unambiguous and is subject to approval === Namespaces === Through IMAP, or our webmails internally using IMAP, it is possible to partition the folder hierarchy into ''namespaces''. Traditionally you are using the root namespace for your private folders. Additional namespaces can be created and will appear among your own folders or separate, depending on your mail client's choice of representation. To avoid name clashes, we decided to prefix all additional namespace names with a '''#'''. Since 2011-05-14, the following extra namespaces are created and reserved: * #Shared, containing all folders other users decided to share with you * #MilkyPond, containing public MP/DC informational mailboxes you may subscribe at will === Folders Permissions === Using IMAP, it is possible to setup rights (read only, write allowed…) to your own folders in order to share them with other users, or group of users. Public folders are owned by no-one, and must be created by the administrators. Once your request is accepted we will delegate its administration to your care. It can then can be managed like shared folders. === Software Support === Client mail softwares support: * RoundCube: *: support namespaces, shared and public folders configurable via ''Settings->Folders'', selecting a folder then using the ''Sharing'' tab * Icedove/Thunderbird: *: support namespaces, shared and public folders configurable via folder selection and ''Tools->Imap-ACL'' menu action Most other softwares have namespace support only, so you should be able to use shared/public folders you have rights on but not configure them yourself (tell us if you know more software supporting this feature). == Limitations == === Maximum Mail Size === Mail you send or receive are limited to '''20MB'''. If you need to transmit much bigger data, then a mail transport is not appropriate, you'd better use a file sharing method instead. === Quotas === Even if it would be nice to live without it, we had to establish quotas to force people sort their mails out once in a while and delete useless things instead of leaving an ever-growing mess behind. The default quota is '''512MB''' which is not that big but should match needs of most users. This said, you may ask us for more and there's no reason we would refuse a reasonable demand. == Technical Details == This service is made using: * [https://www.postfix.org/ Postfix] * [https://dovecot.org/ Dovecot] * [https://johannes.sipsolutions.net/Projects/dovecot-antispam dovecot-antispam] * [https://projects.duckcorp.org/projects/spoolinger Spoolinger] * [https://rspamd.com/ Rspamd] * [https://www.roundcube.net/ RoundCube] d60bb1d8fab558a13fbf7df57541a31fb0b6382b 762 749 2018-12-19T07:41:41Z Duck 2 /* Technical Details */ wikitext text/x-wiki {{Template:Service | description = Available services: * multiple email addresses (mailboxes+aliases or redirections) based on the ''milkypond.org'' (or maybe ''duckcorp.org'') domain * roaming accounts to be able to send emails wherever you are If you want email addresses using you own domain(s), see the [[Services/MailHosting|mail hosting service]]. | prerequisite = | account = global-reg | ipv6 = true | security_notes = Access to the mail services are fully secured, and to your data, nevertheless most mail exchange on the Internet are not. Complete security can be achieved using signed and encrypted mail (see [[wikipedia:Pretty_Good_Privacy|OpenPGP]] and [[wikipedia:S/MIME|S/MIME]]) }} == Access == === Using a Mail Reader === You can retrieve your mails, in case of a real mailbox, using either: * IMAP+TLS (TCP 143) / IMAPS (TCP 993) on imap.duckcorp.org * or POP3+TLS (TCP 110) / POP3S (TCP 995) on pop.duckcorp.org The IMAP protocol is recommended over POP3, as it provides many interesting features. If you want to download all your mails absolutely at home, loosing the ability to read your mail from anywhere on the planet, you can do that with IMAP too (look at your mail client settings). You can use our servers to send mails out too via smtp.duckcorp.org using: * SUBMISSION (TCP 587) which is the recommended way and has less chance to be filtered, or alternatively SMTP+TLS (TCP 25) / SMTPS (TCP 465) * and SASL authentication === Using a Web Interface === A [https://webmail.duckcorp.org/ webmail interface] is available. == Antivirus and Antispam == Mails stored on our server are checked upon arrival for viruses and SPAMs. Outgoing mails from our services are checked too. Mails being viruses are suppressed automatically upon arrival. Mails with a huge probability of being SPAM are destroyed too. Good mails and possibly spammy mails are delivered to your mailbox. SPAMs are more difficult to detect, and it is an error-prone process, so we chose to use a learning software instead of using a global database. After a few weeks of teaching it is able to recognize most of your habits and block a lot of annoying SPAM. === Probable SPAM Notification === Mails are delivered normally with a special field added (''X-Spam-Status'') to your mail headers (not always visible depending on your mail client and its configuration) indicating if the mail is a SPAM and its ''spamminess'' score. This is quite handy if you prefer SPAMs arranged in a specific folder. You may use then the provided [[#Mail Filtering |filtering system]] to sort them properly, or configure your eMail client. === Retraining === Teaching the system what is SPAM and HAM (non-SPAM) is called ''retraining''. If you have of create a folder named ''Junk'', then it is automatically magic: * if you drop mail into it, it is automatically retrained as SPAM * if you move it out of it, it is automatically retrained as HAM * with time, certain old mails automatically expire, see below To use this folder properly, SPAMs '''must''' be delivered in the ''Junk'' folder automatically, so you can move them out in case of error. You just need to subscribe to this folder in your mail software (this folder is always auto-created). It is not recommended to use your mail software for this filtering, this is horribly inefficient and you would have to set things up on each device and manually synchronize your settings. Automatic expiration logic, based on delivery time (and not the mail timestamp): * deleted mails are purged after 1 day * read mails without an important flag are purge after 7 days * unread mails without an important flag are purge after 30 days If you use the ''incoming_spam'' [[#Global_Rules|global rule]], then SPAMs newly discovered by the system are flagged as important, which means these mails will never by purged until you review it and decide to delete them or mark them as not important. Custom rules might play with this flag and achieve an automatic selection. == Mail Filtering == With your favourite mail client, you can probably filter your mails in proper folders already. Nevertheless, this can be an annoying operation: * blocking you mail client for a long time if you have to process plenty of mails * downloading each mail information, and sometimes content (depending on your filters), is lenghty too, and cost much bandwidth * syncing filters across your machines (home desktop, laptop, office machine…) is a pain in the ass * processing only when you're online prevents triggering actions in a timely manner (automatic redirect, vacation messages…), and running a machine 24/7 with a mail client polling new mails every 30s is not a solution We provide a much better way to do this using the [[wikipedia:Sieve_(mail_filtering_language)|SIEVE]] filters. Shortly, SIEVE is a language dedicated to expressing mail filters (also called ''rules''). Our server is able to process your mails according to these filters as soon as they arrive. You then don't have to care about them anymore, and may use light mail clients or webmails when you're not on your machine with your favourite software. === Rules Configuration === You can express sort/reject/vacation/… filters using these rules, as the capabilities are very rich. Several softwares support managing SIEVE rules: * Icedove/Thunderbird: *: using the SIEVE extension (in ''xul-ext-sieve'' Debian package), it provides a rules editor (for power-users) * Roundcube: *: coupled with the sieverules extension, provides an easy to use web interface *: this webmail has been made available [https://webmail.duckcorp.org/ here] * sieve-connect: *: provides a CLI to upload/download/activate your rules files *: this tool is available on [[Services/Shell|shell hosts]] (tell us if you know more software supporting this feature) To push your filters on the server, a dedicated protocol exists: MANAGESIEVE (TCP 4190) on ''sieve.duckcorp.org''. Our webmails are already configured to use it, but it you use sieve-connect from our hosts or your own mail software, you'll need these parameters. You can read more info about SIEVE here: * supported SIEVE features on our server: http://pigeonhole.dovecot.org/ * http://www.fastmail.fm/docs/sieve/ * http://sieve.info/ === Global Rules === Global rules are provided to ease configuration on specific filters. They can easily be included in your own configuration. Available rules: * ''incoming_spam'': *: SPAMs will automatically be delivered in the ''Junk'' folder and marked as ''important'' If you write your own custom rules, here is an example on how to use one of them: require ["include"]; include :global "&lt;rule-name&gt;"; === Default Rules === The default settings (since 2112-02-11) are to use the global ''incoming_spam'' rule (see below), in order to provide a simple default configuration for most users. All other mails will end-up in your ''Inbox'' folder and you may then sort them by yourself. If you create your own rules, the default rules won't apply anymore, so power-users can replace the default behavior completely to achieve what they really need. If you want to use the default behavior you can use: require ["include"]; include :global "incoming_spam"; You can also take advantage of the antispam spaminess score to use a different threshold like this: require ["fileinto", "spamtestplus", "relational", "comparator-i;ascii-numeric"]; # if SPAM score is >37% then move into the junk box if spamtest :percent :value "gt" :comparator "i;ascii-numeric" "37" { fileinto "Junk"; stop; } == Fetching eMails from an External Mailbox == {{todo}} == Shared/Public Folders == You may need to share mails or messages with friends or people you do stuff with (in a project or association). Depending on your needs, two solutions are possible: * share some of your own private folders, thus called ''shared folders'' * manage a special folder hierarchy, called ''public folders'' (even if they may not be accessible to everyone) *: if you need one, ask an administrator; the namespace name can be freely chosen but must be unambiguous and is subject to approval === Namespaces === Through IMAP, or our webmails internally using IMAP, it is possible to partition the folder hierarchy into ''namespaces''. Traditionally you are using the root namespace for your private folders. Additional namespaces can be created and will appear among your own folders or separate, depending on your mail client's choice of representation. To avoid name clashes, we decided to prefix all additional namespace names with a '''#'''. Since 2011-05-14, the following extra namespaces are created and reserved: * #Shared, containing all folders other users decided to share with you * #MilkyPond, containing public MP/DC informational mailboxes you may subscribe at will === Folders Permissions === Using IMAP, it is possible to setup rights (read only, write allowed…) to your own folders in order to share them with other users, or group of users. Public folders are owned by no-one, and must be created by the administrators. Once your request is accepted we will delegate its administration to your care. It can then can be managed like shared folders. === Software Support === Client mail softwares support: * RoundCube: *: support namespaces, shared and public folders configurable via ''Settings->Folders'', selecting a folder then using the ''Sharing'' tab * Icedove/Thunderbird: *: support namespaces, shared and public folders configurable via folder selection and ''Tools->Imap-ACL'' menu action Most other softwares have namespace support only, so you should be able to use shared/public folders you have rights on but not configure them yourself (tell us if you know more software supporting this feature). == Limitations == === Maximum Mail Size === Mail you send or receive are limited to '''20MB'''. If you need to transmit much bigger data, then a mail transport is not appropriate, you'd better use a file sharing method instead. === Quotas === Even if it would be nice to live without it, we had to establish quotas to force people sort their mails out once in a while and delete useless things instead of leaving an ever-growing mess behind. The default quota is '''512MB''' which is not that big but should match needs of most users. This said, you may ask us for more and there's no reason we would refuse a reasonable demand. == Technical Details == This service is made using: * [https://www.postfix.org/ Postfix] * [https://dovecot.org/ Dovecot] * [https://projects.duckcorp.org/projects/spoolinger Spoolinger] * [https://rspamd.com/ Rspamd] * [https://www.roundcube.net/ RoundCube] e5be1f5dd016150e49b4f688a73a34f436681aaf 775 762 2019-04-09T07:26:14Z Duck 2 /* Antivirus and Antispam */ wikitext text/x-wiki {{Template:Service | description = Available services: * multiple email addresses (mailboxes+aliases or redirections) based on the ''milkypond.org'' (or maybe ''duckcorp.org'') domain * roaming accounts to be able to send emails wherever you are If you want email addresses using you own domain(s), see the [[Services/MailHosting|mail hosting service]]. | prerequisite = | account = global-reg | ipv6 = true | security_notes = Access to the mail services are fully secured, and to your data, nevertheless most mail exchange on the Internet are not. Complete security can be achieved using signed and encrypted mail (see [[wikipedia:Pretty_Good_Privacy|OpenPGP]] and [[wikipedia:S/MIME|S/MIME]]) }} == Access == === Using a Mail Reader === You can retrieve your mails, in case of a real mailbox, using either: * IMAP+TLS (TCP 143) / IMAPS (TCP 993) on imap.duckcorp.org * or POP3+TLS (TCP 110) / POP3S (TCP 995) on pop.duckcorp.org The IMAP protocol is recommended over POP3, as it provides many interesting features. If you want to download all your mails absolutely at home, loosing the ability to read your mail from anywhere on the planet, you can do that with IMAP too (look at your mail client settings). You can use our servers to send mails out too via smtp.duckcorp.org using: * SUBMISSION (TCP 587) which is the recommended way and has less chance to be filtered, or alternatively SMTP+TLS (TCP 25) / SMTPS (TCP 465) * and SASL authentication === Using a Web Interface === A [https://webmail.duckcorp.org/ webmail interface] is available. == Antivirus and Antispam == Mails stored on our server are checked upon arrival for viruses and SPAMs. Outgoing mails from our services are checked too. Mails being viruses are suppressed automatically upon arrival. Mails with a huge probability of being SPAM are destroyed too. Good mails and possibly spammy mails are delivered to your mailbox. SPAMs are more difficult to detect, and it is an error-prone process, so we chose to use a learning software instead of using a global database. After a few weeks of teaching it is able to recognize most of your habits and block a lot of annoying SPAM. === Probable SPAM Notification === Mails are delivered normally with a special field added (''X-Spam-Status'') to your mail headers (not always visible depending on your mail client and its configuration) indicating if the mail is a SPAM and its ''spamminess'' score. This is quite handy if you prefer SPAMs arranged in a specific folder. You may use then the provided [[#Mail Filtering |filtering system]] to sort them properly, or configure your eMail client. === Retraining === Teaching the system what is SPAM and HAM (non-SPAM) is called ''retraining''. If you have of create a folder named ''Junk'', then it is automatically magic: * if you move mail into it, it is automatically retrained as SPAM * if you move mail out of it, it is automatically retrained as HAM * with time, certain old mails automatically expire, see below If you are using an IMAP Sync client which does not support the MOVE operation (isync, offlineimap…) then you unfortunately cannot use this method, please look at the next chapter. To use this folder properly, SPAMs '''must''' be delivered in the ''Junk'' folder automatically, so you can move them out in case of error. You just need to subscribe to this folder in your mail software (this folder is always auto-created). It is not recommended to use your mail software for this filtering, this is horribly inefficient and you would have to set things up on each device and manually synchronize your settings. Automatic expiration logic, based on delivery time (and not the mail timestamp): * deleted mails are purged after 1 day * read mails without an important flag are purge after 7 days * unread mails without an important flag are purge after 30 days If you use the ''incoming_spam'' [[#Global_Rules|global rule]], then SPAMs newly discovered by the system are flagged as important, which means these mails will never by purged until you review it and decide to delete them or mark them as not important. Custom rules might play with this flag and achieve an automatic selection. === Retraining for feature-limited IMAP Sync clients === If your client does not support the MOVE operation (isync, [https://github.com/OfflineIMAP/offlineimap/issues/515 offlineimap]…) then you can only copy (APPEND) mail, which does not work with the magic Junk folder. In this case, you can create special folders called ''SyncSPAM'' and ''SyncHAM'' and copy SPAM and HAM in them. Every two hours a script will pickup these mails, do the retraining, and remove them. Removing these mails from their original locations will be left to you though. == Mail Filtering == With your favourite mail client, you can probably filter your mails in proper folders already. Nevertheless, this can be an annoying operation: * blocking you mail client for a long time if you have to process plenty of mails * downloading each mail information, and sometimes content (depending on your filters), is lenghty too, and cost much bandwidth * syncing filters across your machines (home desktop, laptop, office machine…) is a pain in the ass * processing only when you're online prevents triggering actions in a timely manner (automatic redirect, vacation messages…), and running a machine 24/7 with a mail client polling new mails every 30s is not a solution We provide a much better way to do this using the [[wikipedia:Sieve_(mail_filtering_language)|SIEVE]] filters. Shortly, SIEVE is a language dedicated to expressing mail filters (also called ''rules''). Our server is able to process your mails according to these filters as soon as they arrive. You then don't have to care about them anymore, and may use light mail clients or webmails when you're not on your machine with your favourite software. === Rules Configuration === You can express sort/reject/vacation/… filters using these rules, as the capabilities are very rich. Several softwares support managing SIEVE rules: * Icedove/Thunderbird: *: using the SIEVE extension (in ''xul-ext-sieve'' Debian package), it provides a rules editor (for power-users) * Roundcube: *: coupled with the sieverules extension, provides an easy to use web interface *: this webmail has been made available [https://webmail.duckcorp.org/ here] * sieve-connect: *: provides a CLI to upload/download/activate your rules files *: this tool is available on [[Services/Shell|shell hosts]] (tell us if you know more software supporting this feature) To push your filters on the server, a dedicated protocol exists: MANAGESIEVE (TCP 4190) on ''sieve.duckcorp.org''. Our webmails are already configured to use it, but it you use sieve-connect from our hosts or your own mail software, you'll need these parameters. You can read more info about SIEVE here: * supported SIEVE features on our server: http://pigeonhole.dovecot.org/ * http://www.fastmail.fm/docs/sieve/ * http://sieve.info/ === Global Rules === Global rules are provided to ease configuration on specific filters. They can easily be included in your own configuration. Available rules: * ''incoming_spam'': *: SPAMs will automatically be delivered in the ''Junk'' folder and marked as ''important'' If you write your own custom rules, here is an example on how to use one of them: require ["include"]; include :global "&lt;rule-name&gt;"; === Default Rules === The default settings (since 2112-02-11) are to use the global ''incoming_spam'' rule (see below), in order to provide a simple default configuration for most users. All other mails will end-up in your ''Inbox'' folder and you may then sort them by yourself. If you create your own rules, the default rules won't apply anymore, so power-users can replace the default behavior completely to achieve what they really need. If you want to use the default behavior you can use: require ["include"]; include :global "incoming_spam"; You can also take advantage of the antispam spaminess score to use a different threshold like this: require ["fileinto", "spamtestplus", "relational", "comparator-i;ascii-numeric"]; # if SPAM score is >37% then move into the junk box if spamtest :percent :value "gt" :comparator "i;ascii-numeric" "37" { fileinto "Junk"; stop; } == Fetching eMails from an External Mailbox == {{todo}} == Shared/Public Folders == You may need to share mails or messages with friends or people you do stuff with (in a project or association). Depending on your needs, two solutions are possible: * share some of your own private folders, thus called ''shared folders'' * manage a special folder hierarchy, called ''public folders'' (even if they may not be accessible to everyone) *: if you need one, ask an administrator; the namespace name can be freely chosen but must be unambiguous and is subject to approval === Namespaces === Through IMAP, or our webmails internally using IMAP, it is possible to partition the folder hierarchy into ''namespaces''. Traditionally you are using the root namespace for your private folders. Additional namespaces can be created and will appear among your own folders or separate, depending on your mail client's choice of representation. To avoid name clashes, we decided to prefix all additional namespace names with a '''#'''. Since 2011-05-14, the following extra namespaces are created and reserved: * #Shared, containing all folders other users decided to share with you * #MilkyPond, containing public MP/DC informational mailboxes you may subscribe at will === Folders Permissions === Using IMAP, it is possible to setup rights (read only, write allowed…) to your own folders in order to share them with other users, or group of users. Public folders are owned by no-one, and must be created by the administrators. Once your request is accepted we will delegate its administration to your care. It can then can be managed like shared folders. === Software Support === Client mail softwares support: * RoundCube: *: support namespaces, shared and public folders configurable via ''Settings->Folders'', selecting a folder then using the ''Sharing'' tab * Icedove/Thunderbird: *: support namespaces, shared and public folders configurable via folder selection and ''Tools->Imap-ACL'' menu action Most other softwares have namespace support only, so you should be able to use shared/public folders you have rights on but not configure them yourself (tell us if you know more software supporting this feature). == Limitations == === Maximum Mail Size === Mail you send or receive are limited to '''20MB'''. If you need to transmit much bigger data, then a mail transport is not appropriate, you'd better use a file sharing method instead. === Quotas === Even if it would be nice to live without it, we had to establish quotas to force people sort their mails out once in a while and delete useless things instead of leaving an ever-growing mess behind. The default quota is '''512MB''' which is not that big but should match needs of most users. This said, you may ask us for more and there's no reason we would refuse a reasonable demand. == Technical Details == This service is made using: * [https://www.postfix.org/ Postfix] * [https://dovecot.org/ Dovecot] * [https://projects.duckcorp.org/projects/spoolinger Spoolinger] * [https://rspamd.com/ Rspamd] * [https://www.roundcube.net/ RoundCube] 4da834c00fedf2b55671eac2935d6284f7a8e417 791 775 2019-05-03T05:46:07Z Duck 2 /* Using a Web Interface */ wikitext text/x-wiki {{Template:Service | description = Available services: * multiple email addresses (mailboxes+aliases or redirections) based on the ''milkypond.org'' (or maybe ''duckcorp.org'') domain * roaming accounts to be able to send emails wherever you are If you want email addresses using you own domain(s), see the [[Services/MailHosting|mail hosting service]]. | prerequisite = | account = global-reg | ipv6 = true | security_notes = Access to the mail services are fully secured, and to your data, nevertheless most mail exchange on the Internet are not. Complete security can be achieved using signed and encrypted mail (see [[wikipedia:Pretty_Good_Privacy|OpenPGP]] and [[wikipedia:S/MIME|S/MIME]]) }} == Access == === Using a Mail Reader === You can retrieve your mails, in case of a real mailbox, using either: * IMAP+TLS (TCP 143) / IMAPS (TCP 993) on imap.duckcorp.org * or POP3+TLS (TCP 110) / POP3S (TCP 995) on pop.duckcorp.org The IMAP protocol is recommended over POP3, as it provides many interesting features. If you want to download all your mails absolutely at home, loosing the ability to read your mail from anywhere on the planet, you can do that with IMAP too (look at your mail client settings). You can use our servers to send mails out too via smtp.duckcorp.org using: * SUBMISSION (TCP 587) which is the recommended way and has less chance to be filtered, or alternatively SMTP+TLS (TCP 25) / SMTPS (TCP 465) * and SASL authentication === Using a Web Interface === A [https://webmail.duckcorp.org/ webmail interface] is available. We strongly suggest you enable [https://en.wikipedia.org/wiki/Multi-factor_authentication Two Factor Authentication (2FA)] to protect your account. With this system your login and password is not sufficient to log in, an external secret is needed. Currently only one method is available: * TOTP: using an application on your phone (FreeOTP available on [http://f-droid.org/ F-Droid] is working fine) In the ''settings'' menu click on the ''2-Factor Authentication'' tab and follow these steps: * click on the ''Setup all fields (needs Save)'' button * on your phone, open the TOPT application and scan the QR code * on your phone generate a code, put it in the ''Check code'' text field and click on the button to validate it works fine * click on the ''show recovery codes'' button and store them is a safe place: print then (or store then on an encrypted disk) * click the ''Save'' button, you will be logged out * check you can login again == Antivirus and Antispam == Mails stored on our server are checked upon arrival for viruses and SPAMs. Outgoing mails from our services are checked too. Mails being viruses are suppressed automatically upon arrival. Mails with a huge probability of being SPAM are destroyed too. Good mails and possibly spammy mails are delivered to your mailbox. SPAMs are more difficult to detect, and it is an error-prone process, so we chose to use a learning software instead of using a global database. After a few weeks of teaching it is able to recognize most of your habits and block a lot of annoying SPAM. === Probable SPAM Notification === Mails are delivered normally with a special field added (''X-Spam-Status'') to your mail headers (not always visible depending on your mail client and its configuration) indicating if the mail is a SPAM and its ''spamminess'' score. This is quite handy if you prefer SPAMs arranged in a specific folder. You may use then the provided [[#Mail Filtering |filtering system]] to sort them properly, or configure your eMail client. === Retraining === Teaching the system what is SPAM and HAM (non-SPAM) is called ''retraining''. If you have of create a folder named ''Junk'', then it is automatically magic: * if you move mail into it, it is automatically retrained as SPAM * if you move mail out of it, it is automatically retrained as HAM * with time, certain old mails automatically expire, see below If you are using an IMAP Sync client which does not support the MOVE operation (isync, offlineimap…) then you unfortunately cannot use this method, please look at the next chapter. To use this folder properly, SPAMs '''must''' be delivered in the ''Junk'' folder automatically, so you can move them out in case of error. You just need to subscribe to this folder in your mail software (this folder is always auto-created). It is not recommended to use your mail software for this filtering, this is horribly inefficient and you would have to set things up on each device and manually synchronize your settings. Automatic expiration logic, based on delivery time (and not the mail timestamp): * deleted mails are purged after 1 day * read mails without an important flag are purge after 7 days * unread mails without an important flag are purge after 30 days If you use the ''incoming_spam'' [[#Global_Rules|global rule]], then SPAMs newly discovered by the system are flagged as important, which means these mails will never by purged until you review it and decide to delete them or mark them as not important. Custom rules might play with this flag and achieve an automatic selection. === Retraining for feature-limited IMAP Sync clients === If your client does not support the MOVE operation (isync, [https://github.com/OfflineIMAP/offlineimap/issues/515 offlineimap]…) then you can only copy (APPEND) mail, which does not work with the magic Junk folder. In this case, you can create special folders called ''SyncSPAM'' and ''SyncHAM'' and copy SPAM and HAM in them. Every two hours a script will pickup these mails, do the retraining, and remove them. Removing these mails from their original locations will be left to you though. == Mail Filtering == With your favourite mail client, you can probably filter your mails in proper folders already. Nevertheless, this can be an annoying operation: * blocking you mail client for a long time if you have to process plenty of mails * downloading each mail information, and sometimes content (depending on your filters), is lenghty too, and cost much bandwidth * syncing filters across your machines (home desktop, laptop, office machine…) is a pain in the ass * processing only when you're online prevents triggering actions in a timely manner (automatic redirect, vacation messages…), and running a machine 24/7 with a mail client polling new mails every 30s is not a solution We provide a much better way to do this using the [[wikipedia:Sieve_(mail_filtering_language)|SIEVE]] filters. Shortly, SIEVE is a language dedicated to expressing mail filters (also called ''rules''). Our server is able to process your mails according to these filters as soon as they arrive. You then don't have to care about them anymore, and may use light mail clients or webmails when you're not on your machine with your favourite software. === Rules Configuration === You can express sort/reject/vacation/… filters using these rules, as the capabilities are very rich. Several softwares support managing SIEVE rules: * Icedove/Thunderbird: *: using the SIEVE extension (in ''xul-ext-sieve'' Debian package), it provides a rules editor (for power-users) * Roundcube: *: coupled with the sieverules extension, provides an easy to use web interface *: this webmail has been made available [https://webmail.duckcorp.org/ here] * sieve-connect: *: provides a CLI to upload/download/activate your rules files *: this tool is available on [[Services/Shell|shell hosts]] (tell us if you know more software supporting this feature) To push your filters on the server, a dedicated protocol exists: MANAGESIEVE (TCP 4190) on ''sieve.duckcorp.org''. Our webmails are already configured to use it, but it you use sieve-connect from our hosts or your own mail software, you'll need these parameters. You can read more info about SIEVE here: * supported SIEVE features on our server: http://pigeonhole.dovecot.org/ * http://www.fastmail.fm/docs/sieve/ * http://sieve.info/ === Global Rules === Global rules are provided to ease configuration on specific filters. They can easily be included in your own configuration. Available rules: * ''incoming_spam'': *: SPAMs will automatically be delivered in the ''Junk'' folder and marked as ''important'' If you write your own custom rules, here is an example on how to use one of them: require ["include"]; include :global "&lt;rule-name&gt;"; === Default Rules === The default settings (since 2112-02-11) are to use the global ''incoming_spam'' rule (see below), in order to provide a simple default configuration for most users. All other mails will end-up in your ''Inbox'' folder and you may then sort them by yourself. If you create your own rules, the default rules won't apply anymore, so power-users can replace the default behavior completely to achieve what they really need. If you want to use the default behavior you can use: require ["include"]; include :global "incoming_spam"; You can also take advantage of the antispam spaminess score to use a different threshold like this: require ["fileinto", "spamtestplus", "relational", "comparator-i;ascii-numeric"]; # if SPAM score is >37% then move into the junk box if spamtest :percent :value "gt" :comparator "i;ascii-numeric" "37" { fileinto "Junk"; stop; } == Fetching eMails from an External Mailbox == {{todo}} == Shared/Public Folders == You may need to share mails or messages with friends or people you do stuff with (in a project or association). Depending on your needs, two solutions are possible: * share some of your own private folders, thus called ''shared folders'' * manage a special folder hierarchy, called ''public folders'' (even if they may not be accessible to everyone) *: if you need one, ask an administrator; the namespace name can be freely chosen but must be unambiguous and is subject to approval === Namespaces === Through IMAP, or our webmails internally using IMAP, it is possible to partition the folder hierarchy into ''namespaces''. Traditionally you are using the root namespace for your private folders. Additional namespaces can be created and will appear among your own folders or separate, depending on your mail client's choice of representation. To avoid name clashes, we decided to prefix all additional namespace names with a '''#'''. Since 2011-05-14, the following extra namespaces are created and reserved: * #Shared, containing all folders other users decided to share with you * #MilkyPond, containing public MP/DC informational mailboxes you may subscribe at will === Folders Permissions === Using IMAP, it is possible to setup rights (read only, write allowed…) to your own folders in order to share them with other users, or group of users. Public folders are owned by no-one, and must be created by the administrators. Once your request is accepted we will delegate its administration to your care. It can then can be managed like shared folders. === Software Support === Client mail softwares support: * RoundCube: *: support namespaces, shared and public folders configurable via ''Settings->Folders'', selecting a folder then using the ''Sharing'' tab * Icedove/Thunderbird: *: support namespaces, shared and public folders configurable via folder selection and ''Tools->Imap-ACL'' menu action Most other softwares have namespace support only, so you should be able to use shared/public folders you have rights on but not configure them yourself (tell us if you know more software supporting this feature). == Limitations == === Maximum Mail Size === Mail you send or receive are limited to '''20MB'''. If you need to transmit much bigger data, then a mail transport is not appropriate, you'd better use a file sharing method instead. === Quotas === Even if it would be nice to live without it, we had to establish quotas to force people sort their mails out once in a while and delete useless things instead of leaving an ever-growing mess behind. The default quota is '''512MB''' which is not that big but should match needs of most users. This said, you may ask us for more and there's no reason we would refuse a reasonable demand. == Technical Details == This service is made using: * [https://www.postfix.org/ Postfix] * [https://dovecot.org/ Dovecot] * [https://projects.duckcorp.org/projects/spoolinger Spoolinger] * [https://rspamd.com/ Rspamd] * [https://www.roundcube.net/ RoundCube] 4532279f4641cb009f57c891be4cb358ec3f8fdb 796 791 2019-09-30T03:15:20Z Duck 2 /* Fetching eMails from an External Mailbox */ wikitext text/x-wiki {{Template:Service | description = Available services: * multiple email addresses (mailboxes+aliases or redirections) based on the ''milkypond.org'' (or maybe ''duckcorp.org'') domain * roaming accounts to be able to send emails wherever you are If you want email addresses using you own domain(s), see the [[Services/MailHosting|mail hosting service]]. | prerequisite = | account = global-reg | ipv6 = true | security_notes = Access to the mail services are fully secured, and to your data, nevertheless most mail exchange on the Internet are not. Complete security can be achieved using signed and encrypted mail (see [[wikipedia:Pretty_Good_Privacy|OpenPGP]] and [[wikipedia:S/MIME|S/MIME]]) }} == Access == === Using a Mail Reader === You can retrieve your mails, in case of a real mailbox, using either: * IMAP+TLS (TCP 143) / IMAPS (TCP 993) on imap.duckcorp.org * or POP3+TLS (TCP 110) / POP3S (TCP 995) on pop.duckcorp.org The IMAP protocol is recommended over POP3, as it provides many interesting features. If you want to download all your mails absolutely at home, loosing the ability to read your mail from anywhere on the planet, you can do that with IMAP too (look at your mail client settings). You can use our servers to send mails out too via smtp.duckcorp.org using: * SUBMISSION (TCP 587) which is the recommended way and has less chance to be filtered, or alternatively SMTP+TLS (TCP 25) / SMTPS (TCP 465) * and SASL authentication === Using a Web Interface === A [https://webmail.duckcorp.org/ webmail interface] is available. We strongly suggest you enable [https://en.wikipedia.org/wiki/Multi-factor_authentication Two Factor Authentication (2FA)] to protect your account. With this system your login and password is not sufficient to log in, an external secret is needed. Currently only one method is available: * TOTP: using an application on your phone (FreeOTP available on [http://f-droid.org/ F-Droid] is working fine) In the ''settings'' menu click on the ''2-Factor Authentication'' tab and follow these steps: * click on the ''Setup all fields (needs Save)'' button * on your phone, open the TOPT application and scan the QR code * on your phone generate a code, put it in the ''Check code'' text field and click on the button to validate it works fine * click on the ''show recovery codes'' button and store them is a safe place: print then (or store then on an encrypted disk) * click the ''Save'' button, you will be logged out * check you can login again == Antivirus and Antispam == Mails stored on our server are checked upon arrival for viruses and SPAMs. Outgoing mails from our services are checked too. Mails being viruses are suppressed automatically upon arrival. Mails with a huge probability of being SPAM are destroyed too. Good mails and possibly spammy mails are delivered to your mailbox. SPAMs are more difficult to detect, and it is an error-prone process, so we chose to use a learning software instead of using a global database. After a few weeks of teaching it is able to recognize most of your habits and block a lot of annoying SPAM. === Probable SPAM Notification === Mails are delivered normally with a special field added (''X-Spam-Status'') to your mail headers (not always visible depending on your mail client and its configuration) indicating if the mail is a SPAM and its ''spamminess'' score. This is quite handy if you prefer SPAMs arranged in a specific folder. You may use then the provided [[#Mail Filtering |filtering system]] to sort them properly, or configure your eMail client. === Retraining === Teaching the system what is SPAM and HAM (non-SPAM) is called ''retraining''. If you have of create a folder named ''Junk'', then it is automatically magic: * if you move mail into it, it is automatically retrained as SPAM * if you move mail out of it, it is automatically retrained as HAM * with time, certain old mails automatically expire, see below If you are using an IMAP Sync client which does not support the MOVE operation (isync, offlineimap…) then you unfortunately cannot use this method, please look at the next chapter. To use this folder properly, SPAMs '''must''' be delivered in the ''Junk'' folder automatically, so you can move them out in case of error. You just need to subscribe to this folder in your mail software (this folder is always auto-created). It is not recommended to use your mail software for this filtering, this is horribly inefficient and you would have to set things up on each device and manually synchronize your settings. Automatic expiration logic, based on delivery time (and not the mail timestamp): * deleted mails are purged after 1 day * read mails without an important flag are purge after 7 days * unread mails without an important flag are purge after 30 days If you use the ''incoming_spam'' [[#Global_Rules|global rule]], then SPAMs newly discovered by the system are flagged as important, which means these mails will never by purged until you review it and decide to delete them or mark them as not important. Custom rules might play with this flag and achieve an automatic selection. === Retraining for feature-limited IMAP Sync clients === If your client does not support the MOVE operation (isync, [https://github.com/OfflineIMAP/offlineimap/issues/515 offlineimap]…) then you can only copy (APPEND) mail, which does not work with the magic Junk folder. In this case, you can create special folders called ''SyncSPAM'' and ''SyncHAM'' and copy SPAM and HAM in them. Every two hours a script will pickup these mails, do the retraining, and remove them. Removing these mails from their original locations will be left to you though. == Mail Filtering == With your favourite mail client, you can probably filter your mails in proper folders already. Nevertheless, this can be an annoying operation: * blocking you mail client for a long time if you have to process plenty of mails * downloading each mail information, and sometimes content (depending on your filters), is lenghty too, and cost much bandwidth * syncing filters across your machines (home desktop, laptop, office machine…) is a pain in the ass * processing only when you're online prevents triggering actions in a timely manner (automatic redirect, vacation messages…), and running a machine 24/7 with a mail client polling new mails every 30s is not a solution We provide a much better way to do this using the [[wikipedia:Sieve_(mail_filtering_language)|SIEVE]] filters. Shortly, SIEVE is a language dedicated to expressing mail filters (also called ''rules''). Our server is able to process your mails according to these filters as soon as they arrive. You then don't have to care about them anymore, and may use light mail clients or webmails when you're not on your machine with your favourite software. === Rules Configuration === You can express sort/reject/vacation/… filters using these rules, as the capabilities are very rich. Several softwares support managing SIEVE rules: * Icedove/Thunderbird: *: using the SIEVE extension (in ''xul-ext-sieve'' Debian package), it provides a rules editor (for power-users) * Roundcube: *: coupled with the sieverules extension, provides an easy to use web interface *: this webmail has been made available [https://webmail.duckcorp.org/ here] * sieve-connect: *: provides a CLI to upload/download/activate your rules files *: this tool is available on [[Services/Shell|shell hosts]] (tell us if you know more software supporting this feature) To push your filters on the server, a dedicated protocol exists: MANAGESIEVE (TCP 4190) on ''sieve.duckcorp.org''. Our webmails are already configured to use it, but it you use sieve-connect from our hosts or your own mail software, you'll need these parameters. You can read more info about SIEVE here: * supported SIEVE features on our server: http://pigeonhole.dovecot.org/ * http://www.fastmail.fm/docs/sieve/ * http://sieve.info/ === Global Rules === Global rules are provided to ease configuration on specific filters. They can easily be included in your own configuration. Available rules: * ''incoming_spam'': *: SPAMs will automatically be delivered in the ''Junk'' folder and marked as ''important'' If you write your own custom rules, here is an example on how to use one of them: require ["include"]; include :global "&lt;rule-name&gt;"; === Default Rules === The default settings (since 2112-02-11) are to use the global ''incoming_spam'' rule (see below), in order to provide a simple default configuration for most users. All other mails will end-up in your ''Inbox'' folder and you may then sort them by yourself. If you create your own rules, the default rules won't apply anymore, so power-users can replace the default behavior completely to achieve what they really need. If you want to use the default behavior you can use: require ["include"]; include :global "incoming_spam"; You can also take advantage of the antispam spaminess score to use a different threshold like this: require ["fileinto", "spamtestplus", "relational", "comparator-i;ascii-numeric"]; # if SPAM score is >37% then move into the junk box if spamtest :percent :value "gt" :comparator "i;ascii-numeric" "37" { fileinto "Junk"; stop; } == Fetching eMails from an External Mailbox == {{warning}} This is not supported anymore; you may still redirect mails from your external mailbox to your DuckCorp's email address though. == Shared/Public Folders == You may need to share mails or messages with friends or people you do stuff with (in a project or association). Depending on your needs, two solutions are possible: * share some of your own private folders, thus called ''shared folders'' * manage a special folder hierarchy, called ''public folders'' (even if they may not be accessible to everyone) *: if you need one, ask an administrator; the namespace name can be freely chosen but must be unambiguous and is subject to approval === Namespaces === Through IMAP, or our webmails internally using IMAP, it is possible to partition the folder hierarchy into ''namespaces''. Traditionally you are using the root namespace for your private folders. Additional namespaces can be created and will appear among your own folders or separate, depending on your mail client's choice of representation. To avoid name clashes, we decided to prefix all additional namespace names with a '''#'''. Since 2011-05-14, the following extra namespaces are created and reserved: * #Shared, containing all folders other users decided to share with you * #MilkyPond, containing public MP/DC informational mailboxes you may subscribe at will === Folders Permissions === Using IMAP, it is possible to setup rights (read only, write allowed…) to your own folders in order to share them with other users, or group of users. Public folders are owned by no-one, and must be created by the administrators. Once your request is accepted we will delegate its administration to your care. It can then can be managed like shared folders. === Software Support === Client mail softwares support: * RoundCube: *: support namespaces, shared and public folders configurable via ''Settings->Folders'', selecting a folder then using the ''Sharing'' tab * Icedove/Thunderbird: *: support namespaces, shared and public folders configurable via folder selection and ''Tools->Imap-ACL'' menu action Most other softwares have namespace support only, so you should be able to use shared/public folders you have rights on but not configure them yourself (tell us if you know more software supporting this feature). == Limitations == === Maximum Mail Size === Mail you send or receive are limited to '''20MB'''. If you need to transmit much bigger data, then a mail transport is not appropriate, you'd better use a file sharing method instead. === Quotas === Even if it would be nice to live without it, we had to establish quotas to force people sort their mails out once in a while and delete useless things instead of leaving an ever-growing mess behind. The default quota is '''512MB''' which is not that big but should match needs of most users. This said, you may ask us for more and there's no reason we would refuse a reasonable demand. == Technical Details == This service is made using: * [https://www.postfix.org/ Postfix] * [https://dovecot.org/ Dovecot] * [https://projects.duckcorp.org/projects/spoolinger Spoolinger] * [https://rspamd.com/ Rspamd] * [https://www.roundcube.net/ RoundCube] a4406933e4b4a1aabfd7f6b559dc1e535819a59d 797 796 2019-09-30T03:21:32Z Duck 2 /* Shared/Public Folders */ wikitext text/x-wiki {{Template:Service | description = Available services: * multiple email addresses (mailboxes+aliases or redirections) based on the ''milkypond.org'' (or maybe ''duckcorp.org'') domain * roaming accounts to be able to send emails wherever you are If you want email addresses using you own domain(s), see the [[Services/MailHosting|mail hosting service]]. | prerequisite = | account = global-reg | ipv6 = true | security_notes = Access to the mail services are fully secured, and to your data, nevertheless most mail exchange on the Internet are not. Complete security can be achieved using signed and encrypted mail (see [[wikipedia:Pretty_Good_Privacy|OpenPGP]] and [[wikipedia:S/MIME|S/MIME]]) }} == Access == === Using a Mail Reader === You can retrieve your mails, in case of a real mailbox, using either: * IMAP+TLS (TCP 143) / IMAPS (TCP 993) on imap.duckcorp.org * or POP3+TLS (TCP 110) / POP3S (TCP 995) on pop.duckcorp.org The IMAP protocol is recommended over POP3, as it provides many interesting features. If you want to download all your mails absolutely at home, loosing the ability to read your mail from anywhere on the planet, you can do that with IMAP too (look at your mail client settings). You can use our servers to send mails out too via smtp.duckcorp.org using: * SUBMISSION (TCP 587) which is the recommended way and has less chance to be filtered, or alternatively SMTP+TLS (TCP 25) / SMTPS (TCP 465) * and SASL authentication === Using a Web Interface === A [https://webmail.duckcorp.org/ webmail interface] is available. We strongly suggest you enable [https://en.wikipedia.org/wiki/Multi-factor_authentication Two Factor Authentication (2FA)] to protect your account. With this system your login and password is not sufficient to log in, an external secret is needed. Currently only one method is available: * TOTP: using an application on your phone (FreeOTP available on [http://f-droid.org/ F-Droid] is working fine) In the ''settings'' menu click on the ''2-Factor Authentication'' tab and follow these steps: * click on the ''Setup all fields (needs Save)'' button * on your phone, open the TOPT application and scan the QR code * on your phone generate a code, put it in the ''Check code'' text field and click on the button to validate it works fine * click on the ''show recovery codes'' button and store them is a safe place: print then (or store then on an encrypted disk) * click the ''Save'' button, you will be logged out * check you can login again == Antivirus and Antispam == Mails stored on our server are checked upon arrival for viruses and SPAMs. Outgoing mails from our services are checked too. Mails being viruses are suppressed automatically upon arrival. Mails with a huge probability of being SPAM are destroyed too. Good mails and possibly spammy mails are delivered to your mailbox. SPAMs are more difficult to detect, and it is an error-prone process, so we chose to use a learning software instead of using a global database. After a few weeks of teaching it is able to recognize most of your habits and block a lot of annoying SPAM. === Probable SPAM Notification === Mails are delivered normally with a special field added (''X-Spam-Status'') to your mail headers (not always visible depending on your mail client and its configuration) indicating if the mail is a SPAM and its ''spamminess'' score. This is quite handy if you prefer SPAMs arranged in a specific folder. You may use then the provided [[#Mail Filtering |filtering system]] to sort them properly, or configure your eMail client. === Retraining === Teaching the system what is SPAM and HAM (non-SPAM) is called ''retraining''. If you have of create a folder named ''Junk'', then it is automatically magic: * if you move mail into it, it is automatically retrained as SPAM * if you move mail out of it, it is automatically retrained as HAM * with time, certain old mails automatically expire, see below If you are using an IMAP Sync client which does not support the MOVE operation (isync, offlineimap…) then you unfortunately cannot use this method, please look at the next chapter. To use this folder properly, SPAMs '''must''' be delivered in the ''Junk'' folder automatically, so you can move them out in case of error. You just need to subscribe to this folder in your mail software (this folder is always auto-created). It is not recommended to use your mail software for this filtering, this is horribly inefficient and you would have to set things up on each device and manually synchronize your settings. Automatic expiration logic, based on delivery time (and not the mail timestamp): * deleted mails are purged after 1 day * read mails without an important flag are purge after 7 days * unread mails without an important flag are purge after 30 days If you use the ''incoming_spam'' [[#Global_Rules|global rule]], then SPAMs newly discovered by the system are flagged as important, which means these mails will never by purged until you review it and decide to delete them or mark them as not important. Custom rules might play with this flag and achieve an automatic selection. === Retraining for feature-limited IMAP Sync clients === If your client does not support the MOVE operation (isync, [https://github.com/OfflineIMAP/offlineimap/issues/515 offlineimap]…) then you can only copy (APPEND) mail, which does not work with the magic Junk folder. In this case, you can create special folders called ''SyncSPAM'' and ''SyncHAM'' and copy SPAM and HAM in them. Every two hours a script will pickup these mails, do the retraining, and remove them. Removing these mails from their original locations will be left to you though. == Mail Filtering == With your favourite mail client, you can probably filter your mails in proper folders already. Nevertheless, this can be an annoying operation: * blocking you mail client for a long time if you have to process plenty of mails * downloading each mail information, and sometimes content (depending on your filters), is lenghty too, and cost much bandwidth * syncing filters across your machines (home desktop, laptop, office machine…) is a pain in the ass * processing only when you're online prevents triggering actions in a timely manner (automatic redirect, vacation messages…), and running a machine 24/7 with a mail client polling new mails every 30s is not a solution We provide a much better way to do this using the [[wikipedia:Sieve_(mail_filtering_language)|SIEVE]] filters. Shortly, SIEVE is a language dedicated to expressing mail filters (also called ''rules''). Our server is able to process your mails according to these filters as soon as they arrive. You then don't have to care about them anymore, and may use light mail clients or webmails when you're not on your machine with your favourite software. === Rules Configuration === You can express sort/reject/vacation/… filters using these rules, as the capabilities are very rich. Several softwares support managing SIEVE rules: * Icedove/Thunderbird: *: using the SIEVE extension (in ''xul-ext-sieve'' Debian package), it provides a rules editor (for power-users) * Roundcube: *: coupled with the sieverules extension, provides an easy to use web interface *: this webmail has been made available [https://webmail.duckcorp.org/ here] * sieve-connect: *: provides a CLI to upload/download/activate your rules files *: this tool is available on [[Services/Shell|shell hosts]] (tell us if you know more software supporting this feature) To push your filters on the server, a dedicated protocol exists: MANAGESIEVE (TCP 4190) on ''sieve.duckcorp.org''. Our webmails are already configured to use it, but it you use sieve-connect from our hosts or your own mail software, you'll need these parameters. You can read more info about SIEVE here: * supported SIEVE features on our server: http://pigeonhole.dovecot.org/ * http://www.fastmail.fm/docs/sieve/ * http://sieve.info/ === Global Rules === Global rules are provided to ease configuration on specific filters. They can easily be included in your own configuration. Available rules: * ''incoming_spam'': *: SPAMs will automatically be delivered in the ''Junk'' folder and marked as ''important'' If you write your own custom rules, here is an example on how to use one of them: require ["include"]; include :global "&lt;rule-name&gt;"; === Default Rules === The default settings (since 2112-02-11) are to use the global ''incoming_spam'' rule (see below), in order to provide a simple default configuration for most users. All other mails will end-up in your ''Inbox'' folder and you may then sort them by yourself. If you create your own rules, the default rules won't apply anymore, so power-users can replace the default behavior completely to achieve what they really need. If you want to use the default behavior you can use: require ["include"]; include :global "incoming_spam"; You can also take advantage of the antispam spaminess score to use a different threshold like this: require ["fileinto", "spamtestplus", "relational", "comparator-i;ascii-numeric"]; # if SPAM score is >37% then move into the junk box if spamtest :percent :value "gt" :comparator "i;ascii-numeric" "37" { fileinto "Junk"; stop; } == Fetching eMails from an External Mailbox == {{warning}} This is not supported anymore; you may still redirect mails from your external mailbox to your DuckCorp's email address though. == Shared/Public Folders == {{warning}} This is unfortunately not supported by the synchronization system between our two main mail servers; it was not used anyway. Private (non-shared) namespaces are possible though. You may need to share mails or messages with friends or people you do stuff with (in a project or association). Depending on your needs, two solutions are possible:</del> * share some of your own private folders, thus called ''shared folders'' * manage a special folder hierarchy, called ''public folders'' (even if they may not be accessible to everyone) *: if you need one, ask an administrator; the namespace name can be freely chosen but must be unambiguous and is subject to approval === Namespaces === Through IMAP, or our webmails internally using IMAP, it is possible to partition the folder hierarchy into ''namespaces''. Traditionally you are using the root namespace for your private folders. Additional namespaces can be created and will appear among your own folders or separate, depending on your mail client's choice of representation. To avoid name clashes, we decided to prefix all additional namespace names with a '''#'''. Since 2011-05-14, the following extra namespaces are created and reserved: * #Shared, containing all folders other users decided to share with you * #MilkyPond, containing public MP/DC informational mailboxes you may subscribe at will === Folders Permissions === Using IMAP, it is possible to setup rights (read only, write allowed…) to your own folders in order to share them with other users, or group of users. Public folders are owned by no-one, and must be created by the administrators. Once your request is accepted we will delegate its administration to your care. It can then can be managed like shared folders. === Software Support === Client mail softwares support: * RoundCube: *: support namespaces, shared and public folders configurable via ''Settings->Folders'', selecting a folder then using the ''Sharing'' tab * Icedove/Thunderbird: *: support namespaces, shared and public folders configurable via folder selection and ''Tools->Imap-ACL'' menu action Most other softwares have namespace support only, so you should be able to use shared/public folders you have rights on but not configure them yourself (tell us if you know more software supporting this feature). == Limitations == === Maximum Mail Size === Mail you send or receive are limited to '''20MB'''. If you need to transmit much bigger data, then a mail transport is not appropriate, you'd better use a file sharing method instead. === Quotas === Even if it would be nice to live without it, we had to establish quotas to force people sort their mails out once in a while and delete useless things instead of leaving an ever-growing mess behind. The default quota is '''512MB''' which is not that big but should match needs of most users. This said, you may ask us for more and there's no reason we would refuse a reasonable demand. == Technical Details == This service is made using: * [https://www.postfix.org/ Postfix] * [https://dovecot.org/ Dovecot] * [https://projects.duckcorp.org/projects/spoolinger Spoolinger] * [https://rspamd.com/ Rspamd] * [https://www.roundcube.net/ RoundCube] 591d9e54d7f7be5c6404cb455daf52595751b41f 798 797 2019-09-30T03:25:24Z Duck 2 /* Technical Details */ wikitext text/x-wiki {{Template:Service | description = Available services: * multiple email addresses (mailboxes+aliases or redirections) based on the ''milkypond.org'' (or maybe ''duckcorp.org'') domain * roaming accounts to be able to send emails wherever you are If you want email addresses using you own domain(s), see the [[Services/MailHosting|mail hosting service]]. | prerequisite = | account = global-reg | ipv6 = true | security_notes = Access to the mail services are fully secured, and to your data, nevertheless most mail exchange on the Internet are not. Complete security can be achieved using signed and encrypted mail (see [[wikipedia:Pretty_Good_Privacy|OpenPGP]] and [[wikipedia:S/MIME|S/MIME]]) }} == Access == === Using a Mail Reader === You can retrieve your mails, in case of a real mailbox, using either: * IMAP+TLS (TCP 143) / IMAPS (TCP 993) on imap.duckcorp.org * or POP3+TLS (TCP 110) / POP3S (TCP 995) on pop.duckcorp.org The IMAP protocol is recommended over POP3, as it provides many interesting features. If you want to download all your mails absolutely at home, loosing the ability to read your mail from anywhere on the planet, you can do that with IMAP too (look at your mail client settings). You can use our servers to send mails out too via smtp.duckcorp.org using: * SUBMISSION (TCP 587) which is the recommended way and has less chance to be filtered, or alternatively SMTP+TLS (TCP 25) / SMTPS (TCP 465) * and SASL authentication === Using a Web Interface === A [https://webmail.duckcorp.org/ webmail interface] is available. We strongly suggest you enable [https://en.wikipedia.org/wiki/Multi-factor_authentication Two Factor Authentication (2FA)] to protect your account. With this system your login and password is not sufficient to log in, an external secret is needed. Currently only one method is available: * TOTP: using an application on your phone (FreeOTP available on [http://f-droid.org/ F-Droid] is working fine) In the ''settings'' menu click on the ''2-Factor Authentication'' tab and follow these steps: * click on the ''Setup all fields (needs Save)'' button * on your phone, open the TOPT application and scan the QR code * on your phone generate a code, put it in the ''Check code'' text field and click on the button to validate it works fine * click on the ''show recovery codes'' button and store them is a safe place: print then (or store then on an encrypted disk) * click the ''Save'' button, you will be logged out * check you can login again == Antivirus and Antispam == Mails stored on our server are checked upon arrival for viruses and SPAMs. Outgoing mails from our services are checked too. Mails being viruses are suppressed automatically upon arrival. Mails with a huge probability of being SPAM are destroyed too. Good mails and possibly spammy mails are delivered to your mailbox. SPAMs are more difficult to detect, and it is an error-prone process, so we chose to use a learning software instead of using a global database. After a few weeks of teaching it is able to recognize most of your habits and block a lot of annoying SPAM. === Probable SPAM Notification === Mails are delivered normally with a special field added (''X-Spam-Status'') to your mail headers (not always visible depending on your mail client and its configuration) indicating if the mail is a SPAM and its ''spamminess'' score. This is quite handy if you prefer SPAMs arranged in a specific folder. You may use then the provided [[#Mail Filtering |filtering system]] to sort them properly, or configure your eMail client. === Retraining === Teaching the system what is SPAM and HAM (non-SPAM) is called ''retraining''. If you have of create a folder named ''Junk'', then it is automatically magic: * if you move mail into it, it is automatically retrained as SPAM * if you move mail out of it, it is automatically retrained as HAM * with time, certain old mails automatically expire, see below If you are using an IMAP Sync client which does not support the MOVE operation (isync, offlineimap…) then you unfortunately cannot use this method, please look at the next chapter. To use this folder properly, SPAMs '''must''' be delivered in the ''Junk'' folder automatically, so you can move them out in case of error. You just need to subscribe to this folder in your mail software (this folder is always auto-created). It is not recommended to use your mail software for this filtering, this is horribly inefficient and you would have to set things up on each device and manually synchronize your settings. Automatic expiration logic, based on delivery time (and not the mail timestamp): * deleted mails are purged after 1 day * read mails without an important flag are purge after 7 days * unread mails without an important flag are purge after 30 days If you use the ''incoming_spam'' [[#Global_Rules|global rule]], then SPAMs newly discovered by the system are flagged as important, which means these mails will never by purged until you review it and decide to delete them or mark them as not important. Custom rules might play with this flag and achieve an automatic selection. === Retraining for feature-limited IMAP Sync clients === If your client does not support the MOVE operation (isync, [https://github.com/OfflineIMAP/offlineimap/issues/515 offlineimap]…) then you can only copy (APPEND) mail, which does not work with the magic Junk folder. In this case, you can create special folders called ''SyncSPAM'' and ''SyncHAM'' and copy SPAM and HAM in them. Every two hours a script will pickup these mails, do the retraining, and remove them. Removing these mails from their original locations will be left to you though. == Mail Filtering == With your favourite mail client, you can probably filter your mails in proper folders already. Nevertheless, this can be an annoying operation: * blocking you mail client for a long time if you have to process plenty of mails * downloading each mail information, and sometimes content (depending on your filters), is lenghty too, and cost much bandwidth * syncing filters across your machines (home desktop, laptop, office machine…) is a pain in the ass * processing only when you're online prevents triggering actions in a timely manner (automatic redirect, vacation messages…), and running a machine 24/7 with a mail client polling new mails every 30s is not a solution We provide a much better way to do this using the [[wikipedia:Sieve_(mail_filtering_language)|SIEVE]] filters. Shortly, SIEVE is a language dedicated to expressing mail filters (also called ''rules''). Our server is able to process your mails according to these filters as soon as they arrive. You then don't have to care about them anymore, and may use light mail clients or webmails when you're not on your machine with your favourite software. === Rules Configuration === You can express sort/reject/vacation/… filters using these rules, as the capabilities are very rich. Several softwares support managing SIEVE rules: * Icedove/Thunderbird: *: using the SIEVE extension (in ''xul-ext-sieve'' Debian package), it provides a rules editor (for power-users) * Roundcube: *: coupled with the sieverules extension, provides an easy to use web interface *: this webmail has been made available [https://webmail.duckcorp.org/ here] * sieve-connect: *: provides a CLI to upload/download/activate your rules files *: this tool is available on [[Services/Shell|shell hosts]] (tell us if you know more software supporting this feature) To push your filters on the server, a dedicated protocol exists: MANAGESIEVE (TCP 4190) on ''sieve.duckcorp.org''. Our webmails are already configured to use it, but it you use sieve-connect from our hosts or your own mail software, you'll need these parameters. You can read more info about SIEVE here: * supported SIEVE features on our server: http://pigeonhole.dovecot.org/ * http://www.fastmail.fm/docs/sieve/ * http://sieve.info/ === Global Rules === Global rules are provided to ease configuration on specific filters. They can easily be included in your own configuration. Available rules: * ''incoming_spam'': *: SPAMs will automatically be delivered in the ''Junk'' folder and marked as ''important'' If you write your own custom rules, here is an example on how to use one of them: require ["include"]; include :global "&lt;rule-name&gt;"; === Default Rules === The default settings (since 2112-02-11) are to use the global ''incoming_spam'' rule (see below), in order to provide a simple default configuration for most users. All other mails will end-up in your ''Inbox'' folder and you may then sort them by yourself. If you create your own rules, the default rules won't apply anymore, so power-users can replace the default behavior completely to achieve what they really need. If you want to use the default behavior you can use: require ["include"]; include :global "incoming_spam"; You can also take advantage of the antispam spaminess score to use a different threshold like this: require ["fileinto", "spamtestplus", "relational", "comparator-i;ascii-numeric"]; # if SPAM score is >37% then move into the junk box if spamtest :percent :value "gt" :comparator "i;ascii-numeric" "37" { fileinto "Junk"; stop; } == Fetching eMails from an External Mailbox == {{warning}} This is not supported anymore; you may still redirect mails from your external mailbox to your DuckCorp's email address though. == Shared/Public Folders == {{warning}} This is unfortunately not supported by the synchronization system between our two main mail servers; it was not used anyway. Private (non-shared) namespaces are possible though. You may need to share mails or messages with friends or people you do stuff with (in a project or association). Depending on your needs, two solutions are possible:</del> * share some of your own private folders, thus called ''shared folders'' * manage a special folder hierarchy, called ''public folders'' (even if they may not be accessible to everyone) *: if you need one, ask an administrator; the namespace name can be freely chosen but must be unambiguous and is subject to approval === Namespaces === Through IMAP, or our webmails internally using IMAP, it is possible to partition the folder hierarchy into ''namespaces''. Traditionally you are using the root namespace for your private folders. Additional namespaces can be created and will appear among your own folders or separate, depending on your mail client's choice of representation. To avoid name clashes, we decided to prefix all additional namespace names with a '''#'''. Since 2011-05-14, the following extra namespaces are created and reserved: * #Shared, containing all folders other users decided to share with you * #MilkyPond, containing public MP/DC informational mailboxes you may subscribe at will === Folders Permissions === Using IMAP, it is possible to setup rights (read only, write allowed…) to your own folders in order to share them with other users, or group of users. Public folders are owned by no-one, and must be created by the administrators. Once your request is accepted we will delegate its administration to your care. It can then can be managed like shared folders. === Software Support === Client mail softwares support: * RoundCube: *: support namespaces, shared and public folders configurable via ''Settings->Folders'', selecting a folder then using the ''Sharing'' tab * Icedove/Thunderbird: *: support namespaces, shared and public folders configurable via folder selection and ''Tools->Imap-ACL'' menu action Most other softwares have namespace support only, so you should be able to use shared/public folders you have rights on but not configure them yourself (tell us if you know more software supporting this feature). == Limitations == === Maximum Mail Size === Mail you send or receive are limited to '''20MB'''. If you need to transmit much bigger data, then a mail transport is not appropriate, you'd better use a file sharing method instead. === Quotas === Even if it would be nice to live without it, we had to establish quotas to force people sort their mails out once in a while and delete useless things instead of leaving an ever-growing mess behind. The default quota is '''512MB''' which is not that big but should match needs of most users. This said, you may ask us for more and there's no reason we would refuse a reasonable demand. == Technical Details == This service is made using: * [https://www.clamav.net/ ClamAV] * [https://dovecot.org/ Dovecot] * [https://www.postfix.org/ Postfix] * [https://github.com/Snawoot/postfix-mta-sts-resolver postfix-mta-sts-resolver] * [https://www.roundcube.net/ RoundCube] * [https://rspamd.com/ Rspamd] * [https://projects.duckcorp.org/projects/spoolinger Spoolinger] 7288f5d8eee7746d39d21ab1200ffbd27d91f78f 799 798 2019-09-30T03:28:11Z Duck 2 wikitext text/x-wiki {{Template:Service | description = Available services: * multiple email addresses (mailboxes+aliases or redirections) based on the ''milkypond.org'' (or maybe ''duckcorp.org'') domain * roaming accounts to be able to send emails wherever you are If you want email addresses using you own domain(s), see the [[Services/MailHosting|mail hosting service]]. | prerequisite = | account = global-reg | ipv6 = true | security_notes = Access to the mail services are fully secured, and to your data, nevertheless most mail exchange on the Internet are not. MX DNS records are protected with DNSSEC and we publish a MTA-STS policy as well as DANE/TLSA records to use secure connections as much as possible. Complete security can be achieved using signed and encrypted mails (see [[wikipedia:Pretty_Good_Privacy|OpenPGP]] and [[wikipedia:S/MIME|S/MIME]]) }} == Access == === Using a Mail Reader === You can retrieve your mails, in case of a real mailbox, using either: * IMAP+TLS (TCP 143) / IMAPS (TCP 993) on imap.duckcorp.org * or POP3+TLS (TCP 110) / POP3S (TCP 995) on pop.duckcorp.org The IMAP protocol is recommended over POP3, as it provides many interesting features. If you want to download all your mails absolutely at home, loosing the ability to read your mail from anywhere on the planet, you can do that with IMAP too (look at your mail client settings). You can use our servers to send mails out too via smtp.duckcorp.org using: * SUBMISSION (TCP 587) which is the recommended way and has less chance to be filtered, or alternatively SMTP+TLS (TCP 25) / SMTPS (TCP 465) * and SASL authentication === Using a Web Interface === A [https://webmail.duckcorp.org/ webmail interface] is available. We strongly suggest you enable [https://en.wikipedia.org/wiki/Multi-factor_authentication Two Factor Authentication (2FA)] to protect your account. With this system your login and password is not sufficient to log in, an external secret is needed. Currently only one method is available: * TOTP: using an application on your phone (FreeOTP available on [http://f-droid.org/ F-Droid] is working fine) In the ''settings'' menu click on the ''2-Factor Authentication'' tab and follow these steps: * click on the ''Setup all fields (needs Save)'' button * on your phone, open the TOPT application and scan the QR code * on your phone generate a code, put it in the ''Check code'' text field and click on the button to validate it works fine * click on the ''show recovery codes'' button and store them is a safe place: print then (or store then on an encrypted disk) * click the ''Save'' button, you will be logged out * check you can login again == Antivirus and Antispam == Mails stored on our server are checked upon arrival for viruses and SPAMs. Outgoing mails from our services are checked too. Mails being viruses are suppressed automatically upon arrival. Mails with a huge probability of being SPAM are destroyed too. Good mails and possibly spammy mails are delivered to your mailbox. SPAMs are more difficult to detect, and it is an error-prone process, so we chose to use a learning software instead of using a global database. After a few weeks of teaching it is able to recognize most of your habits and block a lot of annoying SPAM. === Probable SPAM Notification === Mails are delivered normally with a special field added (''X-Spam-Status'') to your mail headers (not always visible depending on your mail client and its configuration) indicating if the mail is a SPAM and its ''spamminess'' score. This is quite handy if you prefer SPAMs arranged in a specific folder. You may use then the provided [[#Mail Filtering |filtering system]] to sort them properly, or configure your eMail client. === Retraining === Teaching the system what is SPAM and HAM (non-SPAM) is called ''retraining''. If you have of create a folder named ''Junk'', then it is automatically magic: * if you move mail into it, it is automatically retrained as SPAM * if you move mail out of it, it is automatically retrained as HAM * with time, certain old mails automatically expire, see below If you are using an IMAP Sync client which does not support the MOVE operation (isync, offlineimap…) then you unfortunately cannot use this method, please look at the next chapter. To use this folder properly, SPAMs '''must''' be delivered in the ''Junk'' folder automatically, so you can move them out in case of error. You just need to subscribe to this folder in your mail software (this folder is always auto-created). It is not recommended to use your mail software for this filtering, this is horribly inefficient and you would have to set things up on each device and manually synchronize your settings. Automatic expiration logic, based on delivery time (and not the mail timestamp): * deleted mails are purged after 1 day * read mails without an important flag are purge after 7 days * unread mails without an important flag are purge after 30 days If you use the ''incoming_spam'' [[#Global_Rules|global rule]], then SPAMs newly discovered by the system are flagged as important, which means these mails will never by purged until you review it and decide to delete them or mark them as not important. Custom rules might play with this flag and achieve an automatic selection. === Retraining for feature-limited IMAP Sync clients === If your client does not support the MOVE operation (isync, [https://github.com/OfflineIMAP/offlineimap/issues/515 offlineimap]…) then you can only copy (APPEND) mail, which does not work with the magic Junk folder. In this case, you can create special folders called ''SyncSPAM'' and ''SyncHAM'' and copy SPAM and HAM in them. Every two hours a script will pickup these mails, do the retraining, and remove them. Removing these mails from their original locations will be left to you though. == Mail Filtering == With your favourite mail client, you can probably filter your mails in proper folders already. Nevertheless, this can be an annoying operation: * blocking you mail client for a long time if you have to process plenty of mails * downloading each mail information, and sometimes content (depending on your filters), is lenghty too, and cost much bandwidth * syncing filters across your machines (home desktop, laptop, office machine…) is a pain in the ass * processing only when you're online prevents triggering actions in a timely manner (automatic redirect, vacation messages…), and running a machine 24/7 with a mail client polling new mails every 30s is not a solution We provide a much better way to do this using the [[wikipedia:Sieve_(mail_filtering_language)|SIEVE]] filters. Shortly, SIEVE is a language dedicated to expressing mail filters (also called ''rules''). Our server is able to process your mails according to these filters as soon as they arrive. You then don't have to care about them anymore, and may use light mail clients or webmails when you're not on your machine with your favourite software. === Rules Configuration === You can express sort/reject/vacation/… filters using these rules, as the capabilities are very rich. Several softwares support managing SIEVE rules: * Icedove/Thunderbird: *: using the SIEVE extension (in ''xul-ext-sieve'' Debian package), it provides a rules editor (for power-users) * Roundcube: *: coupled with the sieverules extension, provides an easy to use web interface *: this webmail has been made available [https://webmail.duckcorp.org/ here] * sieve-connect: *: provides a CLI to upload/download/activate your rules files *: this tool is available on [[Services/Shell|shell hosts]] (tell us if you know more software supporting this feature) To push your filters on the server, a dedicated protocol exists: MANAGESIEVE (TCP 4190) on ''sieve.duckcorp.org''. Our webmails are already configured to use it, but it you use sieve-connect from our hosts or your own mail software, you'll need these parameters. You can read more info about SIEVE here: * supported SIEVE features on our server: http://pigeonhole.dovecot.org/ * http://www.fastmail.fm/docs/sieve/ * http://sieve.info/ === Global Rules === Global rules are provided to ease configuration on specific filters. They can easily be included in your own configuration. Available rules: * ''incoming_spam'': *: SPAMs will automatically be delivered in the ''Junk'' folder and marked as ''important'' If you write your own custom rules, here is an example on how to use one of them: require ["include"]; include :global "&lt;rule-name&gt;"; === Default Rules === The default settings (since 2112-02-11) are to use the global ''incoming_spam'' rule (see below), in order to provide a simple default configuration for most users. All other mails will end-up in your ''Inbox'' folder and you may then sort them by yourself. If you create your own rules, the default rules won't apply anymore, so power-users can replace the default behavior completely to achieve what they really need. If you want to use the default behavior you can use: require ["include"]; include :global "incoming_spam"; You can also take advantage of the antispam spaminess score to use a different threshold like this: require ["fileinto", "spamtestplus", "relational", "comparator-i;ascii-numeric"]; # if SPAM score is >37% then move into the junk box if spamtest :percent :value "gt" :comparator "i;ascii-numeric" "37" { fileinto "Junk"; stop; } == Fetching eMails from an External Mailbox == {{warning}} This is not supported anymore; you may still redirect mails from your external mailbox to your DuckCorp's email address though. == Shared/Public Folders == {{warning}} This is unfortunately not supported by the synchronization system between our two main mail servers; it was not used anyway. Private (non-shared) namespaces are possible though. You may need to share mails or messages with friends or people you do stuff with (in a project or association). Depending on your needs, two solutions are possible:</del> * share some of your own private folders, thus called ''shared folders'' * manage a special folder hierarchy, called ''public folders'' (even if they may not be accessible to everyone) *: if you need one, ask an administrator; the namespace name can be freely chosen but must be unambiguous and is subject to approval === Namespaces === Through IMAP, or our webmails internally using IMAP, it is possible to partition the folder hierarchy into ''namespaces''. Traditionally you are using the root namespace for your private folders. Additional namespaces can be created and will appear among your own folders or separate, depending on your mail client's choice of representation. To avoid name clashes, we decided to prefix all additional namespace names with a '''#'''. Since 2011-05-14, the following extra namespaces are created and reserved: * #Shared, containing all folders other users decided to share with you * #MilkyPond, containing public MP/DC informational mailboxes you may subscribe at will === Folders Permissions === Using IMAP, it is possible to setup rights (read only, write allowed…) to your own folders in order to share them with other users, or group of users. Public folders are owned by no-one, and must be created by the administrators. Once your request is accepted we will delegate its administration to your care. It can then can be managed like shared folders. === Software Support === Client mail softwares support: * RoundCube: *: support namespaces, shared and public folders configurable via ''Settings->Folders'', selecting a folder then using the ''Sharing'' tab * Icedove/Thunderbird: *: support namespaces, shared and public folders configurable via folder selection and ''Tools->Imap-ACL'' menu action Most other softwares have namespace support only, so you should be able to use shared/public folders you have rights on but not configure them yourself (tell us if you know more software supporting this feature). == Limitations == === Maximum Mail Size === Mail you send or receive are limited to '''20MB'''. If you need to transmit much bigger data, then a mail transport is not appropriate, you'd better use a file sharing method instead. === Quotas === Even if it would be nice to live without it, we had to establish quotas to force people sort their mails out once in a while and delete useless things instead of leaving an ever-growing mess behind. The default quota is '''512MB''' which is not that big but should match needs of most users. This said, you may ask us for more and there's no reason we would refuse a reasonable demand. == Technical Details == This service is made using: * [https://www.clamav.net/ ClamAV] * [https://dovecot.org/ Dovecot] * [https://www.postfix.org/ Postfix] * [https://github.com/Snawoot/postfix-mta-sts-resolver postfix-mta-sts-resolver] * [https://www.roundcube.net/ RoundCube] * [https://rspamd.com/ Rspamd] * [https://projects.duckcorp.org/projects/spoolinger Spoolinger] 91c76a10e29c60effc6e5cc31a4aebf724fae807 801 799 2020-04-08T03:57:14Z Duck 2 /* Using a Web Interface */ wikitext text/x-wiki {{Template:Service | description = Available services: * multiple email addresses (mailboxes+aliases or redirections) based on the ''milkypond.org'' (or maybe ''duckcorp.org'') domain * roaming accounts to be able to send emails wherever you are If you want email addresses using you own domain(s), see the [[Services/MailHosting|mail hosting service]]. | prerequisite = | account = global-reg | ipv6 = true | security_notes = Access to the mail services are fully secured, and to your data, nevertheless most mail exchange on the Internet are not. MX DNS records are protected with DNSSEC and we publish a MTA-STS policy as well as DANE/TLSA records to use secure connections as much as possible. Complete security can be achieved using signed and encrypted mails (see [[wikipedia:Pretty_Good_Privacy|OpenPGP]] and [[wikipedia:S/MIME|S/MIME]]) }} == Access == === Using a Mail Reader === You can retrieve your mails, in case of a real mailbox, using either: * IMAP+TLS (TCP 143) / IMAPS (TCP 993) on imap.duckcorp.org * or POP3+TLS (TCP 110) / POP3S (TCP 995) on pop.duckcorp.org The IMAP protocol is recommended over POP3, as it provides many interesting features. If you want to download all your mails absolutely at home, loosing the ability to read your mail from anywhere on the planet, you can do that with IMAP too (look at your mail client settings). You can use our servers to send mails out too via smtp.duckcorp.org using: * SUBMISSION (TCP 587) which is the recommended way and has less chance to be filtered, or alternatively SMTP+TLS (TCP 25) / SMTPS (TCP 465) * and SASL authentication === Using a Web Interface === A [https://webmail.duckcorp.org/ webmail interface] is available. ==== Securing Your Account ==== We strongly suggest you enable [https://en.wikipedia.org/wiki/Multi-factor_authentication Two Factor Authentication (2FA)] to protect your account. With this system your login and password is not sufficient to log in, an external secret is needed. Currently only one method is available: * TOTP: using an application on your phone (FreeOTP available on [http://f-droid.org/ F-Droid] is working fine) In the ''settings'' menu click on the ''2-Factor Authentication'' tab and follow these steps: * click on the ''Setup all fields (needs Save)'' button * on your phone, open the TOPT application and scan the QR code * on your phone generate a code, put it in the ''Check code'' text field and click on the button to validate it works fine * click on the ''show recovery codes'' button and store them is a safe place: print then (or store then on an encrypted disk) * click the ''Save'' button, you will be logged out * check you can login again ==== Mail Encryption and Signing ==== It is possible to encrypt and sign your emails via PGP. In the past is was possible to upload your key on the server but there is a more secure method now: with [https://www.mailvelope.com/ Mailvelope] you can use your key on your machine without exposing your secrets. The company behind Mailvelope proposes various plans but you don't need to subscribe or pay for anything, just install the Free Software plugin for your browser. == Antivirus and Antispam == Mails stored on our server are checked upon arrival for viruses and SPAMs. Outgoing mails from our services are checked too. Mails being viruses are suppressed automatically upon arrival. Mails with a huge probability of being SPAM are destroyed too. Good mails and possibly spammy mails are delivered to your mailbox. SPAMs are more difficult to detect, and it is an error-prone process, so we chose to use a learning software instead of using a global database. After a few weeks of teaching it is able to recognize most of your habits and block a lot of annoying SPAM. === Probable SPAM Notification === Mails are delivered normally with a special field added (''X-Spam-Status'') to your mail headers (not always visible depending on your mail client and its configuration) indicating if the mail is a SPAM and its ''spamminess'' score. This is quite handy if you prefer SPAMs arranged in a specific folder. You may use then the provided [[#Mail Filtering |filtering system]] to sort them properly, or configure your eMail client. === Retraining === Teaching the system what is SPAM and HAM (non-SPAM) is called ''retraining''. If you have of create a folder named ''Junk'', then it is automatically magic: * if you move mail into it, it is automatically retrained as SPAM * if you move mail out of it, it is automatically retrained as HAM * with time, certain old mails automatically expire, see below If you are using an IMAP Sync client which does not support the MOVE operation (isync, offlineimap…) then you unfortunately cannot use this method, please look at the next chapter. To use this folder properly, SPAMs '''must''' be delivered in the ''Junk'' folder automatically, so you can move them out in case of error. You just need to subscribe to this folder in your mail software (this folder is always auto-created). It is not recommended to use your mail software for this filtering, this is horribly inefficient and you would have to set things up on each device and manually synchronize your settings. Automatic expiration logic, based on delivery time (and not the mail timestamp): * deleted mails are purged after 1 day * read mails without an important flag are purge after 7 days * unread mails without an important flag are purge after 30 days If you use the ''incoming_spam'' [[#Global_Rules|global rule]], then SPAMs newly discovered by the system are flagged as important, which means these mails will never by purged until you review it and decide to delete them or mark them as not important. Custom rules might play with this flag and achieve an automatic selection. === Retraining for feature-limited IMAP Sync clients === If your client does not support the MOVE operation (isync, [https://github.com/OfflineIMAP/offlineimap/issues/515 offlineimap]…) then you can only copy (APPEND) mail, which does not work with the magic Junk folder. In this case, you can create special folders called ''SyncSPAM'' and ''SyncHAM'' and copy SPAM and HAM in them. Every two hours a script will pickup these mails, do the retraining, and remove them. Removing these mails from their original locations will be left to you though. == Mail Filtering == With your favourite mail client, you can probably filter your mails in proper folders already. Nevertheless, this can be an annoying operation: * blocking you mail client for a long time if you have to process plenty of mails * downloading each mail information, and sometimes content (depending on your filters), is lenghty too, and cost much bandwidth * syncing filters across your machines (home desktop, laptop, office machine…) is a pain in the ass * processing only when you're online prevents triggering actions in a timely manner (automatic redirect, vacation messages…), and running a machine 24/7 with a mail client polling new mails every 30s is not a solution We provide a much better way to do this using the [[wikipedia:Sieve_(mail_filtering_language)|SIEVE]] filters. Shortly, SIEVE is a language dedicated to expressing mail filters (also called ''rules''). Our server is able to process your mails according to these filters as soon as they arrive. You then don't have to care about them anymore, and may use light mail clients or webmails when you're not on your machine with your favourite software. === Rules Configuration === You can express sort/reject/vacation/… filters using these rules, as the capabilities are very rich. Several softwares support managing SIEVE rules: * Icedove/Thunderbird: *: using the SIEVE extension (in ''xul-ext-sieve'' Debian package), it provides a rules editor (for power-users) * Roundcube: *: coupled with the sieverules extension, provides an easy to use web interface *: this webmail has been made available [https://webmail.duckcorp.org/ here] * sieve-connect: *: provides a CLI to upload/download/activate your rules files *: this tool is available on [[Services/Shell|shell hosts]] (tell us if you know more software supporting this feature) To push your filters on the server, a dedicated protocol exists: MANAGESIEVE (TCP 4190) on ''sieve.duckcorp.org''. Our webmails are already configured to use it, but it you use sieve-connect from our hosts or your own mail software, you'll need these parameters. You can read more info about SIEVE here: * supported SIEVE features on our server: http://pigeonhole.dovecot.org/ * http://www.fastmail.fm/docs/sieve/ * http://sieve.info/ === Global Rules === Global rules are provided to ease configuration on specific filters. They can easily be included in your own configuration. Available rules: * ''incoming_spam'': *: SPAMs will automatically be delivered in the ''Junk'' folder and marked as ''important'' If you write your own custom rules, here is an example on how to use one of them: require ["include"]; include :global "&lt;rule-name&gt;"; === Default Rules === The default settings (since 2112-02-11) are to use the global ''incoming_spam'' rule (see below), in order to provide a simple default configuration for most users. All other mails will end-up in your ''Inbox'' folder and you may then sort them by yourself. If you create your own rules, the default rules won't apply anymore, so power-users can replace the default behavior completely to achieve what they really need. If you want to use the default behavior you can use: require ["include"]; include :global "incoming_spam"; You can also take advantage of the antispam spaminess score to use a different threshold like this: require ["fileinto", "spamtestplus", "relational", "comparator-i;ascii-numeric"]; # if SPAM score is >37% then move into the junk box if spamtest :percent :value "gt" :comparator "i;ascii-numeric" "37" { fileinto "Junk"; stop; } == Fetching eMails from an External Mailbox == {{warning}} This is not supported anymore; you may still redirect mails from your external mailbox to your DuckCorp's email address though. == Shared/Public Folders == {{warning}} This is unfortunately not supported by the synchronization system between our two main mail servers; it was not used anyway. Private (non-shared) namespaces are possible though. You may need to share mails or messages with friends or people you do stuff with (in a project or association). Depending on your needs, two solutions are possible:</del> * share some of your own private folders, thus called ''shared folders'' * manage a special folder hierarchy, called ''public folders'' (even if they may not be accessible to everyone) *: if you need one, ask an administrator; the namespace name can be freely chosen but must be unambiguous and is subject to approval === Namespaces === Through IMAP, or our webmails internally using IMAP, it is possible to partition the folder hierarchy into ''namespaces''. Traditionally you are using the root namespace for your private folders. Additional namespaces can be created and will appear among your own folders or separate, depending on your mail client's choice of representation. To avoid name clashes, we decided to prefix all additional namespace names with a '''#'''. Since 2011-05-14, the following extra namespaces are created and reserved: * #Shared, containing all folders other users decided to share with you * #MilkyPond, containing public MP/DC informational mailboxes you may subscribe at will === Folders Permissions === Using IMAP, it is possible to setup rights (read only, write allowed…) to your own folders in order to share them with other users, or group of users. Public folders are owned by no-one, and must be created by the administrators. Once your request is accepted we will delegate its administration to your care. It can then can be managed like shared folders. === Software Support === Client mail softwares support: * RoundCube: *: support namespaces, shared and public folders configurable via ''Settings->Folders'', selecting a folder then using the ''Sharing'' tab * Icedove/Thunderbird: *: support namespaces, shared and public folders configurable via folder selection and ''Tools->Imap-ACL'' menu action Most other softwares have namespace support only, so you should be able to use shared/public folders you have rights on but not configure them yourself (tell us if you know more software supporting this feature). == Limitations == === Maximum Mail Size === Mail you send or receive are limited to '''20MB'''. If you need to transmit much bigger data, then a mail transport is not appropriate, you'd better use a file sharing method instead. === Quotas === Even if it would be nice to live without it, we had to establish quotas to force people sort their mails out once in a while and delete useless things instead of leaving an ever-growing mess behind. The default quota is '''512MB''' which is not that big but should match needs of most users. This said, you may ask us for more and there's no reason we would refuse a reasonable demand. == Technical Details == This service is made using: * [https://www.clamav.net/ ClamAV] * [https://dovecot.org/ Dovecot] * [https://www.postfix.org/ Postfix] * [https://github.com/Snawoot/postfix-mta-sts-resolver postfix-mta-sts-resolver] * [https://www.roundcube.net/ RoundCube] * [https://rspamd.com/ Rspamd] * [https://projects.duckcorp.org/projects/spoolinger Spoolinger] a44a6e394b64c36e021c2fc7cbbc7672cbf0a68b 0 50 756 607 2018-12-19T07:31:18Z Duck 2 wikitext text/x-wiki {{Template:Service | description = Remote [[wikipedia:Shell_(computing)|shell]] to a DuckCorp machine. | prerequisite = You need to ask an administrator for an account, but we need to know you well-enough to ensure you are trustable. This is '''not''' a VIP requirement, but such an access can be very dangerous and we don't know any other way to avoid a disaster, sorry. You also need to provide a RSA/DSA public key (see ''ssh-keygen''). | account = global-reg | ipv6 = true | security_notes = This service is secure. }} == Access == Via SSH with a RSA/ECDSA/ED25519 key on the following hosts: (ED25519 recommended) * thorfinn.duckcorp.org (prefered for lengthy sessions, like screens) * toushirou.duckcorp.org (mostly useful to manage Web/FTP data) Via SSH+[http://mosh.mit.edu/ Mosh], with the same hosts and conditions defined above. On Debian you can use the ''mosh'' package to get the client application and do ''mosh &lt;server&gt;''. === Locked behind a firewall === If you are obliged to go through a firewall (at work for eg), you can try a few things to through and end-up on Toushirou (and can bounce on Thorfinn then). First, if you know there is a proxy, or direct access does not work, you may be able to find the firewall host and port in the browser configuration. If there is none, then the proxy may be transparent (hidden) and you can try a direct SSH access using ''portal.duckcorp.org'' on port ''443''. If it does not work, you can try using a tool to wrap SSH through the firewall. From a terminal the ''corkscrew'' (Debian has a package of the same name) tool car be used with the following SSH configuration (in ''~/.ssh/config''): Host portal.duckcorp.org ProxyCommand /usr/bin/corkscrew &lt;proxy-host&gt; &lt;proxy-port&gt; %h %p and connect with: ssh portal.duckcorp.org == Available Resources == The following resources are available and will remain until we advertise a scheduled removal. If you miss something you can send us a request. === Locales === {{warning}} warning for Mosh users: Mosh only supports UTF-8 locales * br_FR.UTF-8 * en_GB.UTF-8 * en_US.UTF-8 * fr_FR.UTF-8 * ja_JP.EUC-JP * ja_JP.UTF-8 === Shells === * dash * bash * zsh * ksh * tcsh === Programs === * aspell (with same support as system locales) * dict * emacs * graphviz * imagemagick * irssi (with plugins and scripts) * latex (full TeXlive on Thorfinn, limited installation on Toushirou) * p7zip * rsync * screen * sieve-connect * unar * unison * vim * w3m * weechat (with plugins and scripts) (and probably a few others we forgot to mention) Additional tools: * [[Services/VCS|VCS tools]] === Weechat Relay via WSS === If you have weechat running in screen/tmux, then maybe you would like to open access to it to connect your phone (the [https://f-droid.org/en/packages/com.ubergeek42.WeechatAndroid/ Weechat for Android app] has been tested with this setup). For security reasons we do not open ports directly but proxy it via WSS. If you would like such a setup, please ask us and we would assign a specific port. Then you can setup your Weechat relay like this: /set relay.network.password &lt;password&gt; /set relay.network.bind_address ::1 /relay add weechat &lt;port&gt; And ask your app to connect to ''static.perso.duckcorp.org/&lt;user&gt;/weechat'' using websocket+TLS and your password. === Spaces === The following spaces are available: * your home * ask an administrator if you need a project-specific space in /srv/projects/ on Toushirou * ask an administrator if you need a space for public VCS repositories on _vcs.duckcorp.org_ (Toushirou) * ask an administrator if you need a space (personal or project) on the public FTP (private FTP spaces are ***OBSOLETE***) == Technical Details == This service is made using: * [http://www.openssh.org/ OpenSSH] * [http://mosh.mit.edu/ Mosh] 8ba7f27495224b6d42cac69869d4d369c97c8cda 800 756 2019-09-30T03:30:39Z Duck 2 /* Spaces */ wikitext text/x-wiki {{Template:Service | description = Remote [[wikipedia:Shell_(computing)|shell]] to a DuckCorp machine. | prerequisite = You need to ask an administrator for an account, but we need to know you well-enough to ensure you are trustable. This is '''not''' a VIP requirement, but such an access can be very dangerous and we don't know any other way to avoid a disaster, sorry. You also need to provide a RSA/DSA public key (see ''ssh-keygen''). | account = global-reg | ipv6 = true | security_notes = This service is secure. }} == Access == Via SSH with a RSA/ECDSA/ED25519 key on the following hosts: (ED25519 recommended) * thorfinn.duckcorp.org (prefered for lengthy sessions, like screens) * toushirou.duckcorp.org (mostly useful to manage Web/FTP data) Via SSH+[http://mosh.mit.edu/ Mosh], with the same hosts and conditions defined above. On Debian you can use the ''mosh'' package to get the client application and do ''mosh &lt;server&gt;''. === Locked behind a firewall === If you are obliged to go through a firewall (at work for eg), you can try a few things to through and end-up on Toushirou (and can bounce on Thorfinn then). First, if you know there is a proxy, or direct access does not work, you may be able to find the firewall host and port in the browser configuration. If there is none, then the proxy may be transparent (hidden) and you can try a direct SSH access using ''portal.duckcorp.org'' on port ''443''. If it does not work, you can try using a tool to wrap SSH through the firewall. From a terminal the ''corkscrew'' (Debian has a package of the same name) tool car be used with the following SSH configuration (in ''~/.ssh/config''): Host portal.duckcorp.org ProxyCommand /usr/bin/corkscrew &lt;proxy-host&gt; &lt;proxy-port&gt; %h %p and connect with: ssh portal.duckcorp.org == Available Resources == The following resources are available and will remain until we advertise a scheduled removal. If you miss something you can send us a request. === Locales === {{warning}} warning for Mosh users: Mosh only supports UTF-8 locales * br_FR.UTF-8 * en_GB.UTF-8 * en_US.UTF-8 * fr_FR.UTF-8 * ja_JP.EUC-JP * ja_JP.UTF-8 === Shells === * dash * bash * zsh * ksh * tcsh === Programs === * aspell (with same support as system locales) * dict * emacs * graphviz * imagemagick * irssi (with plugins and scripts) * latex (full TeXlive on Thorfinn, limited installation on Toushirou) * p7zip * rsync * screen * sieve-connect * unar * unison * vim * w3m * weechat (with plugins and scripts) (and probably a few others we forgot to mention) Additional tools: * [[Services/VCS|VCS tools]] === Weechat Relay via WSS === If you have weechat running in screen/tmux, then maybe you would like to open access to it to connect your phone (the [https://f-droid.org/en/packages/com.ubergeek42.WeechatAndroid/ Weechat for Android app] has been tested with this setup). For security reasons we do not open ports directly but proxy it via WSS. If you would like such a setup, please ask us and we would assign a specific port. Then you can setup your Weechat relay like this: /set relay.network.password &lt;password&gt; /set relay.network.bind_address ::1 /relay add weechat &lt;port&gt; And ask your app to connect to ''static.perso.duckcorp.org/&lt;user&gt;/weechat'' using websocket+TLS and your password. === Spaces === The following spaces are available: * your home * ask an administrator if you need a project-specific space in ''/srv/projects/'' on Toushirou * ask an administrator if you need a space for public VCS repositories on ''vcs.duckcorp.org'' (Toushirou) * ask an administrator if you need a space (personal or project) on the public FTP (private FTP spaces are ***OBSOLETE***) == Technical Details == This service is made using: * [http://www.openssh.org/ OpenSSH] * [http://mosh.mit.edu/ Mosh] d91ec95829011801551d836f08985bf0241505bf 0 55 767 499 2019-01-02T03:47:19Z Duck 2 wikitext text/x-wiki {{Template:Service | description = [[wikipedia:Irc|IRC]] (Internet Relay Chat) is a chat system. We have our own internal network, formerly used to contact administrators and discuss with other users. Even is not advertise widely, external people may join the network, so you can invite your friend. | prerequisite = | account = | ipv6 = true | security_notes = Your messages are secured if you connect using the secure port(s), but you need to ensure the recipient uses a secure connection too ; this can be achieved using chanmode +S (see below). {{warning}} Unfortunately, due to a bug in the software (see {{dc-projects|233}}), the link between our servers is not yet fully secured, but you can work around this problem if you talk only to people connected to the same server as yourself. }} == Access == === Using an IRC Software === To connect you need and IRC client, like for example: * [http://irssi.org/ Irssi] * [http://www.pidgin.im Pidgin] * [http://weechat.org/ WeeChat] You need to configure these parameters: * host: irc.milkypond.org * port: ** 6680 (if you want a secure connection using SSL/TLS) ** 6667 or 6669 (because 6667 is sometimes filtered) No password is needed to connect. === Using a Web Interface === Use the following URL: https://irconweb.milkypond.org/ == Official Channels == * #MilkyPond: main channel used to meet with other users and friends and ask general questions * #DuckCorp: contact with DuckCorp Administrators and technical discussions == Contacting IRC Administrators == In case of problems on IRC you can find connected administrators using this command (mind the idle time): /QUOTE STATS P Beware IRC Administrators may not be DuckCorp Administrators. == Features == === Commands === You can see available commands using this command: /QUOTE HELP You can get help about a particular command using this command: /QUOTE HELP &lt;command&gt; ==== Additional Commands for IRC Administrators ==== All special commands are listed in the Oper MOTD. === User Modes === You can see available channel modes using this command: /QUOTE HELP UMODE ==== Mode +g ==== (partial quote from the ircd-ratbox documentation) When a client is set +g, that user will be in "Caller ID" mode. Any user that messages a +g client will receive a notice saying that they are in +g (server side ignore) mode. The target client (who is set +g) will also receive a notice saying that so and so messaged them, and that they are in +g mode. The target of the message will only receive one notification per minute, from any client, in order to help prevent flooding. The sender will '''not''' have the rate limit, and will receive a notice saying the target is in +g mode every time they send a message. Note that this behavior is similar to the way AWAY messages are done. There are numerous benefits for both opers and regular users, including the ability to stop spambot messages from ever reaching your client, stopping private message and CTCP floods, and being able to sit on IRC in privacy. One question that arises is how to message specific users, while blocking out everyone else. The command ACCEPT is your answer. To add a user to your accept list, issue the raw command: /QUOTE ACCEPT &lt;nick&gt;,&lt;nick&gt;,&lt;nick&gt;,… That user will now be able to send messages to your client until the association is broken. Associations break in one of the following situations: when an accepted user QUIT's (or is on the other side of a split), you QUIT, or the accepted user changes their nick. The reason why a remote user's nick change will remove them from your accept list is so that you cannot track a user after they changed their nick. Viewing the accept list is also very easy. Issue the raw command: /QUOTE ACCEPT * Removing a user from your accept list is also simple. Issue the command: /QUOTE ACCEPT -&lt;nick&gt; === Channel Modes === You can see available channel modes using this command: /QUOTE HELP CHMODE These extra modes are also available: * +R - registered - Users must be registered with services to JOIN * +z - ssl only - Requires SSL/TLS connections to join === IRC Services === To help not loose your favorite nick or channel, the IRC Services can register them so you're still in control. It also helps manage channel with a variety of tools. Look at the user introduction manual in the documentation below. List of Services: * ALIS: search available channels * USERSERV: register an account * INFOSERV: read operator news (not in use in this network, we send global announces and post to the mailing-list) * STATSERV: few network information (not that useful) List of Services available with an account (see USERSERV): * NICKSERV: register nicknames * GROUPSERV: manage group of users used in ACLs * CHANSERV: register and manage channels * MEMOSERV: send and receive memos from other registered users To get help on each service commands, use the following command: /QUOTE &lt;service&gt; HELP ==== Additional Services for IRC Administrators ==== (exact privileges depends on trust and delegation) * OPERSERV: superadmin commands * GLOBAL: messaging all users === Secure Service Authentication (CERTFP) === You can authenticate to your service account using a password, but it is more secure to use a certificate and not too complicated to setup. The Freenode network has a good [https://freenode.net/kb/answer/certfp documentation for this feature]. == Documentation == * [http://docs.ratbox.org/svc_userintro.shtml IRC Services Introduction] == Technical Details == This service is made using: * [https://www.inspircd.org/ InspIRCd] * [https://atheme.github.io/atheme.html Atheme IRC Services] * [https://thelounge.github.io/ The Lounge] (Web UI) 793bc760797c4c3aab95b5bc2a290b256b7a9c0c 0 47 778 568 2019-04-18T02:39:22Z Duck 2 wikitext text/x-wiki Here is the list of '''current''' DuckCorp's administrators. These are the only people which have full access to the system (even if we may delegate nonsensitive things to trusted parties, but you'll always be warned of such changes). == Active administrators == * Duck: *: Full Name: Marc Dequènes *: GPG Key Fingerprint: 7297 2A83 E526 453D F288 5F81 55E9 F9F7 AC1C 443F *: (old: 6ADD 5093 AC6D 1072 C912 9000 B1CC D972 9026 7086) * Pilou: *: Full Name: Pierre-Louis Bonicoli *: GPG Key Fingerprint: 21F2 2208 336D 3C26 431D 028A DBD7 1F45 5255 2D44 *: (old: 2B1E DB5E ABEB 0483 AA50 15B3 13FA 63E9 3F25 BB1F) == Fallback administrators == * Arnau: *: Full Name: Arnaud Fontaine *: GPG Key Fingerprint: 43B5 1C2A AAD3 E0D4 9ACF 8F59 97C2 C6AB 313C 7B03 *: (old: D792 B8A5 A567 B001 C342 2613 BDF2 A220 5E36 19D3) a28043afa0c2ef2e46b682c9f80b41f94d873e4b 0 68 779 515 2019-04-21T09:22:25Z Duck 2 wikitext text/x-wiki {{Template:Service | description = The StuffCloud service is a webservice used to access, sync, and share your personal data. Currently you can: * store your files and share them with people inside and outside DuckCorp (and in-place view/edit of certain extensions directly from the web interface) * manage your contacts * manage your calendars * manage your tasks * manage your notes * manage your web bookmarks (with browser Sync) * backup/restore your SMS * create your own groups (circles) | prerequisite = | account = global | ipv6 = true | security_notes = This service is secure but beware when sharing your data to other people. }} {{warning}} Remember not to use this service to store illegal or non-free data. == Access == === Web Interface === Use this URL in your browser: https://stuff.milkypond.org/ Then you can setup your contacts, calendars, store files… We strongly suggest you enable [https://en.wikipedia.org/wiki/Multi-factor_authentication Two Factor Authentication (2FA)] to protect your account. With this system your login and password is not sufficient to log in, an external secret is needed. Two methods are avaible in the security tab of your preferences: * TOTP: using an application on your phone (FreeOTP available on F-Droid is working fine) * U2F: an external device like an USB key (Yubikey for example) It is very easy to use TOPT with your phone and the FreeOTP application (available on [http://f-droid.org/ F-Droid]). You [https://docs.nextcloud.com/server/stable/user_manual/user_2fa.html can find here] more detailed explanation on how to set this up. Do not forget to generate and print (or store on an encrypted disk) the recovery code in case your device is lost. Also please note your connected devices (smartphone, tablet…) using StuffCloud to sync contacts/calendars/files/… will not be able to login anymore using login/password, but you can generate tokens which are safer (see below). === WebDAV Interface === You can use the [[wikipedia:WebDAV|WebDAV]] interface to sync your data from a desktop application or you mobile device. Applications can use the main address of the web interface (see above) with your credentials and should be able to discover you data, but sometimes they have limitations and you need to specify a full ugly link ; in this case you can find the link in the interface, either on the resource to access or in your personal settings page. It is not safe to use your login/password to connect your mobile devices, and this does not work with 2FA anyway. Thus we recommend you to [https://docs.nextcloud.com/server/stable/user_manual/session_management.html?highlight=token generate tokens], one for each device so you can easily remove access to a lost or stolen device. ==== Files ==== * Desktop: ** remote drive (synchronous): use XFCE/Gigolo or GNOME/Nautilus ** synchronize (asynchronous): use the [https://nextcloud.com/install/#install-clients sync] utility (no Debian package yet) * Mobile Devices: ** Android: use the [https://nextcloud.com/install/#install-clients NextCloud] app (available on [http://f-droid.org/ F-Droid]) to synchronize files ==== Contacts ==== * Desktop: synchronize with GNOME/Evolution * Mobile Devices: ** Android: the '''DAVdroid''' app (available on [http://f-droid.org/ F-Droid]) works well * Webmail: works nicely with the newest webmail (RoundCube) (see in Settings->Preferences->CardDAV) ==== Calendars ==== * Desktop: synchronize with GNOME/Evolution * Mobile Devices: ** Android: the '''DAVdroid''' app (available on [http://f-droid.org/ F-Droid]) works well * Webmail: should work but it does not seem to parse events properly even if there's no errors (see in Settings->Preferences->Calendar and the Provider field) ==== Tasks ==== It may be provided by your calendar application. * Desktop: ??? * Mobile Devices: ** Android: the '''DAVdroid''' app for synchronization and '''OpenTasks''' for UI work well (both available on [http://f-droid.org/ F-Droid]) ** webmail: not supported ==== Notes ==== * Desktop: ??? * Mobile Devices: ** Android: the '''Notes''' app (available on [http://f-droid.org/ F-Droid]) works but seem to have some bugs (like duplicate saving, to be investigated) ==== Web Bookmarks ==== * Desktop: ** Firefox: the [https://addons.mozilla.org/en-US/firefox/addon/floccus/ Floccus] app works; it creates a special bookmark in ''Other Bookmarks'' called ''Owncloud'' (I don't think renaming would not break things); the sync happens every 25 minutes, so be patient ** Chromium: the [https://github.com/marcelklehr/floccus/releases/ Floccus] app is untested * Mobile Devices: ** Android: *** the '''Nextcloud Bookmarks''' app (available on [http://f-droid.org/ F-Droid]) works well *** the '''save to Nextcloud Bookmarks''' app (available on [http://f-droid.org/ F-Droid]) is supposed to work but does not seem to connect… == Documentation == * ''NextCloud'' section in the [https://docs.nextcloud.com/ Documentation Page] == Technical Details == This service is made using: * [https://nextcloud.com/ NextCloud] ec364c80680accebdf525a8f4dac2803ea0c49e6 780 779 2019-05-03T05:37:34Z Duck 2 /* Web Interface */ wikitext text/x-wiki {{Template:Service | description = The StuffCloud service is a webservice used to access, sync, and share your personal data. Currently you can: * store your files and share them with people inside and outside DuckCorp (and in-place view/edit of certain extensions directly from the web interface) * manage your contacts * manage your calendars * manage your tasks * manage your notes * manage your web bookmarks (with browser Sync) * backup/restore your SMS * create your own groups (circles) | prerequisite = | account = global | ipv6 = true | security_notes = This service is secure but beware when sharing your data to other people. }} {{warning}} Remember not to use this service to store illegal or non-free data. == Access == === Web Interface === Use this URL in your browser: https://stuff.milkypond.org/ Then you can setup your contacts, calendars, store files… We strongly suggest you enable [https://en.wikipedia.org/wiki/Multi-factor_authentication Two Factor Authentication (2FA)] to protect your account. With this system your login and password is not sufficient to log in, an external secret is needed. Two methods are available in the security tab of your preferences: * TOTP: using an application on your phone (FreeOTP available on F-Droid is working fine) * U2F: an external device like an USB key (Yubikey for example) It is very easy to use TOPT with your phone and the FreeOTP application (available on [http://f-droid.org/ F-Droid]). You [https://docs.nextcloud.com/server/stable/user_manual/user_2fa.html can find here] more detailed explanation on how to set this up. Do not forget to generate and print (or store on an encrypted disk) the recovery code in case your device is lost. Also please note your connected devices (smartphone, tablet…) using StuffCloud to sync contacts/calendars/files/… will not be able to login anymore using login/password, but you can generate tokens which are safer (see below). === WebDAV Interface === You can use the [[wikipedia:WebDAV|WebDAV]] interface to sync your data from a desktop application or you mobile device. Applications can use the main address of the web interface (see above) with your credentials and should be able to discover you data, but sometimes they have limitations and you need to specify a full ugly link ; in this case you can find the link in the interface, either on the resource to access or in your personal settings page. It is not safe to use your login/password to connect your mobile devices, and this does not work with 2FA anyway. Thus we recommend you to [https://docs.nextcloud.com/server/stable/user_manual/session_management.html?highlight=token generate tokens], one for each device so you can easily remove access to a lost or stolen device. ==== Files ==== * Desktop: ** remote drive (synchronous): use XFCE/Gigolo or GNOME/Nautilus ** synchronize (asynchronous): use the [https://nextcloud.com/install/#install-clients sync] utility (no Debian package yet) * Mobile Devices: ** Android: use the [https://nextcloud.com/install/#install-clients NextCloud] app (available on [http://f-droid.org/ F-Droid]) to synchronize files ==== Contacts ==== * Desktop: synchronize with GNOME/Evolution * Mobile Devices: ** Android: the '''DAVdroid''' app (available on [http://f-droid.org/ F-Droid]) works well * Webmail: works nicely with the newest webmail (RoundCube) (see in Settings->Preferences->CardDAV) ==== Calendars ==== * Desktop: synchronize with GNOME/Evolution * Mobile Devices: ** Android: the '''DAVdroid''' app (available on [http://f-droid.org/ F-Droid]) works well * Webmail: should work but it does not seem to parse events properly even if there's no errors (see in Settings->Preferences->Calendar and the Provider field) ==== Tasks ==== It may be provided by your calendar application. * Desktop: ??? * Mobile Devices: ** Android: the '''DAVdroid''' app for synchronization and '''OpenTasks''' for UI work well (both available on [http://f-droid.org/ F-Droid]) ** webmail: not supported ==== Notes ==== * Desktop: ??? * Mobile Devices: ** Android: the '''Notes''' app (available on [http://f-droid.org/ F-Droid]) works but seem to have some bugs (like duplicate saving, to be investigated) ==== Web Bookmarks ==== * Desktop: ** Firefox: the [https://addons.mozilla.org/en-US/firefox/addon/floccus/ Floccus] app works; it creates a special bookmark in ''Other Bookmarks'' called ''Owncloud'' (I don't think renaming would not break things); the sync happens every 25 minutes, so be patient ** Chromium: the [https://github.com/marcelklehr/floccus/releases/ Floccus] app is untested * Mobile Devices: ** Android: *** the '''Nextcloud Bookmarks''' app (available on [http://f-droid.org/ F-Droid]) works well *** the '''save to Nextcloud Bookmarks''' app (available on [http://f-droid.org/ F-Droid]) is supposed to work but does not seem to connect… == Documentation == * ''NextCloud'' section in the [https://docs.nextcloud.com/ Documentation Page] == Technical Details == This service is made using: * [https://nextcloud.com/ NextCloud] ffd8be37c1a8d8894dd68cfe5ec1385af2fe6931 795 780 2019-07-30T02:28:57Z Arnau 8 Add Joplin app (louis) wikitext text/x-wiki {{Template:Service | description = The StuffCloud service is a webservice used to access, sync, and share your personal data. Currently you can: * store your files and share them with people inside and outside DuckCorp (and in-place view/edit of certain extensions directly from the web interface) * manage your contacts * manage your calendars * manage your tasks * manage your notes * manage your web bookmarks (with browser Sync) * backup/restore your SMS * create your own groups (circles) | prerequisite = | account = global | ipv6 = true | security_notes = This service is secure but beware when sharing your data to other people. }} {{warning}} Remember not to use this service to store illegal or non-free data. == Access == === Web Interface === Use this URL in your browser: https://stuff.milkypond.org/ Then you can setup your contacts, calendars, store files… We strongly suggest you enable [https://en.wikipedia.org/wiki/Multi-factor_authentication Two Factor Authentication (2FA)] to protect your account. With this system your login and password is not sufficient to log in, an external secret is needed. Two methods are available in the security tab of your preferences: * TOTP: using an application on your phone (FreeOTP available on F-Droid is working fine) * U2F: an external device like an USB key (Yubikey for example) It is very easy to use TOPT with your phone and the FreeOTP application (available on [http://f-droid.org/ F-Droid]). You [https://docs.nextcloud.com/server/stable/user_manual/user_2fa.html can find here] more detailed explanation on how to set this up. Do not forget to generate and print (or store on an encrypted disk) the recovery code in case your device is lost. Also please note your connected devices (smartphone, tablet…) using StuffCloud to sync contacts/calendars/files/… will not be able to login anymore using login/password, but you can generate tokens which are safer (see below). === WebDAV Interface === You can use the [[wikipedia:WebDAV|WebDAV]] interface to sync your data from a desktop application or you mobile device. Applications can use the main address of the web interface (see above) with your credentials and should be able to discover you data, but sometimes they have limitations and you need to specify a full ugly link ; in this case you can find the link in the interface, either on the resource to access or in your personal settings page. It is not safe to use your login/password to connect your mobile devices, and this does not work with 2FA anyway. Thus we recommend you to [https://docs.nextcloud.com/server/stable/user_manual/session_management.html?highlight=token generate tokens], one for each device so you can easily remove access to a lost or stolen device. ==== Files ==== * Desktop: ** remote drive (synchronous): use XFCE/Gigolo or GNOME/Nautilus ** synchronize (asynchronous): use the [https://nextcloud.com/install/#install-clients sync] utility (no Debian package yet) * Mobile Devices: ** Android: use the [https://nextcloud.com/install/#install-clients NextCloud] app (available on [http://f-droid.org/ F-Droid]) to synchronize files ==== Contacts ==== * Desktop: synchronize with GNOME/Evolution * Mobile Devices: ** Android: the '''DAVdroid''' app (available on [http://f-droid.org/ F-Droid]) works well * Webmail: works nicely with the newest webmail (RoundCube) (see in Settings->Preferences->CardDAV) ==== Calendars ==== * Desktop: synchronize with GNOME/Evolution * Mobile Devices: ** Android: the '''DAVdroid''' app (available on [http://f-droid.org/ F-Droid]) works well * Webmail: should work but it does not seem to parse events properly even if there's no errors (see in Settings->Preferences->Calendar and the Provider field) ==== Tasks ==== It may be provided by your calendar application. * Desktop: ??? * Mobile Devices: ** Android: *** the '''DAVdroid''' app for synchronization and '''OpenTasks''' for UI work well (both available on [http://f-droid.org/ F-Droid]) *** the '''Joplin''' app is a free, open source note taking and to-do application, which can be synchronized with nextcloud using the webdav URL, i.e. https://stuff.milkypond.org/remote.php/webdav/xxx where xxx is the name of the folder where notes will be saved. * Webmail: not supported ==== Notes ==== * Desktop: ??? * Mobile Devices: ** Android: *** the '''Notes''' app (available on [http://f-droid.org/ F-Droid]) works but seem to have some bugs (like duplicate saving, to be investigated) *** the '''Joplin''' app is a free, open source note taking and to-do application, which can be synchronized with nextcloud using the webdav URL, i.e. https://stuff.milkypond.org/remote.php/webdav/xxx where xxx is the name of the folder where notes will be saved. ==== Web Bookmarks ==== * Desktop: ** Firefox: the [https://addons.mozilla.org/en-US/firefox/addon/floccus/ Floccus] app works; it creates a special bookmark in ''Other Bookmarks'' called ''Owncloud'' (I don't think renaming would not break things); the sync happens every 25 minutes, so be patient ** Chromium: the [https://github.com/marcelklehr/floccus/releases/ Floccus] app is untested * Mobile Devices: ** Android: *** the '''Nextcloud Bookmarks''' app (available on [http://f-droid.org/ F-Droid]) works well *** the '''save to Nextcloud Bookmarks''' app (available on [http://f-droid.org/ F-Droid]) is supposed to work but does not seem to connect… == Documentation == * ''NextCloud'' section in the [https://docs.nextcloud.com/ Documentation Page] == Technical Details == This service is made using: * [https://nextcloud.com/ NextCloud] 2563235afed06353ca26754664d8adab80abe55d 0 46 802 459 2020-04-08T04:05:05Z Duck 2 wikitext text/x-wiki == Introduction == '''All''' services containing sensitive information are protected using cryptography. Whenever possible, we add the necessary configuration to ensure unsecure usages are not possible, to protect your data. Nevertheless, a few things are needed on your side to improve security, that's why we are providing the following notes in order to help you configure your software in a secure fashion. You can read more about [https://projects.duckcorp.org/projects/dc-admin/wiki/Security_Model ou security model on the wiki]. == Areas of Security == === Mails from DC's Administrators === You should not trust mails pretenting to come from us. The only way to be sure a mail is from someone, is to agree on exchanging cryptographically-protected messages. On [[Admins|this page]] you'll find the list of DC's administrators from which you may receive mails (on the users's mailing-list for example). You could trust their GPG keys directly, but that would not be secure at all. The best way is to meet, live, in a [[wikipedia:Key_signing_party|key signing party]]. If a friend has already signed our key, and is not too far from you, you may also propagate your trust to our keys. Once done, you'll be sure what seems to come from us is really from us. === Talking to the Right Machine/Service === All remote services use an address on the internet, like ''superservice.duckcorp.org'', but if you are connected through an untrusted network (like if you're using a third-party's WIFI), you cannot be sure you'll be connecting to the right machine, and you may disclose important information like your credentials. ==== TLS/SSL-based Services ==== Nowadays we use Let's Encrypt certificates for all public-facing services. Your system should already be configured out of the box to support it. ===== Using DuckCorp's Internal CA ===== If you need to access internal service like LDAP, then you'll need to configure your system to use DuckCorp's CA with the procedure below. To ensure you're talking to the right server, and noone pretend to be a DC's server to tricks you, you need to install the following certificate ([[File:Duckcorp.crt]], which was signed by Arnau [[File:Arnau duckcorp.crt.asc]], Pilou [[File:Pilou duckcorp.crt.asc]] and Duck [[File:Duck duckcorp.crt.asc]]): * either in your software configuration (for example, to validate HTTP site in your browser, clicking on the link should ask for installation, and you'll just need to confirm you trust it) ** For Firefox you must manually import the certificate ([http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=316436 #316436]): Preferences -> Advanced -> Certificates -> View Certificates -> Authorities -> Import. ** For Chromium too, you must manually import the certificate: Settings -> Show advanced settings -> Manage certificates -> Authorities -> Import. * or globally on your host by installing the certificate, as root: ** (method 1, prefered) in ''/usr/local/share/ca-certificates'', and running ''update-ca-certificates'' (the ''ca-certificates'' package needs to be installed) ** (method 2, not suitable for GNUTLS-based apps) in ''/etc/ssl/certs'', and running ''c_rehash'' (the ''openssl'' package needs to be installed) The certificate and signatures can also be downloaded from the following link: http://ca.duckcorp.org/ ==== Service Locator Security ==== One possible attack is to alter replies from the machine locator service (DNS) in order to redirect your communication to a nasty machine. Since November 2010, ''duckcorp.org'' and ''milkypond.org'' domains are cryptographically signed using the DNSSEC system, so you are now able to verify the address returned for the service is the right one. This system is not new, but has recently switched into production, so your operating system may not yet be properly configured to use this protection. Until it is pre-configured in most of them, you may configure it yourself using [[Services/DNS#How_to_test_my_zone_is_secured.3F|this procedure]]. {{warning}} Beware this protection solves certains security problems but is not sufficient to ensure you're talking to the right machine/service. Nevertheless it ensures: * the address of the machine/service is the right one * information related to the domain, list of mail servers, security information on hosts (SSHFP)… are not tampered Using this security plus certificate verification (see [[Services/Security#TLS.2FSSL-based_Services|section about TLS/SSL-based Security]]) would ensure full security. === Secure SSH Connections === In order not to be tricked connecting to a fake server, or to a rooted server (just in case), it is possible to check the SSH key of the server. As this verification is quite boring both for administrators and users, almost nobody on earth does it. Fortunately, it is possible to publish this information in the DNS and have OpenSSH check it for you automatically. To add this security, you can edit your system configuration (''/etc/ssh/ssh_config'') or your personal one (''~/.ssh/config''), and add the folowing: Host * VerifyHostKeyDNS ask Of course, the DNS replies may be altered, so if you want full security, read the [[Services/Security#Service_Locator_Security|section about Service Locator Security]]. 450d4c6494030ae6fe357435affaab04495b962a 0 65 806 476 2020-04-08T05:07:56Z Duck 2 wikitext text/x-wiki {{Template:Service | description = News feeds reader through a web interface. | prerequisite = none | account = global | ipv6 = true | security_notes = This service is secure except if you don't check the website certificate properly (like on Android, see below). }} == Access == === Using a Web Browser === You can connect to the web interface using the following URL: https://gossip.duckcorp.org/ === Using the Android Application === You need the official ttrss application, see: https://play.google.com/store/apps/details?id=org.fox.ttrss (at least another unofficial applications exists made by Nils Braden, but it doesn't work well, TLS certificates problems) Unfortunately the application available on [http://f-droid.org/ F-Droid] is Nils' one and does not work. So if you do not have the Google Play Store on your phone (which is recommended for security and privacy), you may fetch this application using the [https://apk-dl.com/ APK Downloader]. To unlock all the features you will need the Google Play Store to be able to pay, sorry. You might ask a friend or have a dirty phone (like an old one for this kind of infrequent uses) to retrieve the APK (hint: '''Apk Extractor''' and '''SD Scanner''' can help you). The special app you need to get and install just once is: https://play.google.com/store/apps/details?id=org.fox.ttrss.key&rdid=org.fox.ttrss.key You need to connect once through your web browser to activate the web API, which is needed by the Android application: look in Preferences -> Advanced -> Enable external API. Then you can configure your application: * URL: https://gossip.duckcorp.org/ * Login/Password * Accept any SSL certificate: '''False''' * HTTP authentication Login/Password: repeat Login/Password === Sharing News === You can share interesting news: * by mail (but there is no link to your address book) * by URL: these ones are public, meaning there is no need to authenticate to use them, so you can give them away to anybody == Technical Details == This service is made using: * [http://tt-rss.org/ Tiny Tiny RSS] 3d7eceab946aecc58ff5f1ee7afb2f2ff0001f45 0 66 807 587 2020-04-08T05:18:50Z Duck 2 wikitext text/x-wiki {{Template:Service | description = A project management and issue tracking software is a tool intended to help organize projects (not only computer science related projects), from various aspects: scheduling, planning, communication, tracking, documentation… | prerequisite = You may need to ask a project administrator for membership to access certain projects and resources, but can already login with your global account. A few projects may be public, which means you (or outsiders) can access most information without authenticating (and maybe even add some). | account = global-reg | ipv6 = true | security_notes = This service is secure. }} == Access == Use the following URL and login: https://projects.duckcorp.org/ == Editorial Policy == This is a space of freedom but please be considerate with past works and use a respectful tone, thank you. == Documentation == * [https://www.mediawiki.org/wiki/Help:Contents Help Pages] == Technical Details == This service is made using: * [https://www.mediawiki.org/ MediaWiki] d3c432e126a097cc7f87732cd44b5208a6ddc357 809 807 2020-04-08T05:20:23Z Duck 2 Undo revision 807 by [[Special:Contributions/Duck|Duck]] ([[User talk:Duck|talk]]) wikitext text/x-wiki {{Template:Service | description = A project management and issue tracking software is a tool intended to help organize projects (not only computer science related projects), from various aspects: scheduling, planning, communication, tracking, documentation… | prerequisite = You may need to ask a project administrator for membership to access certain projects and resources, but can already login with your global account. A few projects may be public, which means you (or outsiders) can access most information without authenticating (and maybe even add some). | account = global-reg | ipv6 = true | security_notes = This service is secure. }} == Access == Use the following URL and login: https://projects.duckcorp.org/ == Managing a Project == Ask an administrator if you need a project created. You will be set as Manager and will be able to manage your project settings and members. This can be coupled with a [[Services/VCS|VCS access]]. == Documentation == * [http://www.redmine.org/guide Help Page] * generic documentation on [[wikipedia:Project_management_software|Project management software]] == Technical Details == This service is made using: * [http://www.redmine.org/ Redmine] ec141deca435d03d1cbfc9b4f69c2e4394746fe9 810 809 2020-04-08T05:20:56Z Duck 2 HTTPS wikitext text/x-wiki {{Template:Service | description = A project management and issue tracking software is a tool intended to help organize projects (not only computer science related projects), from various aspects: scheduling, planning, communication, tracking, documentation… | prerequisite = You may need to ask a project administrator for membership to access certain projects and resources, but can already login with your global account. A few projects may be public, which means you (or outsiders) can access most information without authenticating (and maybe even add some). | account = global-reg | ipv6 = true | security_notes = This service is secure. }} == Access == Use the following URL and login: https://projects.duckcorp.org/ == Managing a Project == Ask an administrator if you need a project created. You will be set as Manager and will be able to manage your project settings and members. This can be coupled with a [[Services/VCS|VCS access]]. == Documentation == * [https://www.redmine.org/guide Help Page] * generic documentation on [[wikipedia:Project_management_software|Project management software]] == Technical Details == This service is made using: * [https://www.redmine.org/ Redmine] 3612052c4312ade19ac012723455258eed1a978e 0 179 808 2020-04-08T05:19:45Z Duck 2 Created page with "{{Template:Service | description = Wiki with articles or tips on various subjects | prerequisite = none | account = global | ipv6 = true | security_notes = This service is sec..." wikitext text/x-wiki {{Template:Service | description = Wiki with articles or tips on various subjects | prerequisite = none | account = global | ipv6 = true | security_notes = This service is secure but don't input any private information as everything is public. }} == Access == Use this URL in your browser: https://wiki.duckcorp.org/ == Editorial Policy == This is a space of freedom but please be considerate with past works and use a respectful tone, thank you. == Documentation == * [https://www.mediawiki.org/wiki/Help:Contents Help Pages] == Technical Details == This service is made using: * [https://www.mediawiki.org/ MediaWiki] 9a4000b6659c8ff3f747db1ca1f22912631c2d77 0 49 811 801 2020-04-08T05:23:44Z Duck 2 wikitext text/x-wiki {{Template:Service | description = Available services: * multiple email addresses (mailboxes+aliases or redirections) based on the ''milkypond.org'' (or maybe ''duckcorp.org'') domain * roaming accounts to be able to send emails wherever you are If you want email addresses using you own domain(s), see the [[Services/MailHosting|mail hosting service]]. | prerequisite = | account = global-reg | ipv6 = true | security_notes = Access to the mail services are fully secured, and to your data, nevertheless most mail exchange on the Internet are not. MX DNS records are protected with DNSSEC and we publish a MTA-STS policy as well as DANE/TLSA records to use secure connections as much as possible. Complete security can be achieved using signed and encrypted mails (see [[wikipedia:Pretty_Good_Privacy|OpenPGP]] and [[wikipedia:S/MIME|S/MIME]]) }} == Access == === Using a Mail Reader === You can retrieve your mails, in case of a real mailbox, using either: * IMAP+TLS (TCP 143) / IMAPS (TCP 993) on imap.duckcorp.org * or POP3+TLS (TCP 110) / POP3S (TCP 995) on pop.duckcorp.org The IMAP protocol is recommended over POP3, as it provides many interesting features. If you want to download all your mails absolutely at home, loosing the ability to read your mail from anywhere on the planet, you can do that with IMAP too (look at your mail client settings). You can use our servers to send mails out too via smtp.duckcorp.org using: * SUBMISSION (TCP 587) which is the recommended way and has less chance to be filtered, or alternatively SMTP+TLS (TCP 25) / SMTPS (TCP 465) * and SASL authentication === Using a Web Interface === A [https://webmail.duckcorp.org/ webmail interface] is available. ==== Securing Your Account ==== We strongly suggest you enable [https://en.wikipedia.org/wiki/Multi-factor_authentication Two Factor Authentication (2FA)] to protect your account. With this system your login and password is not sufficient to log in, an external secret is needed. Currently only one method is available: * TOTP: using an application on your phone (FreeOTP available on [https://f-droid.org/ F-Droid] is working fine) In the ''settings'' menu click on the ''2-Factor Authentication'' tab and follow these steps: * click on the ''Setup all fields (needs Save)'' button * on your phone, open the TOPT application and scan the QR code * on your phone generate a code, put it in the ''Check code'' text field and click on the button to validate it works fine * click on the ''show recovery codes'' button and store them is a safe place: print then (or store then on an encrypted disk) * click the ''Save'' button, you will be logged out * check you can login again ==== Mail Encryption and Signing ==== It is possible to encrypt and sign your emails via PGP. In the past is was possible to upload your key on the server but there is a more secure method now: with [https://www.mailvelope.com/ Mailvelope] you can use your key on your machine without exposing your secrets. The company behind Mailvelope proposes various plans but you don't need to subscribe or pay for anything, just install the Free Software plugin for your browser. == Antivirus and Antispam == Mails stored on our server are checked upon arrival for viruses and SPAMs. Outgoing mails from our services are checked too. Mails being viruses are suppressed automatically upon arrival. Mails with a huge probability of being SPAM are destroyed too. Good mails and possibly spammy mails are delivered to your mailbox. SPAMs are more difficult to detect, and it is an error-prone process, so we chose to use a learning software instead of using a global database. After a few weeks of teaching it is able to recognize most of your habits and block a lot of annoying SPAM. === Probable SPAM Notification === Mails are delivered normally with a special field added (''X-Spam-Status'') to your mail headers (not always visible depending on your mail client and its configuration) indicating if the mail is a SPAM and its ''spamminess'' score. This is quite handy if you prefer SPAMs arranged in a specific folder. You may use then the provided [[#Mail Filtering |filtering system]] to sort them properly, or configure your eMail client. === Retraining === Teaching the system what is SPAM and HAM (non-SPAM) is called ''retraining''. If you have of create a folder named ''Junk'', then it is automatically magic: * if you move mail into it, it is automatically retrained as SPAM * if you move mail out of it, it is automatically retrained as HAM * with time, certain old mails automatically expire, see below If you are using an IMAP Sync client which does not support the MOVE operation (isync, offlineimap…) then you unfortunately cannot use this method, please look at the next chapter. To use this folder properly, SPAMs '''must''' be delivered in the ''Junk'' folder automatically, so you can move them out in case of error. You just need to subscribe to this folder in your mail software (this folder is always auto-created). It is not recommended to use your mail software for this filtering, this is horribly inefficient and you would have to set things up on each device and manually synchronize your settings. Automatic expiration logic, based on delivery time (and not the mail timestamp): * deleted mails are purged after 1 day * read mails without an important flag are purge after 7 days * unread mails without an important flag are purge after 30 days If you use the ''incoming_spam'' [[#Global_Rules|global rule]], then SPAMs newly discovered by the system are flagged as important, which means these mails will never by purged until you review it and decide to delete them or mark them as not important. Custom rules might play with this flag and achieve an automatic selection. === Retraining for feature-limited IMAP Sync clients === If your client does not support the MOVE operation (isync, [https://github.com/OfflineIMAP/offlineimap/issues/515 offlineimap]…) then you can only copy (APPEND) mail, which does not work with the magic Junk folder. In this case, you can create special folders called ''SyncSPAM'' and ''SyncHAM'' and copy SPAM and HAM in them. Every two hours a script will pickup these mails, do the retraining, and remove them. Removing these mails from their original locations will be left to you though. == Mail Filtering == With your favourite mail client, you can probably filter your mails in proper folders already. Nevertheless, this can be an annoying operation: * blocking you mail client for a long time if you have to process plenty of mails * downloading each mail information, and sometimes content (depending on your filters), is lenghty too, and cost much bandwidth * syncing filters across your machines (home desktop, laptop, office machine…) is a pain in the ass * processing only when you're online prevents triggering actions in a timely manner (automatic redirect, vacation messages…), and running a machine 24/7 with a mail client polling new mails every 30s is not a solution We provide a much better way to do this using the [[wikipedia:Sieve_(mail_filtering_language)|SIEVE]] filters. Shortly, SIEVE is a language dedicated to expressing mail filters (also called ''rules''). Our server is able to process your mails according to these filters as soon as they arrive. You then don't have to care about them anymore, and may use light mail clients or webmails when you're not on your machine with your favourite software. === Rules Configuration === You can express sort/reject/vacation/… filters using these rules, as the capabilities are very rich. Several softwares support managing SIEVE rules: * Icedove/Thunderbird: *: using the SIEVE extension (in ''xul-ext-sieve'' Debian package), it provides a rules editor (for power-users) * Roundcube: *: coupled with the sieverules extension, provides an easy to use web interface *: this webmail has been made available [https://webmail.duckcorp.org/ here] * sieve-connect: *: provides a CLI to upload/download/activate your rules files *: this tool is available on [[Services/Shell|shell hosts]] (tell us if you know more software supporting this feature) To push your filters on the server, a dedicated protocol exists: MANAGESIEVE (TCP 4190) on ''sieve.duckcorp.org''. Our webmails are already configured to use it, but it you use sieve-connect from our hosts or your own mail software, you'll need these parameters. You can read more info about SIEVE here: * supported SIEVE features on our server: https://pigeonhole.dovecot.org/ * http://sieve.info/ === Global Rules === Global rules are provided to ease configuration on specific filters. They can easily be included in your own configuration. Available rules: * ''incoming_spam'': *: SPAMs will automatically be delivered in the ''Junk'' folder and marked as ''important'' If you write your own custom rules, here is an example on how to use one of them: require ["include"]; include :global "&lt;rule-name&gt;"; === Default Rules === The default settings (since 2112-02-11) are to use the global ''incoming_spam'' rule (see below), in order to provide a simple default configuration for most users. All other mails will end-up in your ''Inbox'' folder and you may then sort them by yourself. If you create your own rules, the default rules won't apply anymore, so power-users can replace the default behavior completely to achieve what they really need. If you want to use the default behavior you can use: require ["include"]; include :global "incoming_spam"; You can also take advantage of the antispam spaminess score to use a different threshold like this: require ["fileinto", "spamtestplus", "relational", "comparator-i;ascii-numeric"]; # if SPAM score is >37% then move into the junk box if spamtest :percent :value "gt" :comparator "i;ascii-numeric" "37" { fileinto "Junk"; stop; } == Fetching eMails from an External Mailbox == {{warning}} This is not supported anymore; you may still redirect mails from your external mailbox to your DuckCorp's email address though. == Shared/Public Folders == {{warning}} This is unfortunately not supported by the synchronization system between our two main mail servers; it was not used anyway. Private (non-shared) namespaces are possible though. You may need to share mails or messages with friends or people you do stuff with (in a project or association). Depending on your needs, two solutions are possible:</del> * share some of your own private folders, thus called ''shared folders'' * manage a special folder hierarchy, called ''public folders'' (even if they may not be accessible to everyone) *: if you need one, ask an administrator; the namespace name can be freely chosen but must be unambiguous and is subject to approval === Namespaces === Through IMAP, or our webmails internally using IMAP, it is possible to partition the folder hierarchy into ''namespaces''. Traditionally you are using the root namespace for your private folders. Additional namespaces can be created and will appear among your own folders or separate, depending on your mail client's choice of representation. To avoid name clashes, we decided to prefix all additional namespace names with a '''#'''. Since 2011-05-14, the following extra namespaces are created and reserved: * #Shared, containing all folders other users decided to share with you * #MilkyPond, containing public MP/DC informational mailboxes you may subscribe at will === Folders Permissions === Using IMAP, it is possible to setup rights (read only, write allowed…) to your own folders in order to share them with other users, or group of users. Public folders are owned by no-one, and must be created by the administrators. Once your request is accepted we will delegate its administration to your care. It can then can be managed like shared folders. === Software Support === Client mail softwares support: * RoundCube: *: support namespaces, shared and public folders configurable via ''Settings->Folders'', selecting a folder then using the ''Sharing'' tab * Icedove/Thunderbird: *: support namespaces, shared and public folders configurable via folder selection and ''Tools->Imap-ACL'' menu action Most other softwares have namespace support only, so you should be able to use shared/public folders you have rights on but not configure them yourself (tell us if you know more software supporting this feature). == Limitations == === Maximum Mail Size === Mail you send or receive are limited to '''20MB'''. If you need to transmit much bigger data, then a mail transport is not appropriate, you'd better use a file sharing method instead. === Quotas === Even if it would be nice to live without it, we had to establish quotas to force people sort their mails out once in a while and delete useless things instead of leaving an ever-growing mess behind. The default quota is '''512MB''' which is not that big but should match needs of most users. This said, you may ask us for more and there's no reason we would refuse a reasonable demand. == Technical Details == This service is made using: * [https://www.clamav.net/ ClamAV] * [https://dovecot.org/ Dovecot] * [https://www.postfix.org/ Postfix] * [https://github.com/Snawoot/postfix-mta-sts-resolver postfix-mta-sts-resolver] * [https://www.roundcube.net/ RoundCube] * [https://rspamd.com/ Rspamd] * [https://projects.duckcorp.org/projects/spoolinger Spoolinger] c44b3af5fd0bfee1d7809f329862b47a2f7fa849 0 55 812 767 2020-04-08T05:25:25Z Duck 2 wikitext text/x-wiki {{Template:Service | description = [[wikipedia:Irc|IRC]] (Internet Relay Chat) is a chat system. We have our own internal network, formerly used to contact administrators and discuss with other users. Even is not advertise widely, external people may join the network, so you can invite your friend. | prerequisite = | account = | ipv6 = true | security_notes = Your messages are secured if you connect using the secure port(s), but you need to ensure the recipient uses a secure connection too ; this can be achieved using chanmode +S (see below). {{warning}} Unfortunately, due to a bug in the software (see {{dc-projects|233}}), the link between our servers is not yet fully secured, but you can work around this problem if you talk only to people connected to the same server as yourself. }} == Access == === Using an IRC Software === To connect you need and IRC client, like for example: * [https://www.pidgin.im Pidgin] * [https://weechat.org/ WeeChat] You need to configure these parameters: * host: irc.milkypond.org * port: ** 6680 (if you want a secure connection using SSL/TLS) ** 6667 or 6669 (because 6667 is sometimes filtered) No password is needed to connect. === Using a Web Interface === Use the following URL: https://irconweb.milkypond.org/ == Official Channels == * #MilkyPond: main channel used to meet with other users and friends and ask general questions * #DuckCorp: contact with DuckCorp Administrators and technical discussions == Contacting IRC Administrators == In case of problems on IRC you can find connected administrators using this command (mind the idle time): /QUOTE STATS P Beware IRC Administrators may not be DuckCorp Administrators. == Features == === Commands === You can see available commands using this command: /QUOTE HELP You can get help about a particular command using this command: /QUOTE HELP &lt;command&gt; ==== Additional Commands for IRC Administrators ==== All special commands are listed in the Oper MOTD. === User Modes === You can see available channel modes using this command: /QUOTE HELP UMODE ==== Mode +g ==== (partial quote from the ircd-ratbox documentation) When a client is set +g, that user will be in "Caller ID" mode. Any user that messages a +g client will receive a notice saying that they are in +g (server side ignore) mode. The target client (who is set +g) will also receive a notice saying that so and so messaged them, and that they are in +g mode. The target of the message will only receive one notification per minute, from any client, in order to help prevent flooding. The sender will '''not''' have the rate limit, and will receive a notice saying the target is in +g mode every time they send a message. Note that this behavior is similar to the way AWAY messages are done. There are numerous benefits for both opers and regular users, including the ability to stop spambot messages from ever reaching your client, stopping private message and CTCP floods, and being able to sit on IRC in privacy. One question that arises is how to message specific users, while blocking out everyone else. The command ACCEPT is your answer. To add a user to your accept list, issue the raw command: /QUOTE ACCEPT &lt;nick&gt;,&lt;nick&gt;,&lt;nick&gt;,… That user will now be able to send messages to your client until the association is broken. Associations break in one of the following situations: when an accepted user QUIT's (or is on the other side of a split), you QUIT, or the accepted user changes their nick. The reason why a remote user's nick change will remove them from your accept list is so that you cannot track a user after they changed their nick. Viewing the accept list is also very easy. Issue the raw command: /QUOTE ACCEPT * Removing a user from your accept list is also simple. Issue the command: /QUOTE ACCEPT -&lt;nick&gt; === Channel Modes === You can see available channel modes using this command: /QUOTE HELP CHMODE These extra modes are also available: * +R - registered - Users must be registered with services to JOIN * +z - ssl only - Requires SSL/TLS connections to join === IRC Services === To help not loose your favorite nick or channel, the IRC Services can register them so you're still in control. It also helps manage channel with a variety of tools. Look at the user introduction manual in the documentation below. List of Services: * ALIS: search available channels * USERSERV: register an account * INFOSERV: read operator news (not in use in this network, we send global announces and post to the mailing-list) * STATSERV: few network information (not that useful) List of Services available with an account (see USERSERV): * NICKSERV: register nicknames * GROUPSERV: manage group of users used in ACLs * CHANSERV: register and manage channels * MEMOSERV: send and receive memos from other registered users To get help on each service commands, use the following command: /QUOTE &lt;service&gt; HELP ==== Additional Services for IRC Administrators ==== (exact privileges depends on trust and delegation) * OPERSERV: superadmin commands * GLOBAL: messaging all users === Secure Service Authentication (CERTFP) === You can authenticate to your service account using a password, but it is more secure to use a certificate and not too complicated to setup. The Freenode network has a good [https://freenode.net/kb/answer/certfp documentation for this feature]. == Documentation == * [http://docs.ratbox.org/svc_userintro.shtml IRC Services Introduction] == Technical Details == This service is made using: * [https://www.inspircd.org/ InspIRCd] * [https://atheme.github.io/atheme.html Atheme IRC Services] * [https://thelounge.github.io/ The Lounge] (Web UI) 71b69cbc83449e0a518cfd86f4c40494a1eb6165 826 812 2020-04-08T06:21:51Z Duck 2 wikitext text/x-wiki {{Template:Service | description = [[wikipedia:Irc|IRC]] (Internet Relay Chat) is a chat system. We have our own internal network, formerly used to contact administrators and discuss with other users. Even is not advertise widely, external people may join the network, so you can invite your friend. | prerequisite = | account = | ipv6 = true | security_notes = Your messages are secured if you connect using the secure port(s), but you need to ensure the recipient uses a secure connection too ; this can be achieved using chanmode +z (see below). }} == Access == === Using an IRC Software === To connect you need and IRC client, like for example: * [https://www.pidgin.im Pidgin] * [https://weechat.org/ WeeChat] You need to configure these parameters: * host: irc.milkypond.org * port: ** 6680 (if you want a secure connection using SSL/TLS, recommended) ** 6667 or 6669 (because 6667 is sometimes filtered) No password is needed to connect. === Using a Web Interface === Use the following URL: https://irconweb.milkypond.org/ == Official Channels == * #MilkyPond: main channel used to meet with other users and friends and ask general questions * #DuckCorp: contact with DuckCorp Administrators and technical discussions == Contacting IRC Administrators == In case of problems on IRC you can find connected administrators using this command (mind the idle time): /QUOTE STATS P Beware IRC Administrators may not be DuckCorp Administrators. == Features == === Commands === You can see available commands using this command: /QUOTE HELP You can get help about a particular command using this command: /QUOTE HELP &lt;command&gt; The list of commands is also [https://docs.inspircd.org/2/commands/ documented here]. ==== Additional Commands for IRC Administrators ==== All special commands are listed in the Oper MOTD. === User Modes === You can see available user modes using this command: /QUOTE HELP UMODES ==== Filtering Unwanted Messages ==== We try to ban spam and nasty people from our network but if we're not fast enough (sleeping…) you might want to take action into your own hands. With the "Caller ID" mode (user mode +g) a user can define an access list. With this mode you will be notified when someone not in your accept list is trying to contact you, but at a reasonable rate. The person trying to contact you will get notified their messaqe has been blocked. You can use the '''ACCEPT''' command to define your accept list. To add someone to your list: /QUOTE ACCEPT &lt;nick&gt;,&lt;nick&gt;,&lt;nick&gt;,… That user will now be able to send messages to your client until the association is broken. Associations break in one of the following situations: when an accepted user QUIT's (or is on the other side of a split), you QUIT, or the accepted user changes their nick. The reason why a remote user's nick change will remove them from your accept list is so that you cannot track a user after they changed their nick. You can view you accept list at any time: /QUOTE ACCEPT * Removing a user from your accept list can be done with this command: /QUOTE ACCEPT -&lt;nick&gt; === Channel Modes === You can see available channel modes using this command: /QUOTE HELP CHMODES These extra modes are also available: * +R - registered - Users must be registered with services to JOIN * +z - ssl only - Requires SSL/TLS connections to join === IRC Services === To help not loose your favorite nick or channel, the IRC Services can register them so you're still in control. It also helps manage channel with a variety of tools. Look at the user introduction manual in the documentation below. List of Services: * ALIS: search available channels * USERSERV: register an account * INFOSERV: read operator news (not in use in this network, we send global announces and post to the mailing-list) * STATSERV: few network information (not that useful) List of Services available with an account (see USERSERV): * NICKSERV: register nicknames * GROUPSERV: manage group of users used in ACLs * CHANSERV: register and manage channels * MEMOSERV: send and receive memos from other registered users To get help on each service commands, use the following command: /QUOTE &lt;service&gt; HELP === Secure Service Authentication (CERTFP) === You can authenticate to your service account using a password, but it is more secure to use a certificate and not too complicated to setup. The Freenode network has a good [https://freenode.net/kb/answer/certfp documentation for this feature]. ==== Additional Services for IRC Administrators ==== (exact privileges depends on trust and delegation) * OPERSERV: superadmin commands * GLOBAL: messaging all users == Technical Details == This service is made using: * [https://www.inspircd.org/ InspIRCd] * [https://atheme.github.io/atheme.html Atheme IRC Services] * [https://thelounge.github.io/ The Lounge] (Web UI) f4fd14c37a84db397910cc1df4a5c8b0285ed540 841 826 2020-04-08T11:46:57Z Duck 2 /* Official Channels */ wikitext text/x-wiki {{Template:Service | description = [[wikipedia:Irc|IRC]] (Internet Relay Chat) is a chat system. We have our own internal network, formerly used to contact administrators and discuss with other users. Even is not advertise widely, external people may join the network, so you can invite your friend. | prerequisite = | account = | ipv6 = true | security_notes = Your messages are secured if you connect using the secure port(s), but you need to ensure the recipient uses a secure connection too ; this can be achieved using chanmode +z (see below). }} == Access == === Using an IRC Software === To connect you need and IRC client, like for example: * [https://www.pidgin.im Pidgin] * [https://weechat.org/ WeeChat] You need to configure these parameters: * host: irc.milkypond.org * port: ** 6680 (if you want a secure connection using SSL/TLS, recommended) ** 6667 or 6669 (because 6667 is sometimes filtered) No password is needed to connect. === Using a Web Interface === Use the following URL: https://irconweb.milkypond.org/ == Official Channels == * '''#MilkyPond''': main channel used to meet with other users and friends and ask general questions * '''#DuckCorp''': contact with DuckCorp Administrators and technical discussions == Contacting IRC Administrators == In case of problems on IRC you can find connected administrators using this command (mind the idle time): /QUOTE STATS P Beware IRC Administrators may not be DuckCorp Administrators. == Features == === Commands === You can see available commands using this command: /QUOTE HELP You can get help about a particular command using this command: /QUOTE HELP &lt;command&gt; The list of commands is also [https://docs.inspircd.org/2/commands/ documented here]. ==== Additional Commands for IRC Administrators ==== All special commands are listed in the Oper MOTD. === User Modes === You can see available user modes using this command: /QUOTE HELP UMODES ==== Filtering Unwanted Messages ==== We try to ban spam and nasty people from our network but if we're not fast enough (sleeping…) you might want to take action into your own hands. With the "Caller ID" mode (user mode +g) a user can define an access list. With this mode you will be notified when someone not in your accept list is trying to contact you, but at a reasonable rate. The person trying to contact you will get notified their messaqe has been blocked. You can use the '''ACCEPT''' command to define your accept list. To add someone to your list: /QUOTE ACCEPT &lt;nick&gt;,&lt;nick&gt;,&lt;nick&gt;,… That user will now be able to send messages to your client until the association is broken. Associations break in one of the following situations: when an accepted user QUIT's (or is on the other side of a split), you QUIT, or the accepted user changes their nick. The reason why a remote user's nick change will remove them from your accept list is so that you cannot track a user after they changed their nick. You can view you accept list at any time: /QUOTE ACCEPT * Removing a user from your accept list can be done with this command: /QUOTE ACCEPT -&lt;nick&gt; === Channel Modes === You can see available channel modes using this command: /QUOTE HELP CHMODES These extra modes are also available: * +R - registered - Users must be registered with services to JOIN * +z - ssl only - Requires SSL/TLS connections to join === IRC Services === To help not loose your favorite nick or channel, the IRC Services can register them so you're still in control. It also helps manage channel with a variety of tools. Look at the user introduction manual in the documentation below. List of Services: * ALIS: search available channels * USERSERV: register an account * INFOSERV: read operator news (not in use in this network, we send global announces and post to the mailing-list) * STATSERV: few network information (not that useful) List of Services available with an account (see USERSERV): * NICKSERV: register nicknames * GROUPSERV: manage group of users used in ACLs * CHANSERV: register and manage channels * MEMOSERV: send and receive memos from other registered users To get help on each service commands, use the following command: /QUOTE &lt;service&gt; HELP === Secure Service Authentication (CERTFP) === You can authenticate to your service account using a password, but it is more secure to use a certificate and not too complicated to setup. The Freenode network has a good [https://freenode.net/kb/answer/certfp documentation for this feature]. ==== Additional Services for IRC Administrators ==== (exact privileges depends on trust and delegation) * OPERSERV: superadmin commands * GLOBAL: messaging all users == Technical Details == This service is made using: * [https://www.inspircd.org/ InspIRCd] * [https://atheme.github.io/atheme.html Atheme IRC Services] * [https://thelounge.github.io/ The Lounge] (Web UI) ad83e7c52f5b12c4be751ca6797c2ca465ad24a4 851 841 2021-01-20T11:59:19Z Duck 2 /* Using an IRC Software */ wikitext text/x-wiki {{Template:Service | description = [[wikipedia:Irc|IRC]] (Internet Relay Chat) is a chat system. We have our own internal network, formerly used to contact administrators and discuss with other users. Even is not advertise widely, external people may join the network, so you can invite your friend. | prerequisite = | account = | ipv6 = true | security_notes = Your messages are secured if you connect using the secure port(s), but you need to ensure the recipient uses a secure connection too ; this can be achieved using chanmode +z (see below). }} == Access == === Using an IRC Software === To connect you need and IRC client, like for example: * [https://www.pidgin.im Pidgin] * [https://weechat.org/ WeeChat] If you have problems seeing the modes then you probably need to upgrade your client to [https://docs.inspircd.org/faq/#why-does-my-client-not-show-mode-changesopped-users-on-joinetc-correctly-when-using-inspircd-v3 fix bugs parsing the protocol]. You need to configure these parameters: * host: irc.milkypond.org * port: ** 6680 ('''secure connection''' using SSL/TLS, recommended) ** 6667 or 6669 (because 6667 is sometimes filtered) No password is needed to connect but you may pass your Service Account password and it will be passed to NickServ automagically. === Using a Web Interface === Use the following URL: https://irconweb.milkypond.org/ == Official Channels == * '''#MilkyPond''': main channel used to meet with other users and friends and ask general questions * '''#DuckCorp''': contact with DuckCorp Administrators and technical discussions == Contacting IRC Administrators == In case of problems on IRC you can find connected administrators using this command (mind the idle time): /QUOTE STATS P Beware IRC Administrators may not be DuckCorp Administrators. == Features == === Commands === You can see available commands using this command: /QUOTE HELP You can get help about a particular command using this command: /QUOTE HELP &lt;command&gt; The list of commands is also [https://docs.inspircd.org/2/commands/ documented here]. ==== Additional Commands for IRC Administrators ==== All special commands are listed in the Oper MOTD. === User Modes === You can see available user modes using this command: /QUOTE HELP UMODES ==== Filtering Unwanted Messages ==== We try to ban spam and nasty people from our network but if we're not fast enough (sleeping…) you might want to take action into your own hands. With the "Caller ID" mode (user mode +g) a user can define an access list. With this mode you will be notified when someone not in your accept list is trying to contact you, but at a reasonable rate. The person trying to contact you will get notified their messaqe has been blocked. You can use the '''ACCEPT''' command to define your accept list. To add someone to your list: /QUOTE ACCEPT &lt;nick&gt;,&lt;nick&gt;,&lt;nick&gt;,… That user will now be able to send messages to your client until the association is broken. Associations break in one of the following situations: when an accepted user QUIT's (or is on the other side of a split), you QUIT, or the accepted user changes their nick. The reason why a remote user's nick change will remove them from your accept list is so that you cannot track a user after they changed their nick. You can view you accept list at any time: /QUOTE ACCEPT * Removing a user from your accept list can be done with this command: /QUOTE ACCEPT -&lt;nick&gt; === Channel Modes === You can see available channel modes using this command: /QUOTE HELP CHMODES These extra modes are also available: * +R - registered - Users must be registered with services to JOIN * +z - ssl only - Requires SSL/TLS connections to join === IRC Services === To help not loose your favorite nick or channel, the IRC Services can register them so you're still in control. It also helps manage channel with a variety of tools. Look at the user introduction manual in the documentation below. List of Services: * ALIS: search available channels * USERSERV: register an account * INFOSERV: read operator news (not in use in this network, we send global announces and post to the mailing-list) * STATSERV: few network information (not that useful) List of Services available with an account (see USERSERV): * NICKSERV: register nicknames * GROUPSERV: manage group of users used in ACLs * CHANSERV: register and manage channels * MEMOSERV: send and receive memos from other registered users To get help on each service commands, use the following command: /QUOTE &lt;service&gt; HELP === Secure Service Authentication (CERTFP) === You can authenticate to your service account using a password, but it is more secure to use a certificate and not too complicated to setup. The Freenode network has a good [https://freenode.net/kb/answer/certfp documentation for this feature]. ==== Additional Services for IRC Administrators ==== (exact privileges depends on trust and delegation) * OPERSERV: superadmin commands * GLOBAL: messaging all users == Technical Details == This service is made using: * [https://www.inspircd.org/ InspIRCd] * [https://atheme.github.io/atheme.html Atheme IRC Services] * [https://thelounge.github.io/ The Lounge] (Web UI) 33178e360ac62144512026b4c2700df5da570f03 852 851 2021-01-20T12:03:04Z Duck 2 /* Using an IRC Software */ wikitext text/x-wiki {{Template:Service | description = [[wikipedia:Irc|IRC]] (Internet Relay Chat) is a chat system. We have our own internal network, formerly used to contact administrators and discuss with other users. Even is not advertise widely, external people may join the network, so you can invite your friend. | prerequisite = | account = | ipv6 = true | security_notes = Your messages are secured if you connect using the secure port(s), but you need to ensure the recipient uses a secure connection too ; this can be achieved using chanmode +z (see below). }} == Access == === Using an IRC Software === To connect you need and IRC client, like for example: * [https://www.pidgin.im Pidgin] * [https://weechat.org/ WeeChat] If you have problems seeing the modes then you probably need to upgrade your client to [https://docs.inspircd.org/faq/#why-does-my-client-not-show-mode-changesopped-users-on-joinetc-correctly-when-using-inspircd-v3 fix bugs parsing the protocol]. You need to configure these parameters: * host: irc.milkypond.org * port: ** 6680 ('''secure connection''' using SSL/TLS, recommended) ** 6667 or 6669 (because 6667 is sometimes filtered) No password is needed to connect but you may pass your Service Account password and it will be passed to NickServ automagically. The recommended and most secure method is to create a certificate and authenticate with CertFP (see below). === Using a Web Interface === Use the following URL: https://irconweb.milkypond.org/ == Official Channels == * '''#MilkyPond''': main channel used to meet with other users and friends and ask general questions * '''#DuckCorp''': contact with DuckCorp Administrators and technical discussions == Contacting IRC Administrators == In case of problems on IRC you can find connected administrators using this command (mind the idle time): /QUOTE STATS P Beware IRC Administrators may not be DuckCorp Administrators. == Features == === Commands === You can see available commands using this command: /QUOTE HELP You can get help about a particular command using this command: /QUOTE HELP &lt;command&gt; The list of commands is also [https://docs.inspircd.org/2/commands/ documented here]. ==== Additional Commands for IRC Administrators ==== All special commands are listed in the Oper MOTD. === User Modes === You can see available user modes using this command: /QUOTE HELP UMODES ==== Filtering Unwanted Messages ==== We try to ban spam and nasty people from our network but if we're not fast enough (sleeping…) you might want to take action into your own hands. With the "Caller ID" mode (user mode +g) a user can define an access list. With this mode you will be notified when someone not in your accept list is trying to contact you, but at a reasonable rate. The person trying to contact you will get notified their messaqe has been blocked. You can use the '''ACCEPT''' command to define your accept list. To add someone to your list: /QUOTE ACCEPT &lt;nick&gt;,&lt;nick&gt;,&lt;nick&gt;,… That user will now be able to send messages to your client until the association is broken. Associations break in one of the following situations: when an accepted user QUIT's (or is on the other side of a split), you QUIT, or the accepted user changes their nick. The reason why a remote user's nick change will remove them from your accept list is so that you cannot track a user after they changed their nick. You can view you accept list at any time: /QUOTE ACCEPT * Removing a user from your accept list can be done with this command: /QUOTE ACCEPT -&lt;nick&gt; === Channel Modes === You can see available channel modes using this command: /QUOTE HELP CHMODES These extra modes are also available: * +R - registered - Users must be registered with services to JOIN * +z - ssl only - Requires SSL/TLS connections to join === IRC Services === To help not loose your favorite nick or channel, the IRC Services can register them so you're still in control. It also helps manage channel with a variety of tools. Look at the user introduction manual in the documentation below. List of Services: * ALIS: search available channels * USERSERV: register an account * INFOSERV: read operator news (not in use in this network, we send global announces and post to the mailing-list) * STATSERV: few network information (not that useful) List of Services available with an account (see USERSERV): * NICKSERV: register nicknames * GROUPSERV: manage group of users used in ACLs * CHANSERV: register and manage channels * MEMOSERV: send and receive memos from other registered users To get help on each service commands, use the following command: /QUOTE &lt;service&gt; HELP === Secure Service Authentication (CERTFP) === You can authenticate to your service account using a password, but it is more secure to use a certificate and not too complicated to setup. The Freenode network has a good [https://freenode.net/kb/answer/certfp documentation for this feature]. ==== Additional Services for IRC Administrators ==== (exact privileges depends on trust and delegation) * OPERSERV: superadmin commands * GLOBAL: messaging all users == Technical Details == This service is made using: * [https://www.inspircd.org/ InspIRCd] * [https://atheme.github.io/atheme.html Atheme IRC Services] * [https://thelounge.github.io/ The Lounge] (Web UI) cd9f2316152be6209bb69f963c6a299cfe103905 853 852 2021-01-20T12:04:36Z Duck 2 /* Using an IRC Software */ wikitext text/x-wiki {{Template:Service | description = [[wikipedia:Irc|IRC]] (Internet Relay Chat) is a chat system. We have our own internal network, formerly used to contact administrators and discuss with other users. Even is not advertise widely, external people may join the network, so you can invite your friend. | prerequisite = | account = | ipv6 = true | security_notes = Your messages are secured if you connect using the secure port(s), but you need to ensure the recipient uses a secure connection too ; this can be achieved using chanmode +z (see below). }} == Access == === Using an IRC Software === To connect you need and IRC client, like for example: * [https://www.pidgin.im Pidgin] * [https://weechat.org/ WeeChat] If you have problems seeing the modes then you probably need to upgrade your client to [https://docs.inspircd.org/faq/#why-does-my-client-not-show-mode-changesopped-users-on-joinetc-correctly-when-using-inspircd-v3 fix bugs parsing the protocol]. You need to configure these parameters: * host: irc.milkypond.org * port: ** 6680 ('''secure connection''' using SSL/TLS, recommended) ** 6667 or 6669 (because 6667 is sometimes filtered) No password is needed to connect but you may pass your Service Account password and it will be passed to NickServ automagically. The recommended and most secure configuration is: * TLS connection on port 6680 * create a certificate and authenticate with CertFP (see below) * create a service account and associate your certificate with your account === Using a Web Interface === Use the following URL: https://irconweb.milkypond.org/ == Official Channels == * '''#MilkyPond''': main channel used to meet with other users and friends and ask general questions * '''#DuckCorp''': contact with DuckCorp Administrators and technical discussions == Contacting IRC Administrators == In case of problems on IRC you can find connected administrators using this command (mind the idle time): /QUOTE STATS P Beware IRC Administrators may not be DuckCorp Administrators. == Features == === Commands === You can see available commands using this command: /QUOTE HELP You can get help about a particular command using this command: /QUOTE HELP &lt;command&gt; The list of commands is also [https://docs.inspircd.org/2/commands/ documented here]. ==== Additional Commands for IRC Administrators ==== All special commands are listed in the Oper MOTD. === User Modes === You can see available user modes using this command: /QUOTE HELP UMODES ==== Filtering Unwanted Messages ==== We try to ban spam and nasty people from our network but if we're not fast enough (sleeping…) you might want to take action into your own hands. With the "Caller ID" mode (user mode +g) a user can define an access list. With this mode you will be notified when someone not in your accept list is trying to contact you, but at a reasonable rate. The person trying to contact you will get notified their messaqe has been blocked. You can use the '''ACCEPT''' command to define your accept list. To add someone to your list: /QUOTE ACCEPT &lt;nick&gt;,&lt;nick&gt;,&lt;nick&gt;,… That user will now be able to send messages to your client until the association is broken. Associations break in one of the following situations: when an accepted user QUIT's (or is on the other side of a split), you QUIT, or the accepted user changes their nick. The reason why a remote user's nick change will remove them from your accept list is so that you cannot track a user after they changed their nick. You can view you accept list at any time: /QUOTE ACCEPT * Removing a user from your accept list can be done with this command: /QUOTE ACCEPT -&lt;nick&gt; === Channel Modes === You can see available channel modes using this command: /QUOTE HELP CHMODES These extra modes are also available: * +R - registered - Users must be registered with services to JOIN * +z - ssl only - Requires SSL/TLS connections to join === IRC Services === To help not loose your favorite nick or channel, the IRC Services can register them so you're still in control. It also helps manage channel with a variety of tools. Look at the user introduction manual in the documentation below. List of Services: * ALIS: search available channels * USERSERV: register an account * INFOSERV: read operator news (not in use in this network, we send global announces and post to the mailing-list) * STATSERV: few network information (not that useful) List of Services available with an account (see USERSERV): * NICKSERV: register nicknames * GROUPSERV: manage group of users used in ACLs * CHANSERV: register and manage channels * MEMOSERV: send and receive memos from other registered users To get help on each service commands, use the following command: /QUOTE &lt;service&gt; HELP === Secure Service Authentication (CERTFP) === You can authenticate to your service account using a password, but it is more secure to use a certificate and not too complicated to setup. The Freenode network has a good [https://freenode.net/kb/answer/certfp documentation for this feature]. ==== Additional Services for IRC Administrators ==== (exact privileges depends on trust and delegation) * OPERSERV: superadmin commands * GLOBAL: messaging all users == Technical Details == This service is made using: * [https://www.inspircd.org/ InspIRCd] * [https://atheme.github.io/atheme.html Atheme IRC Services] * [https://thelounge.github.io/ The Lounge] (Web UI) e78c619c3be1e9ba747831b4b8bc51c900fe62fb 854 853 2021-01-20T12:07:33Z Duck 2 /* Secure Service Authentication (CERTFP) */ wikitext text/x-wiki {{Template:Service | description = [[wikipedia:Irc|IRC]] (Internet Relay Chat) is a chat system. We have our own internal network, formerly used to contact administrators and discuss with other users. Even is not advertise widely, external people may join the network, so you can invite your friend. | prerequisite = | account = | ipv6 = true | security_notes = Your messages are secured if you connect using the secure port(s), but you need to ensure the recipient uses a secure connection too ; this can be achieved using chanmode +z (see below). }} == Access == === Using an IRC Software === To connect you need and IRC client, like for example: * [https://www.pidgin.im Pidgin] * [https://weechat.org/ WeeChat] If you have problems seeing the modes then you probably need to upgrade your client to [https://docs.inspircd.org/faq/#why-does-my-client-not-show-mode-changesopped-users-on-joinetc-correctly-when-using-inspircd-v3 fix bugs parsing the protocol]. You need to configure these parameters: * host: irc.milkypond.org * port: ** 6680 ('''secure connection''' using SSL/TLS, recommended) ** 6667 or 6669 (because 6667 is sometimes filtered) No password is needed to connect but you may pass your Service Account password and it will be passed to NickServ automagically. The recommended and most secure configuration is: * TLS connection on port 6680 * create a certificate and authenticate with CertFP (see below) * create a service account and associate your certificate with your account === Using a Web Interface === Use the following URL: https://irconweb.milkypond.org/ == Official Channels == * '''#MilkyPond''': main channel used to meet with other users and friends and ask general questions * '''#DuckCorp''': contact with DuckCorp Administrators and technical discussions == Contacting IRC Administrators == In case of problems on IRC you can find connected administrators using this command (mind the idle time): /QUOTE STATS P Beware IRC Administrators may not be DuckCorp Administrators. == Features == === Commands === You can see available commands using this command: /QUOTE HELP You can get help about a particular command using this command: /QUOTE HELP &lt;command&gt; The list of commands is also [https://docs.inspircd.org/2/commands/ documented here]. ==== Additional Commands for IRC Administrators ==== All special commands are listed in the Oper MOTD. === User Modes === You can see available user modes using this command: /QUOTE HELP UMODES ==== Filtering Unwanted Messages ==== We try to ban spam and nasty people from our network but if we're not fast enough (sleeping…) you might want to take action into your own hands. With the "Caller ID" mode (user mode +g) a user can define an access list. With this mode you will be notified when someone not in your accept list is trying to contact you, but at a reasonable rate. The person trying to contact you will get notified their messaqe has been blocked. You can use the '''ACCEPT''' command to define your accept list. To add someone to your list: /QUOTE ACCEPT &lt;nick&gt;,&lt;nick&gt;,&lt;nick&gt;,… That user will now be able to send messages to your client until the association is broken. Associations break in one of the following situations: when an accepted user QUIT's (or is on the other side of a split), you QUIT, or the accepted user changes their nick. The reason why a remote user's nick change will remove them from your accept list is so that you cannot track a user after they changed their nick. You can view you accept list at any time: /QUOTE ACCEPT * Removing a user from your accept list can be done with this command: /QUOTE ACCEPT -&lt;nick&gt; === Channel Modes === You can see available channel modes using this command: /QUOTE HELP CHMODES These extra modes are also available: * +R - registered - Users must be registered with services to JOIN * +z - ssl only - Requires SSL/TLS connections to join === IRC Services === To help not loose your favorite nick or channel, the IRC Services can register them so you're still in control. It also helps manage channel with a variety of tools. Look at the user introduction manual in the documentation below. List of Services: * ALIS: search available channels * USERSERV: register an account * INFOSERV: read operator news (not in use in this network, we send global announces and post to the mailing-list) * STATSERV: few network information (not that useful) List of Services available with an account (see USERSERV): * NICKSERV: register nicknames * GROUPSERV: manage group of users used in ACLs * CHANSERV: register and manage channels * MEMOSERV: send and receive memos from other registered users To get help on each service commands, use the following command: /QUOTE &lt;service&gt; HELP ==== Secure Service Authentication (CERTFP) ==== You can authenticate to your service account using a password, but it is more secure to use a certificate and not too complicated to setup. The Freenode network has a good [https://freenode.net/kb/answer/certfp documentation for this feature]. Don't forget to select the SASL/EXTERNAL authentication method and use TLS. ==== Additional Services for IRC Administrators ==== (exact privileges depends on trust and delegation) * OPERSERV: superadmin commands * GLOBAL: messaging all users == Technical Details == This service is made using: * [https://www.inspircd.org/ InspIRCd] * [https://atheme.github.io/atheme.html Atheme IRC Services] * [https://thelounge.github.io/ The Lounge] (Web UI) 8fb1ef882a223369ae52e0d1314e58a6476ec66e 855 854 2021-01-20T12:18:28Z Duck 2 /* IRC Services */ wikitext text/x-wiki {{Template:Service | description = [[wikipedia:Irc|IRC]] (Internet Relay Chat) is a chat system. We have our own internal network, formerly used to contact administrators and discuss with other users. Even is not advertise widely, external people may join the network, so you can invite your friend. | prerequisite = | account = | ipv6 = true | security_notes = Your messages are secured if you connect using the secure port(s), but you need to ensure the recipient uses a secure connection too ; this can be achieved using chanmode +z (see below). }} == Access == === Using an IRC Software === To connect you need and IRC client, like for example: * [https://www.pidgin.im Pidgin] * [https://weechat.org/ WeeChat] If you have problems seeing the modes then you probably need to upgrade your client to [https://docs.inspircd.org/faq/#why-does-my-client-not-show-mode-changesopped-users-on-joinetc-correctly-when-using-inspircd-v3 fix bugs parsing the protocol]. You need to configure these parameters: * host: irc.milkypond.org * port: ** 6680 ('''secure connection''' using SSL/TLS, recommended) ** 6667 or 6669 (because 6667 is sometimes filtered) No password is needed to connect but you may pass your Service Account password and it will be passed to NickServ automagically. The recommended and most secure configuration is: * TLS connection on port 6680 * create a certificate and authenticate with CertFP (see below) * create a service account and associate your certificate with your account === Using a Web Interface === Use the following URL: https://irconweb.milkypond.org/ == Official Channels == * '''#MilkyPond''': main channel used to meet with other users and friends and ask general questions * '''#DuckCorp''': contact with DuckCorp Administrators and technical discussions == Contacting IRC Administrators == In case of problems on IRC you can find connected administrators using this command (mind the idle time): /QUOTE STATS P Beware IRC Administrators may not be DuckCorp Administrators. == Features == === Commands === You can see available commands using this command: /QUOTE HELP You can get help about a particular command using this command: /QUOTE HELP &lt;command&gt; The list of commands is also [https://docs.inspircd.org/2/commands/ documented here]. ==== Additional Commands for IRC Administrators ==== All special commands are listed in the Oper MOTD. === User Modes === You can see available user modes using this command: /QUOTE HELP UMODES ==== Filtering Unwanted Messages ==== We try to ban spam and nasty people from our network but if we're not fast enough (sleeping…) you might want to take action into your own hands. With the "Caller ID" mode (user mode +g) a user can define an access list. With this mode you will be notified when someone not in your accept list is trying to contact you, but at a reasonable rate. The person trying to contact you will get notified their messaqe has been blocked. You can use the '''ACCEPT''' command to define your accept list. To add someone to your list: /QUOTE ACCEPT &lt;nick&gt;,&lt;nick&gt;,&lt;nick&gt;,… That user will now be able to send messages to your client until the association is broken. Associations break in one of the following situations: when an accepted user QUIT's (or is on the other side of a split), you QUIT, or the accepted user changes their nick. The reason why a remote user's nick change will remove them from your accept list is so that you cannot track a user after they changed their nick. You can view you accept list at any time: /QUOTE ACCEPT * Removing a user from your accept list can be done with this command: /QUOTE ACCEPT -&lt;nick&gt; === Channel Modes === You can see available channel modes using this command: /QUOTE HELP CHMODES These extra modes are also available: * +R - registered - Users must be registered with services to JOIN * +z - ssl only - Requires SSL/TLS connections to join === IRC Services === To help not loose your favorite nick or channel, the IRC Services can register them so you're still in control. It also helps manage channel with a variety of tools. Look at the user introduction manual in the documentation below. List of Services: * ALIS: search available channels * USERSERV: register an account * INFOSERV: read operator news (not in use in this network, we send global announces and post to the mailing-list) * STATSERV: few network information (not that useful) List of Services available with an account (see USERSERV): * NICKSERV: register nicknames * GROUPSERV: manage group of users used in ACLs * CHANSERV: register and manage channels * MEMOSERV: send and receive memos from other registered users To get help on each service commands, use the following command: /QUOTE &lt;service&gt; HELP ==== Register an Account ==== To create an account first register it: /QUOTE nickserv register <password> <email> Then check your emails and use the provided verification command that should look like this: /QUOTE nickserv verify register <nick> <code> Your account will not be valid until verified. If you change your email address you will need to revalidate it using the same process. ==== Secure Service Authentication (CERTFP) ==== You can authenticate to your service account using a password, but it is more secure to use a certificate and not too complicated to setup. The Freenode network has a good [https://freenode.net/kb/answer/certfp documentation for this feature]. Don't forget to select the SASL/EXTERNAL authentication method and use TLS. The commands to associate your certificate to your account are the same as on Freenode: * get your fingerprint with: /whois <mynick> * add the fingerprint to your account (you need to have registered and account and by logged in): /QUOTE nickserv cert add <fpr> ==== Additional Services for IRC Administrators ==== (exact privileges depends on trust and delegation) * OPERSERV: superadmin commands * GLOBAL: messaging all users == Technical Details == This service is made using: * [https://www.inspircd.org/ InspIRCd] * [https://atheme.github.io/atheme.html Atheme IRC Services] * [https://thelounge.github.io/ The Lounge] (Web UI) 22709a3733ba5d4e97d02c92a8261e155a35f724 856 855 2021-01-20T12:22:22Z Duck 2 /* IRC Services */ wikitext text/x-wiki {{Template:Service | description = [[wikipedia:Irc|IRC]] (Internet Relay Chat) is a chat system. We have our own internal network, formerly used to contact administrators and discuss with other users. Even is not advertise widely, external people may join the network, so you can invite your friend. | prerequisite = | account = | ipv6 = true | security_notes = Your messages are secured if you connect using the secure port(s), but you need to ensure the recipient uses a secure connection too ; this can be achieved using chanmode +z (see below). }} == Access == === Using an IRC Software === To connect you need and IRC client, like for example: * [https://www.pidgin.im Pidgin] * [https://weechat.org/ WeeChat] If you have problems seeing the modes then you probably need to upgrade your client to [https://docs.inspircd.org/faq/#why-does-my-client-not-show-mode-changesopped-users-on-joinetc-correctly-when-using-inspircd-v3 fix bugs parsing the protocol]. You need to configure these parameters: * host: irc.milkypond.org * port: ** 6680 ('''secure connection''' using SSL/TLS, recommended) ** 6667 or 6669 (because 6667 is sometimes filtered) No password is needed to connect but you may pass your Service Account password and it will be passed to NickServ automagically. The recommended and most secure configuration is: * TLS connection on port 6680 * create a certificate and authenticate with CertFP (see below) * create a service account and associate your certificate with your account === Using a Web Interface === Use the following URL: https://irconweb.milkypond.org/ == Official Channels == * '''#MilkyPond''': main channel used to meet with other users and friends and ask general questions * '''#DuckCorp''': contact with DuckCorp Administrators and technical discussions == Contacting IRC Administrators == In case of problems on IRC you can find connected administrators using this command (mind the idle time): /QUOTE STATS P Beware IRC Administrators may not be DuckCorp Administrators. == Features == === Commands === You can see available commands using this command: /QUOTE HELP You can get help about a particular command using this command: /QUOTE HELP &lt;command&gt; The list of commands is also [https://docs.inspircd.org/2/commands/ documented here]. ==== Additional Commands for IRC Administrators ==== All special commands are listed in the Oper MOTD. === User Modes === You can see available user modes using this command: /QUOTE HELP UMODES ==== Filtering Unwanted Messages ==== We try to ban spam and nasty people from our network but if we're not fast enough (sleeping…) you might want to take action into your own hands. With the "Caller ID" mode (user mode +g) a user can define an access list. With this mode you will be notified when someone not in your accept list is trying to contact you, but at a reasonable rate. The person trying to contact you will get notified their messaqe has been blocked. You can use the '''ACCEPT''' command to define your accept list. To add someone to your list: /QUOTE ACCEPT &lt;nick&gt;,&lt;nick&gt;,&lt;nick&gt;,… That user will now be able to send messages to your client until the association is broken. Associations break in one of the following situations: when an accepted user QUIT's (or is on the other side of a split), you QUIT, or the accepted user changes their nick. The reason why a remote user's nick change will remove them from your accept list is so that you cannot track a user after they changed their nick. You can view you accept list at any time: /QUOTE ACCEPT * Removing a user from your accept list can be done with this command: /QUOTE ACCEPT -&lt;nick&gt; === Channel Modes === You can see available channel modes using this command: /QUOTE HELP CHMODES These extra modes are also available: * +R - registered - Users must be registered with services to JOIN * +z - ssl only - Requires SSL/TLS connections to join === IRC Services === To help not loose your favorite nick or channel, the IRC Services can register them so you're still in control. It also helps manage channel with a variety of tools. Look at the user introduction manual in the documentation below. List of Services: * ALIS: search available channels * USERSERV: register an account * INFOSERV: read operator news (not in use in this network, we send global announces and post to the mailing-list) * STATSERV: few network information (not that useful) List of Services available with an account (see USERSERV): * NICKSERV: register nicknames * GROUPSERV: manage group of users used in ACLs * CHANSERV: register and manage channels * MEMOSERV: send and receive memos from other registered users To get help on each service commands, use the following command: /QUOTE &lt;service&gt; HELP ==== Register an Account ==== To create an account first register it: /QUOTE nickserv register &lt;password&gt; &lt;email&gt; Then check your emails and use the provided verification command that should look like this: /QUOTE nickserv verify register &lt;nick&gt; &lt;code&gt; Your account will not be valid until verified. If you change your email address you will need to revalidate it using the same process. ==== Secure Service Authentication (CERTFP) ==== You can authenticate to your service account using a password, but it is more secure to use a certificate and not too complicated to setup. The Freenode network has a good [https://freenode.net/kb/answer/certfp documentation for this feature]. Don't forget to select the SASL/EXTERNAL authentication method and use TLS. The commands to associate your certificate to your account are the same as on Freenode: * get your fingerprint with: /whois &lt;mynick&gt; * add the fingerprint to your account (you need to have registered and account and by logged in): /QUOTE nickserv cert add &lt;fpr&gt; ==== Additional Services for IRC Administrators ==== (exact privileges depends on trust and delegation) * OPERSERV: superadmin commands * GLOBAL: messaging all users == Technical Details == This service is made using: * [https://www.inspircd.org/ InspIRCd] * [https://atheme.github.io/atheme.html Atheme IRC Services] * [https://thelounge.github.io/ The Lounge] (Web UI) 06fae3c02d0460465b497dee3fabd97bac83c2b1 857 856 2021-01-20T12:23:42Z Duck 2 /* Contacting IRC Administrators */ wikitext text/x-wiki {{Template:Service | description = [[wikipedia:Irc|IRC]] (Internet Relay Chat) is a chat system. We have our own internal network, formerly used to contact administrators and discuss with other users. Even is not advertise widely, external people may join the network, so you can invite your friend. | prerequisite = | account = | ipv6 = true | security_notes = Your messages are secured if you connect using the secure port(s), but you need to ensure the recipient uses a secure connection too ; this can be achieved using chanmode +z (see below). }} == Access == === Using an IRC Software === To connect you need and IRC client, like for example: * [https://www.pidgin.im Pidgin] * [https://weechat.org/ WeeChat] If you have problems seeing the modes then you probably need to upgrade your client to [https://docs.inspircd.org/faq/#why-does-my-client-not-show-mode-changesopped-users-on-joinetc-correctly-when-using-inspircd-v3 fix bugs parsing the protocol]. You need to configure these parameters: * host: irc.milkypond.org * port: ** 6680 ('''secure connection''' using SSL/TLS, recommended) ** 6667 or 6669 (because 6667 is sometimes filtered) No password is needed to connect but you may pass your Service Account password and it will be passed to NickServ automagically. The recommended and most secure configuration is: * TLS connection on port 6680 * create a certificate and authenticate with CertFP (see below) * create a service account and associate your certificate with your account === Using a Web Interface === Use the following URL: https://irconweb.milkypond.org/ == Official Channels == * '''#MilkyPond''': main channel used to meet with other users and friends and ask general questions * '''#DuckCorp''': contact with DuckCorp Administrators and technical discussions == Contacting IRC Administrators == In case of problems on IRC you can find connected administrators using this command (mind the idle time): /QUOTE STATS P == Features == === Commands === You can see available commands using this command: /QUOTE HELP You can get help about a particular command using this command: /QUOTE HELP &lt;command&gt; The list of commands is also [https://docs.inspircd.org/2/commands/ documented here]. ==== Additional Commands for IRC Administrators ==== All special commands are listed in the Oper MOTD. === User Modes === You can see available user modes using this command: /QUOTE HELP UMODES ==== Filtering Unwanted Messages ==== We try to ban spam and nasty people from our network but if we're not fast enough (sleeping…) you might want to take action into your own hands. With the "Caller ID" mode (user mode +g) a user can define an access list. With this mode you will be notified when someone not in your accept list is trying to contact you, but at a reasonable rate. The person trying to contact you will get notified their messaqe has been blocked. You can use the '''ACCEPT''' command to define your accept list. To add someone to your list: /QUOTE ACCEPT &lt;nick&gt;,&lt;nick&gt;,&lt;nick&gt;,… That user will now be able to send messages to your client until the association is broken. Associations break in one of the following situations: when an accepted user QUIT's (or is on the other side of a split), you QUIT, or the accepted user changes their nick. The reason why a remote user's nick change will remove them from your accept list is so that you cannot track a user after they changed their nick. You can view you accept list at any time: /QUOTE ACCEPT * Removing a user from your accept list can be done with this command: /QUOTE ACCEPT -&lt;nick&gt; === Channel Modes === You can see available channel modes using this command: /QUOTE HELP CHMODES These extra modes are also available: * +R - registered - Users must be registered with services to JOIN * +z - ssl only - Requires SSL/TLS connections to join === IRC Services === To help not loose your favorite nick or channel, the IRC Services can register them so you're still in control. It also helps manage channel with a variety of tools. Look at the user introduction manual in the documentation below. List of Services: * ALIS: search available channels * USERSERV: register an account * INFOSERV: read operator news (not in use in this network, we send global announces and post to the mailing-list) * STATSERV: few network information (not that useful) List of Services available with an account (see USERSERV): * NICKSERV: register nicknames * GROUPSERV: manage group of users used in ACLs * CHANSERV: register and manage channels * MEMOSERV: send and receive memos from other registered users To get help on each service commands, use the following command: /QUOTE &lt;service&gt; HELP ==== Register an Account ==== To create an account first register it: /QUOTE nickserv register &lt;password&gt; &lt;email&gt; Then check your emails and use the provided verification command that should look like this: /QUOTE nickserv verify register &lt;nick&gt; &lt;code&gt; Your account will not be valid until verified. If you change your email address you will need to revalidate it using the same process. ==== Secure Service Authentication (CERTFP) ==== You can authenticate to your service account using a password, but it is more secure to use a certificate and not too complicated to setup. The Freenode network has a good [https://freenode.net/kb/answer/certfp documentation for this feature]. Don't forget to select the SASL/EXTERNAL authentication method and use TLS. The commands to associate your certificate to your account are the same as on Freenode: * get your fingerprint with: /whois &lt;mynick&gt; * add the fingerprint to your account (you need to have registered and account and by logged in): /QUOTE nickserv cert add &lt;fpr&gt; ==== Additional Services for IRC Administrators ==== (exact privileges depends on trust and delegation) * OPERSERV: superadmin commands * GLOBAL: messaging all users == Technical Details == This service is made using: * [https://www.inspircd.org/ InspIRCd] * [https://atheme.github.io/atheme.html Atheme IRC Services] * [https://thelounge.github.io/ The Lounge] (Web UI) e6523183fc17a34237204289d23bc8bbe03dd03d 858 857 2021-01-20T12:24:43Z Duck 2 /* Channel Modes */ wikitext text/x-wiki {{Template:Service | description = [[wikipedia:Irc|IRC]] (Internet Relay Chat) is a chat system. We have our own internal network, formerly used to contact administrators and discuss with other users. Even is not advertise widely, external people may join the network, so you can invite your friend. | prerequisite = | account = | ipv6 = true | security_notes = Your messages are secured if you connect using the secure port(s), but you need to ensure the recipient uses a secure connection too ; this can be achieved using chanmode +z (see below). }} == Access == === Using an IRC Software === To connect you need and IRC client, like for example: * [https://www.pidgin.im Pidgin] * [https://weechat.org/ WeeChat] If you have problems seeing the modes then you probably need to upgrade your client to [https://docs.inspircd.org/faq/#why-does-my-client-not-show-mode-changesopped-users-on-joinetc-correctly-when-using-inspircd-v3 fix bugs parsing the protocol]. You need to configure these parameters: * host: irc.milkypond.org * port: ** 6680 ('''secure connection''' using SSL/TLS, recommended) ** 6667 or 6669 (because 6667 is sometimes filtered) No password is needed to connect but you may pass your Service Account password and it will be passed to NickServ automagically. The recommended and most secure configuration is: * TLS connection on port 6680 * create a certificate and authenticate with CertFP (see below) * create a service account and associate your certificate with your account === Using a Web Interface === Use the following URL: https://irconweb.milkypond.org/ == Official Channels == * '''#MilkyPond''': main channel used to meet with other users and friends and ask general questions * '''#DuckCorp''': contact with DuckCorp Administrators and technical discussions == Contacting IRC Administrators == In case of problems on IRC you can find connected administrators using this command (mind the idle time): /QUOTE STATS P == Features == === Commands === You can see available commands using this command: /QUOTE HELP You can get help about a particular command using this command: /QUOTE HELP &lt;command&gt; The list of commands is also [https://docs.inspircd.org/2/commands/ documented here]. ==== Additional Commands for IRC Administrators ==== All special commands are listed in the Oper MOTD. === User Modes === You can see available user modes using this command: /QUOTE HELP UMODES ==== Filtering Unwanted Messages ==== We try to ban spam and nasty people from our network but if we're not fast enough (sleeping…) you might want to take action into your own hands. With the "Caller ID" mode (user mode +g) a user can define an access list. With this mode you will be notified when someone not in your accept list is trying to contact you, but at a reasonable rate. The person trying to contact you will get notified their messaqe has been blocked. You can use the '''ACCEPT''' command to define your accept list. To add someone to your list: /QUOTE ACCEPT &lt;nick&gt;,&lt;nick&gt;,&lt;nick&gt;,… That user will now be able to send messages to your client until the association is broken. Associations break in one of the following situations: when an accepted user QUIT's (or is on the other side of a split), you QUIT, or the accepted user changes their nick. The reason why a remote user's nick change will remove them from your accept list is so that you cannot track a user after they changed their nick. You can view you accept list at any time: /QUOTE ACCEPT * Removing a user from your accept list can be done with this command: /QUOTE ACCEPT -&lt;nick&gt; === Channel Modes === You can see available channel modes using this command: /QUOTE HELP CHMODES === IRC Services === To help not loose your favorite nick or channel, the IRC Services can register them so you're still in control. It also helps manage channel with a variety of tools. Look at the user introduction manual in the documentation below. List of Services: * ALIS: search available channels * USERSERV: register an account * INFOSERV: read operator news (not in use in this network, we send global announces and post to the mailing-list) * STATSERV: few network information (not that useful) List of Services available with an account (see USERSERV): * NICKSERV: register nicknames * GROUPSERV: manage group of users used in ACLs * CHANSERV: register and manage channels * MEMOSERV: send and receive memos from other registered users To get help on each service commands, use the following command: /QUOTE &lt;service&gt; HELP ==== Register an Account ==== To create an account first register it: /QUOTE nickserv register &lt;password&gt; &lt;email&gt; Then check your emails and use the provided verification command that should look like this: /QUOTE nickserv verify register &lt;nick&gt; &lt;code&gt; Your account will not be valid until verified. If you change your email address you will need to revalidate it using the same process. ==== Secure Service Authentication (CERTFP) ==== You can authenticate to your service account using a password, but it is more secure to use a certificate and not too complicated to setup. The Freenode network has a good [https://freenode.net/kb/answer/certfp documentation for this feature]. Don't forget to select the SASL/EXTERNAL authentication method and use TLS. The commands to associate your certificate to your account are the same as on Freenode: * get your fingerprint with: /whois &lt;mynick&gt; * add the fingerprint to your account (you need to have registered and account and by logged in): /QUOTE nickserv cert add &lt;fpr&gt; ==== Additional Services for IRC Administrators ==== (exact privileges depends on trust and delegation) * OPERSERV: superadmin commands * GLOBAL: messaging all users == Technical Details == This service is made using: * [https://www.inspircd.org/ InspIRCd] * [https://atheme.github.io/atheme.html Atheme IRC Services] * [https://thelounge.github.io/ The Lounge] (Web UI) 167150aafc111d96287093f5bac5e4d03881fd9d 859 858 2021-03-16T11:31:05Z Duck 2 TLS is now compulsory wikitext text/x-wiki {{Template:Service | description = [[wikipedia:Irc|IRC]] (Internet Relay Chat) is a chat system. We have our own internal network, formerly used to contact administrators and discuss with other users. Even is not advertise widely, external people may join the network, so you can invite your friend. | prerequisite = | account = | ipv6 = true | security_notes = This service is secure. Users' identity is not guarantied though, but you can trust a service account once validated using another secure channel. }} == Access == === Using an IRC Software === To connect you need and IRC client, like for example: * [https://www.pidgin.im Pidgin] * [https://weechat.org/ WeeChat] If you have problems seeing the modes then you probably need to upgrade your client to [https://docs.inspircd.org/faq/#why-does-my-client-not-show-mode-changesopped-users-on-joinetc-correctly-when-using-inspircd-v3 fix bugs parsing the protocol]. You need to configure these parameters: * host: irc.milkypond.org * port: 6667, 6669 or 6680 (because 6667 is sometimes filtered) * tls: enabled (compulsory since 2021-03-16) No password is needed to connect but you may pass your Service Account password and it will be passed to NickServ automagically. The recommended and most secure configuration is: * create a certificate and authenticate with CertFP (see below) * create a service account and associate your certificate with your account === Using a Web Interface === Use the following URL: https://irconweb.milkypond.org/ == Official Channels == * '''#MilkyPond''': main channel used to meet with other users and friends and ask general questions * '''#DuckCorp''': contact with DuckCorp Administrators and technical discussions == Contacting IRC Administrators == In case of problems on IRC you can find connected administrators using this command (mind the idle time): /QUOTE STATS P == Features == === Commands === You can see available commands using this command: /QUOTE HELP You can get help about a particular command using this command: /QUOTE HELP &lt;command&gt; The list of commands is also [https://docs.inspircd.org/2/commands/ documented here]. ==== Additional Commands for IRC Administrators ==== All special commands are listed in the Oper MOTD. === User Modes === You can see available user modes using this command: /QUOTE HELP UMODES ==== Filtering Unwanted Messages ==== We try to ban spam and nasty people from our network but if we're not fast enough (sleeping…) you might want to take action into your own hands. With the "Caller ID" mode (user mode +g) a user can define an access list. With this mode you will be notified when someone not in your accept list is trying to contact you, but at a reasonable rate. The person trying to contact you will get notified their messaqe has been blocked. You can use the '''ACCEPT''' command to define your accept list. To add someone to your list: /QUOTE ACCEPT &lt;nick&gt;,&lt;nick&gt;,&lt;nick&gt;,… That user will now be able to send messages to your client until the association is broken. Associations break in one of the following situations: when an accepted user QUIT's (or is on the other side of a split), you QUIT, or the accepted user changes their nick. The reason why a remote user's nick change will remove them from your accept list is so that you cannot track a user after they changed their nick. You can view you accept list at any time: /QUOTE ACCEPT * Removing a user from your accept list can be done with this command: /QUOTE ACCEPT -&lt;nick&gt; === Channel Modes === You can see available channel modes using this command: /QUOTE HELP CHMODES === IRC Services === To help not loose your favorite nick or channel, the IRC Services can register them so you're still in control. It also helps manage channel with a variety of tools. Look at the user introduction manual in the documentation below. List of Services: * ALIS: search available channels * USERSERV: register an account * INFOSERV: read operator news (not in use in this network, we send global announces and post to the mailing-list) * STATSERV: few network information (not that useful) List of Services available with an account (see USERSERV): * NICKSERV: register nicknames * GROUPSERV: manage group of users used in ACLs * CHANSERV: register and manage channels * MEMOSERV: send and receive memos from other registered users To get help on each service commands, use the following command: /QUOTE &lt;service&gt; HELP ==== Register an Account ==== To create an account first register it: /QUOTE nickserv register &lt;password&gt; &lt;email&gt; Then check your emails and use the provided verification command that should look like this: /QUOTE nickserv verify register &lt;nick&gt; &lt;code&gt; Your account will not be valid until verified. If you change your email address you will need to revalidate it using the same process. ==== Secure Service Authentication (CERTFP) ==== You can authenticate to your service account using a password, but it is more secure to use a certificate and not too complicated to setup. The Freenode network has a good [https://freenode.net/kb/answer/certfp documentation for this feature]. Don't forget to select the SASL/EXTERNAL authentication method and use TLS. The commands to associate your certificate to your account are the same as on Freenode: * get your fingerprint with: /whois &lt;mynick&gt; * add the fingerprint to your account (you need to have registered and account and by logged in): /QUOTE nickserv cert add &lt;fpr&gt; ==== Additional Services for IRC Administrators ==== (exact privileges depends on trust and delegation) * OPERSERV: superadmin commands * GLOBAL: messaging all users == Technical Details == This service is made using: * [https://www.inspircd.org/ InspIRCd] * [https://atheme.github.io/atheme.html Atheme IRC Services] * [https://thelounge.github.io/ The Lounge] (Web UI) 1d8d0664a1f4ae78e83cdd9f745d71931a4dcd14 0 50 813 800 2020-04-08T05:27:37Z Duck 2 wikitext text/x-wiki {{Template:Service | description = Remote [[wikipedia:Shell_(computing)|shell]] to a DuckCorp machine. | prerequisite = You need to ask an administrator for an account, but we need to know you well-enough to ensure you are trustable. This is '''not''' a VIP requirement, but such an access can be very dangerous and we don't know any other way to avoid a disaster, sorry. You also need to provide a RSA/DSA public key (see ''ssh-keygen''). | account = global-reg | ipv6 = true | security_notes = This service is secure. }} == Access == Via SSH with a RSA/ECDSA/ED25519 key on the following hosts: (ED25519 recommended) * thorfinn.duckcorp.org (prefered for lengthy sessions, like screens) * toushirou.duckcorp.org (mostly useful to manage Web/FTP data) Via SSH+[https://mosh.org/ Mosh], with the same hosts and conditions defined above. On Debian you can use the ''mosh'' package to get the client application and do ''mosh &lt;server&gt;''. === Locked behind a firewall === If you are obliged to go through a firewall (at work for eg), you can try a few things to through and end-up on Toushirou (and can bounce on Thorfinn then). First, if you know there is a proxy, or direct access does not work, you may be able to find the firewall host and port in the browser configuration. If there is none, then the proxy may be transparent (hidden) and you can try a direct SSH access using ''portal.duckcorp.org'' on port ''443''. If it does not work, you can try using a tool to wrap SSH through the firewall. From a terminal the ''corkscrew'' (Debian has a package of the same name) tool car be used with the following SSH configuration (in ''~/.ssh/config''): Host portal.duckcorp.org ProxyCommand /usr/bin/corkscrew &lt;proxy-host&gt; &lt;proxy-port&gt; %h %p and connect with: ssh portal.duckcorp.org == Available Resources == The following resources are available and will remain until we advertise a scheduled removal. If you miss something you can send us a request. === Locales === {{warning}} warning for Mosh users: Mosh only supports UTF-8 locales * br_FR.UTF-8 * en_GB.UTF-8 * en_US.UTF-8 * fr_FR.UTF-8 * ja_JP.EUC-JP * ja_JP.UTF-8 === Shells === * dash * bash * zsh * ksh * tcsh === Programs === * aspell (with same support as system locales) * dict * emacs * graphviz * imagemagick * irssi (with plugins and scripts) * latex (full TeXlive on Thorfinn, limited installation on Toushirou) * p7zip * rsync * screen * sieve-connect * unar * unison * vim * w3m * weechat (with plugins and scripts) (and probably a few others we forgot to mention) Additional tools: * [[Services/VCS|VCS tools]] === Weechat Relay via WSS === If you have weechat running in screen/tmux, then maybe you would like to open access to it to connect your phone (the [https://f-droid.org/en/packages/com.ubergeek42.WeechatAndroid/ Weechat for Android app] has been tested with this setup). For security reasons we do not open ports directly but proxy it via WSS. If you would like such a setup, please ask us and we would assign a specific port. Then you can setup your Weechat relay like this: /set relay.network.password &lt;password&gt; /set relay.network.bind_address ::1 /relay add weechat &lt;port&gt; And ask your app to connect to ''static.perso.duckcorp.org/&lt;user&gt;/weechat'' using websocket+TLS and your password. === Spaces === The following spaces are available: * your home * ask an administrator if you need a project-specific space in ''/srv/projects/'' on Toushirou * ask an administrator if you need a space for public VCS repositories on ''vcs.duckcorp.org'' (Toushirou) * ask an administrator if you need a space (personal or project) on the public FTP (private FTP spaces are ***OBSOLETE***) == Technical Details == This service is made using: * [https://www.openssh.com/ OpenSSH] * [https://mosh.org/ Mosh] d8eeacf4b49faf9c7a5fe7b291051872449e2932 0 43 814 336 2020-04-08T05:29:52Z Duck 2 wikitext text/x-wiki {{Template:Service | description = Available services: * full hosting (NS1) on our servers * replication (NS2) on our servers or, at your choice, partner servers (currently via Hivane) | prerequisite = You need to buy a domain from a [[wikipedia:Domain_name_registrar|registrar]] and ask an administrator to configure this service. | account = global-reg | ipv6 = true | security_notes = Your zone content can be secured using DNSSEC, and replication can be secured too using TSIG (see below). }} == Master Zones Administration == To have your master zone modified on our servers, you can: * use our [[UserMagicalInterface]] * ask administrators == DNS Security == To provide as much security as possible, DC supports the following mechanisms. === [[wikipedia:TSIG|TSIG]] === This protocol allows a secure transfer of zones between primary and secondary servers. The DC's DNS servers support TSIG and comminication between them are always secured. The following entities are known to support TSIG and can then securely transfer zones to/from DC: * [https://www.hivane.net/ Hivane] === [[wikipedia:Domain_Name_System_Security_Extensions|DNSSEC]] === ==== What is DNSSEC? ==== This protocol aims at establishing a chain of trust, from the root of the DNS, to ensure response to queries on a zone has not been altered on the way. With the root zone public key, it is possible to validate the replies step by step down to your zone, for example: root public key -> ''.'' zone -> NS for ''org.'' -> ''org.'' zone -> NS for ''milkypond.org.'' -> ''milkypond.org.'' zone -> ''irc.milkypond.org.'' entry. Unfortunately, many DNS providers do not support DNSSEC (Gandi is one of them :-/). In order to help people work on securing their zone, and be ready when their provider is, the [https://www.isc.org/ ISC] created a solution to validate zones using another secure path: by publishing security associations in a special zone (''dlv.isc.org'', called the DLV Registry), which itself can be validated the normal way. This is only a stopgap, but as providers seems not to be in a hurry to do their job, DC decided to use it. ==== How to use it for my zones? ==== DC DNS servers are able to handle the complicated procedure needed to sign a zone for you. You can just modify it the classic way, and have it signed automatically. You just need to ask us to switch the zone to the secure mode. If your provider gladly support DNSSEC, we can provide the necessary information for the chain of trust; if not, we can use the DLV registry. Beware DNS always means propagation delays, so you may have to wait a few days before the switch is completed and your zone fully secured over the whole world. ==== How to test my zone is secured? ==== First, you need a validating DNS server (explanations for ''bind9'' on Debian): * get the root zone public key (using this script for example: [[File:Get dns root zone key.sh]]) * add the key to your configuration (in ''/etc/bind/named.conf''): include "/etc/bind/root.keys"; * add in your global options (''/etc/bind/named.conf.options''): dnssec-enable yes; dnssec-validation yes; * restart bind The DLV Registry public key is already provided in the ''bind9'' package. Then, you can check it with the ''dig'' tool (available in the ''dnsutils'' Debian package): dig +dnssec <zone> Look at the flags: it is secured if you find the ''ad'' flag. If there is the ''aa'' flag instead, then you are interrogating on of the authoritative DNS servers for the zone, it is also secure, but better test it on another server to be sure it is propagated. {{warning}} If you check an entry of your zone which is a CNAME, beware the CNAME is resolved and if the destination name cannot be validated, then your entry won't either. == Documentation == * generic documentation on [[wikipedia:Domain_Name_System|DNS]] == Technical Details == This service is made using: * [https://bind9.net/ Bind9] 5a9f36f85c08d950621be07be78cf4fd8437595f 815 814 2020-04-08T05:35:23Z Duck 2 /* How to test my zone is secured? */ wikitext text/x-wiki {{Template:Service | description = Available services: * full hosting (NS1) on our servers * replication (NS2) on our servers or, at your choice, partner servers (currently via Hivane) | prerequisite = You need to buy a domain from a [[wikipedia:Domain_name_registrar|registrar]] and ask an administrator to configure this service. | account = global-reg | ipv6 = true | security_notes = Your zone content can be secured using DNSSEC, and replication can be secured too using TSIG (see below). }} == Master Zones Administration == To have your master zone modified on our servers, you can: * use our [[UserMagicalInterface]] * ask administrators == DNS Security == To provide as much security as possible, DC supports the following mechanisms. === [[wikipedia:TSIG|TSIG]] === This protocol allows a secure transfer of zones between primary and secondary servers. The DC's DNS servers support TSIG and comminication between them are always secured. The following entities are known to support TSIG and can then securely transfer zones to/from DC: * [https://www.hivane.net/ Hivane] === [[wikipedia:Domain_Name_System_Security_Extensions|DNSSEC]] === ==== What is DNSSEC? ==== This protocol aims at establishing a chain of trust, from the root of the DNS, to ensure response to queries on a zone has not been altered on the way. With the root zone public key, it is possible to validate the replies step by step down to your zone, for example: root public key -> ''.'' zone -> NS for ''org.'' -> ''org.'' zone -> NS for ''milkypond.org.'' -> ''milkypond.org.'' zone -> ''irc.milkypond.org.'' entry. Unfortunately, many DNS providers do not support DNSSEC (Gandi is one of them :-/). In order to help people work on securing their zone, and be ready when their provider is, the [https://www.isc.org/ ISC] created a solution to validate zones using another secure path: by publishing security associations in a special zone (''dlv.isc.org'', called the DLV Registry), which itself can be validated the normal way. This is only a stopgap, but as providers seems not to be in a hurry to do their job, DC decided to use it. ==== How to use it for my zones? ==== DC DNS servers are able to handle the complicated procedure needed to sign a zone for you. You can just modify it the classic way, and have it signed automatically. You just need to ask us to switch the zone to the secure mode. If your provider gladly support DNSSEC, we can provide the necessary information for the chain of trust; if not, we can use the DLV registry. Beware DNS always means propagation delays, so you may have to wait a few days before the switch is completed and your zone fully secured over the whole world. ==== How to test my zone is secured? ==== First, you need a validating DNS server: * [https://nlnetlabs.nl/projects/unbound/about/ Unbound] does this out of the box * [https://bind9.net/ Bind] needs some settings: ** the root zone public key is now installed and configured in all major distributions ** add in your global options (''/etc/bind/named.conf.options''): dnssec-enable yes; dnssec-validation yes; ** restart bind Then, you can check it with the ''dig'' tool (available in the ''dnsutils'' Debian package): dig +dnssec <zone> Look at the flags: it is secured if you find the ''ad'' flag. If there is the ''aa'' flag instead, then you are interrogating on of the authoritative DNS servers for the zone, it is also secure, but better test it on another server to be sure it is propagated. {{warning}} If you check an entry of your zone which is a CNAME, beware the CNAME is resolved and if the destination name cannot be validated, then your entry won't either. == Documentation == * generic documentation on [[wikipedia:Domain_Name_System|DNS]] == Technical Details == This service is made using: * [https://bind9.net/ Bind9] 4a72df5ace3859b24679a28b848881ffda13c7a4 0 178 816 717 2020-04-08T05:38:01Z Duck 2 wikitext text/x-wiki {{Template:Service | description = Packages repository, currently Debian packages only. Provide fixes and backported packages for DuckCorp. Specific sections can be created for users. No prerequisite for read access. | prerequisite = | account = local | ipv6 = true | security_notes = This service is secure. }} == Access == To install packages you can add the following in your '''/etc/apt/sources.list''': deb https://repository.duckcorp.org/debian stretch dc-net At the moment uploading is limited to users having shell access. == Sections == It is configured to allow these sections: * '''dc-net''': packages automatically available to DC machines * '''extra''': other packages for any other use (desktop, various user tools…) == Build for this Repository == To build for this repository you have to care about: * use a proper version numbering: ** '''~<suite>''' for backports ** '''~dc&lt;i&gt;''' / '''+dc&lt;i&gt;''' if there are DC-specific changes (the later can be appended to the backports suffix) * build with or without sources and orig tarball depending if this is your first upload to the DC repo or not ** for a first upload, or NUR, you will most likely use these sbuild options: -s -A --force-orig-source ** for subsequent uploads (except binary only for another architecture) you will most likely use these sbuild options: -A == Upload to this Repository == First, sign with your GPG key (using ''debsign''). You can upload using this <tt>dupload</tt> configuration snippet: # dupload does not support FTP TLS :-/ $cfg{'duckcorp'} = { fqdn => "toushirou.duckcorp.org", method => "scpb", incoming => "/srv/ftp/ftp.duckcorp.org/repository/dc-debian-incoming", # The dinstall on ftp-master sends emails itself dinstall_runs => 1, }; == Technical Details == This service is made using: * [https://wiki.debian.org/DebianRepository/SetupWithReprepro reprepro] 936f49cc2bb61ed47162d96ecc1bb4b47789d213 0 138 817 629 2020-04-08T05:38:45Z Duck 2 wikitext text/x-wiki {{Template:Service | description = SQL Databases, for websites and various applications. | prerequisite = | account = global-reg | ipv6 = true | security_notes = Access to the databases is secure. }} == Access == === Command Line Interface === ==== PostgreSQL ==== You need a client CLI tool to connect to the database. On Debian you can install it easily using: apt-get install postgresql-client You can login to the following nodes: * db-postgresql-1.duckcorp.org To learn how to use this tool, please look at the [https://www.postgresql.org/docs/9.6/static/tutorial-accessdb.html]. ==== MariaDB (MySQL-compatible) ==== You need a client CLI tool to connect to the database. On Debian you can install it easily using: apt-get install mariadb-client (on older systems you can install the _mysql-client_ package instead) You can login to the following nodes: * db-mysql-1.duckcorp.org mysql -u &lt;user&gt; &lt;database&gt; To learn how to use this tool, please look at the [https://mariadb.com/kb/en/library/a-mariadb-primer/ documentation]. === Web SQL Manager === Each database can be accessed and managed using a (simpler) web interface: https://db.duckcorp.org/ == User Accounts == User Accounts are handy to manage your databases. This is handy to prepare and alter schema, repair problems, and do operations the application accounts are not allowed to do. You need to ask an administrator to create your account. ==== PostgreSQL ==== You can connect using your LDAP credentials. ==== MariaDB (MySQL-compatible) ==== You need separate credentials to log into your account. We [https://projects.duckcorp.org/issues/58 plan to add LDAP support]. == Application Accounts & Databases == To ensure security each project of one or more related database will use a specific account to connect. You need to ask an administrator to create application accounts. It is recommended, if the application support it, to restrict the application account permissions on the database; for example to disallow modification of the database schema. These operations are only meant for migrations and maintenance and should be done using your user account, or a dedicated administration application account. == Technical Details == This service is made using: * [https://www.postgresql.org/ PostgreSQL] * [https://mariadb.org/ MariaDB] fc13160eb22d66b6b661d7fe65defef442cec778 833 817 2020-04-08T08:04:19Z Duck 2 wikitext text/x-wiki {{Template:Service | description = SQL Databases, for websites and various applications. | prerequisite = none | account = global-reg | ipv6 = true | security_notes = Access to the databases is secure. }} == Access == === Command Line Interface === ==== PostgreSQL ==== You need a client CLI tool to connect to the database. On Debian you can install it easily using: apt-get install postgresql-client You can login to the following nodes: * db-postgresql-1.duckcorp.org To learn how to use this tool, please look at the [https://www.postgresql.org/docs/9.6/static/tutorial-accessdb.html]. ==== MariaDB (MySQL-compatible) ==== You need a client CLI tool to connect to the database. On Debian you can install it easily using: apt-get install mariadb-client (on older systems you can install the _mysql-client_ package instead) You can login to the following nodes: * db-mysql-1.duckcorp.org mysql -u &lt;user&gt; &lt;database&gt; To learn how to use this tool, please look at the [https://mariadb.com/kb/en/library/a-mariadb-primer/ documentation]. === Web SQL Manager === Each database can be accessed and managed using a (simpler) web interface: https://db.duckcorp.org/ == User Accounts == User Accounts are handy to manage your databases. This is handy to prepare and alter schema, repair problems, and do operations the application accounts are not allowed to do. You need to ask an administrator to create your account. ==== PostgreSQL ==== You can connect using your LDAP credentials. ==== MariaDB (MySQL-compatible) ==== You need separate credentials to log into your account. We [https://projects.duckcorp.org/issues/58 plan to add LDAP support]. == Application Accounts & Databases == To ensure security each project of one or more related database will use a specific account to connect. You need to ask an administrator to create application accounts. It is recommended, if the application support it, to restrict the application account permissions on the database; for example to disallow modification of the database schema. These operations are only meant for migrations and maintenance and should be done using your user account, or a dedicated administration application account. == Technical Details == This service is made using: * [https://www.postgresql.org/ PostgreSQL] * [https://mariadb.org/ MariaDB] 145803313024cb5ea25a61eba1f5ca0ee8100791 834 833 2020-04-08T08:04:41Z Duck 2 wikitext text/x-wiki {{Template:Service | description = SQL Databases, for websites and various applications. | prerequisite = None | account = global-reg | ipv6 = true | security_notes = Access to the databases is secure. }} == Access == === Command Line Interface === ==== PostgreSQL ==== You need a client CLI tool to connect to the database. On Debian you can install it easily using: apt-get install postgresql-client You can login to the following nodes: * db-postgresql-1.duckcorp.org To learn how to use this tool, please look at the [https://www.postgresql.org/docs/9.6/static/tutorial-accessdb.html]. ==== MariaDB (MySQL-compatible) ==== You need a client CLI tool to connect to the database. On Debian you can install it easily using: apt-get install mariadb-client (on older systems you can install the _mysql-client_ package instead) You can login to the following nodes: * db-mysql-1.duckcorp.org mysql -u &lt;user&gt; &lt;database&gt; To learn how to use this tool, please look at the [https://mariadb.com/kb/en/library/a-mariadb-primer/ documentation]. === Web SQL Manager === Each database can be accessed and managed using a (simpler) web interface: https://db.duckcorp.org/ == User Accounts == User Accounts are handy to manage your databases. This is handy to prepare and alter schema, repair problems, and do operations the application accounts are not allowed to do. You need to ask an administrator to create your account. ==== PostgreSQL ==== You can connect using your LDAP credentials. ==== MariaDB (MySQL-compatible) ==== You need separate credentials to log into your account. We [https://projects.duckcorp.org/issues/58 plan to add LDAP support]. == Application Accounts & Databases == To ensure security each project of one or more related database will use a specific account to connect. You need to ask an administrator to create application accounts. It is recommended, if the application support it, to restrict the application account permissions on the database; for example to disallow modification of the database schema. These operations are only meant for migrations and maintenance and should be done using your user account, or a dedicated administration application account. == Technical Details == This service is made using: * [https://www.postgresql.org/ PostgreSQL] * [https://mariadb.org/ MariaDB] 67f47ac77ac780da56710af582d5a70328dfe429 849 834 2020-04-08T12:00:16Z Duck 2 wikitext text/x-wiki {{Template:Service | description = SQL Databases, for websites and various applications. | prerequisite = | account = global-reg | ipv6 = true | security_notes = Access to the databases is secure. }} == Access == === Command Line Interface === ==== PostgreSQL ==== You need a client CLI tool to connect to the database. On Debian you can install it easily using: apt-get install postgresql-client You can login to the following nodes: * db-postgresql-1.duckcorp.org To learn how to use this tool, please look at the [https://www.postgresql.org/docs/9.6/static/tutorial-accessdb.html]. ==== MariaDB (MySQL-compatible) ==== You need a client CLI tool to connect to the database. On Debian you can install it easily using: apt-get install mariadb-client (on older systems you can install the _mysql-client_ package instead) You can login to the following nodes: * db-mysql-1.duckcorp.org mysql -u &lt;user&gt; &lt;database&gt; To learn how to use this tool, please look at the [https://mariadb.com/kb/en/library/a-mariadb-primer/ documentation]. === Web SQL Manager === Each database can be accessed and managed using a (simpler) web interface: https://db.duckcorp.org/ == User Accounts == User Accounts are handy to manage your databases. This is handy to prepare and alter schema, repair problems, and do operations the application accounts are not allowed to do. You need to ask an administrator to create your account. ==== PostgreSQL ==== You can connect using your LDAP credentials. ==== MariaDB (MySQL-compatible) ==== You need separate credentials to log into your account. We [https://projects.duckcorp.org/issues/58 plan to add LDAP support]. == Application Accounts & Databases == To ensure security each project of one or more related database will use a specific account to connect. You need to ask an administrator to create application accounts. It is recommended, if the application support it, to restrict the application account permissions on the database; for example to disallow modification of the database schema. These operations are only meant for migrations and maintenance and should be done using your user account, or a dedicated administration application account. == Technical Details == This service is made using: * [https://www.postgresql.org/ PostgreSQL] * [https://mariadb.org/ MariaDB] 32c9f779dcc6c7ee6d49024767233345e8065985 0 54 818 383 2020-04-08T05:40:06Z Duck 2 wikitext text/x-wiki {{Template:Service | description = A code review software is a tool intended to help improve software quality. It is intended for software developers to help them receive feedback on their patches. | prerequisite = You need to ask an administrator for an account if you want to create or comment on review, but you don't need anything if you just want to watch existing ones. | account = global-reg | ipv6 = true | security_notes = This service is secure. }} == Access == Use the following URL and login: https://codereview.duckcorp.org/ {{warning}} This service is out of order at the moment. 1f0ad6677b617b31641a649732da2754883efe43 0 52 819 331 2020-04-08T05:40:44Z Duck 2 wikitext text/x-wiki {{Template:Service | description = The Media gallery is a website where you can store, enrich, and share your photo and video files. You can organize them in a hierarchy of folders, and setup permissions if you want to restrict access. | prerequisite = | account = local | ipv6 = true | security_notes = This service is secure but beware to properly manage the permissions on your folder. }} == Access == Use this URL in your browser: https://photos.duckcorp.org/ {{warning}} This service is out of order at the moment. b66472b8e6f8dc047b6004f62fef023c477ab6db 0 67 820 430 2020-04-08T05:44:07Z Duck 2 wikitext text/x-wiki {{Template:Service | description = This service is an online dictionary, used both for definitions and translations, providing information from multiple sources | prerequisite = | account = | ipv6 = false | security_notes = There is no big security concern except you can't be sure you're talking to our DICT server (no TLS support). }} == Access == === Web Interface === Use the following URL: https://dico.duckcorp.org/ === Command Line Interface === You need a DICT software to query the dictionary. On Debian you can install it easily using: apt-get install dico or (another compatible software): apt-get install dict With ''dico'' you can query for &lt;word&gt;: dico --host=dict.duckcorp.org &lt;word&gt; or with ''dict'': dict --host=dict.duckcorp.org &lt;word&gt; == Documentation == * generic documentation on [[wikipedia:Dict|DICT]] * [https://puszcza.gnu.org.ua/software/dico/manual/dico.html#dico-client command line syntax for dico] == Technical Details == This service is made using: * [https://puszcza.gnu.org.ua/software/dico/ GNU Dico] * [https://www.djangoproject.com/ Django] 36ca5facb4409501a753ae953bc89a3ae525c216 0 64 821 542 2020-04-08T05:45:01Z Duck 2 wikitext text/x-wiki {{Template:Service | description = This service allows to keep your machine on time, by being synchronized with a remote time server. The later may itself be synchronized with a better time server and so on. The last one (stratum 1) uses an accurate source of time (stratum 0), like an atomic or GPS clock, and distribute it over the Internet. | prerequisite = | account = | ipv6 = true | security_notes = There is no big security concern except you can't be sure you're talking to our NTP server (no DTLS support). }} == Access == === On a personal computer === You need a NTP software to synchronize your machine. On Debian you can install it easily using: apt-get install chrony You then need to edit the configuration file ''/etc/chrony/chrony.conf'' to add this line: server ntp.duckcorp.org iburst prefer And then restart the service: service chrony restart === On a server === You need a NTP software to synchronize your machine. On Debian you can install it easily using: apt-get install ntp You then need to edit the configuration file ''/etc/ntp.conf'' to add this line: server ntp.duckcorp.org iburst prefer And then restart the service: service ntp restart == NTP Pool == Our server is also part of the [https://www.pool.ntp.org/en/ NTP Pool Project]. If you use servers named like ''*.pool.ntp.org'', then you may use our server sometimes. It is often used by vendors and GNU/* distributions. == Documentation == * generic documentation on [[wikipedia:Network_Time_Protocol|NTP]] == Technical Details == This service is made using: * [https://chrony.tuxfamily.org/ Chrony daemon] * [https://www.ntp.org/ NTP daemon] a4e6ceeac3aee48beb65f21e83fb238a57ccb4f3 0 65 822 806 2020-04-08T05:45:58Z Duck 2 wikitext text/x-wiki {{Template:Service | description = News feeds reader through a web interface. | prerequisite = none | account = global | ipv6 = true | security_notes = This service is secure except if you don't check the website certificate properly (like on Android, see below). }} == Access == === Using a Web Browser === You can connect to the web interface using the following URL: https://gossip.duckcorp.org/ === Using the Android Application === You need the official ttrss application, see: https://play.google.com/store/apps/details?id=org.fox.ttrss (at least another unofficial applications exists made by Nils Braden, but it doesn't work well, TLS certificates problems) Unfortunately the application available on [https://f-droid.org/ F-Droid] is Nils' one and does not work. So if you do not have the Google Play Store on your phone (which is recommended for security and privacy), you may fetch this application using the [https://apk-dl.com/ APK Downloader]. To unlock all the features you will need the Google Play Store to be able to pay, sorry. You might ask a friend or have a dirty phone (like an old one for this kind of infrequent uses) to retrieve the APK (hint: '''Apk Extractor''' and '''SD Scanner''' can help you). The special app you need to get and install just once is: https://play.google.com/store/apps/details?id=org.fox.ttrss.key&rdid=org.fox.ttrss.key You need to connect once through your web browser to activate the web API, which is needed by the Android application: look in Preferences -> Advanced -> Enable external API. Then you can configure your application: * URL: https://gossip.duckcorp.org/ * Login/Password * Accept any SSL certificate: '''False''' * HTTP authentication Login/Password: repeat Login/Password === Sharing News === You can share interesting news: * by mail (but there is no link to your address book) * by URL: these ones are public, meaning there is no need to authenticate to use them, so you can give them away to anybody == Technical Details == This service is made using: * [https://tt-rss.org/ Tiny Tiny RSS] df1e76b9d851598f3427c8bf2b45f99609e50fc8 848 822 2020-04-08T11:59:42Z Duck 2 wikitext text/x-wiki {{Template:Service | description = News feeds reader through a web interface. | prerequisite = | account = global | ipv6 = true | security_notes = This service is secure except if you don't check the website certificate properly (like on Android, see below). }} == Access == === Using a Web Browser === You can connect to the web interface using the following URL: https://gossip.duckcorp.org/ === Using the Android Application === You need the official ttrss application, see: https://play.google.com/store/apps/details?id=org.fox.ttrss (at least another unofficial applications exists made by Nils Braden, but it doesn't work well, TLS certificates problems) Unfortunately the application available on [https://f-droid.org/ F-Droid] is Nils' one and does not work. So if you do not have the Google Play Store on your phone (which is recommended for security and privacy), you may fetch this application using the [https://apk-dl.com/ APK Downloader]. To unlock all the features you will need the Google Play Store to be able to pay, sorry. You might ask a friend or have a dirty phone (like an old one for this kind of infrequent uses) to retrieve the APK (hint: '''Apk Extractor''' and '''SD Scanner''' can help you). The special app you need to get and install just once is: https://play.google.com/store/apps/details?id=org.fox.ttrss.key&rdid=org.fox.ttrss.key You need to connect once through your web browser to activate the web API, which is needed by the Android application: look in Preferences -> Advanced -> Enable external API. Then you can configure your application: * URL: https://gossip.duckcorp.org/ * Login/Password * Accept any SSL certificate: '''False''' * HTTP authentication Login/Password: repeat Login/Password === Sharing News === You can share interesting news: * by mail (but there is no link to your address book) * by URL: these ones are public, meaning there is no need to authenticate to use them, so you can give them away to anybody == Technical Details == This service is made using: * [https://tt-rss.org/ Tiny Tiny RSS] 8994e21352137d9bd392cf11b8036d89dd410fbd 0 68 823 795 2020-04-08T05:48:08Z Duck 2 wikitext text/x-wiki {{Template:Service | description = The StuffCloud service is a webservice used to access, sync, and share your personal data. Currently you can: * store your files and share them with people inside and outside DuckCorp (and in-place view/edit of certain extensions directly from the web interface) * manage your contacts * manage your calendars * manage your tasks * manage your notes * manage your web bookmarks (with browser Sync) * backup/restore your SMS * create your own groups (circles) | prerequisite = | account = global | ipv6 = true | security_notes = This service is secure but beware when sharing your data to other people. }} {{warning}} Remember not to use this service to store illegal or non-free data. == Access == === Web Interface === Use this URL in your browser: https://stuff.milkypond.org/ Then you can setup your contacts, calendars, store files… We strongly suggest you enable [https://en.wikipedia.org/wiki/Multi-factor_authentication Two Factor Authentication (2FA)] to protect your account. With this system your login and password is not sufficient to log in, an external secret is needed. Two methods are available in the security tab of your preferences: * TOTP: using an application on your phone (FreeOTP available on F-Droid is working fine) * U2F: an external device like an USB key (Yubikey for example) It is very easy to use TOPT with your phone and the FreeOTP application (available on [https://f-droid.org/ F-Droid]). You [https://docs.nextcloud.com/server/stable/user_manual/user_2fa.html can find here] more detailed explanation on how to set this up. Do not forget to generate and print (or store on an encrypted disk) the recovery code in case your device is lost. Also please note your connected devices (smartphone, tablet…) using StuffCloud to sync contacts/calendars/files/… will not be able to login anymore using login/password, but you can generate tokens which are safer (see below). === WebDAV Interface === You can use the [[wikipedia:WebDAV|WebDAV]] interface to sync your data from a desktop application or you mobile device. Applications can use the main address of the web interface (see above) with your credentials and should be able to discover you data, but sometimes they have limitations and you need to specify a full ugly link ; in this case you can find the link in the interface, either on the resource to access or in your personal settings page. It is not safe to use your login/password to connect your mobile devices, and this does not work with 2FA anyway. Thus we recommend you to [https://docs.nextcloud.com/server/stable/user_manual/session_management.html?highlight=token generate tokens], one for each device so you can easily remove access to a lost or stolen device. ==== Files ==== * Desktop: ** remote drive (synchronous): use XFCE/Gigolo or GNOME/Nautilus ** synchronize (asynchronous): use the [https://nextcloud.com/install/#install-clients sync] utility (no Debian package yet) * Mobile Devices: ** Android: use the [https://nextcloud.com/install/#install-clients NextCloud] app (available on [https://f-droid.org/ F-Droid]) to synchronize files ==== Contacts ==== * Desktop: synchronize with GNOME/Evolution * Mobile Devices: ** Android: the '''DAVdroid''' app (available on [https://f-droid.org/ F-Droid]) works well * Webmail: works nicely with the newest webmail (RoundCube) (see in Settings->Preferences->CardDAV) ==== Calendars ==== * Desktop: synchronize with GNOME/Evolution * Mobile Devices: ** Android: the '''DAVdroid''' app (available on [https://f-droid.org/ F-Droid]) works well * Webmail: should work but it does not seem to parse events properly even if there's no errors (see in Settings->Preferences->Calendar and the Provider field) ==== Tasks ==== It may be provided by your calendar application. * Desktop: ??? * Mobile Devices: ** Android: *** the '''DAVdroid''' app for synchronization and '''OpenTasks''' for UI work well (both available on [https://f-droid.org/ F-Droid]) *** the '''Joplin''' app is a free, open source note taking and to-do application, which can be synchronized with nextcloud using the webdav URL, i.e. https://stuff.milkypond.org/remote.php/webdav/xxx where xxx is the name of the folder where notes will be saved. * Webmail: not supported ==== Notes ==== * Desktop: ??? * Mobile Devices: ** Android: *** the '''Notes''' app (available on [https://f-droid.org/ F-Droid]) works but seem to have some bugs (like duplicate saving, to be investigated) *** the '''Joplin''' app is a free, open source note taking and to-do application, which can be synchronized with nextcloud using the webdav URL, i.e. https://stuff.milkypond.org/remote.php/webdav/xxx where xxx is the name of the folder where notes will be saved. ==== Web Bookmarks ==== * Desktop: ** Firefox: the [https://addons.mozilla.org/en-US/firefox/addon/floccus/ Floccus] app works; it creates a special bookmark in ''Other Bookmarks'' called ''Owncloud'' (I don't think renaming would not break things); the sync happens every 25 minutes, so be patient ** Chromium: the [https://github.com/marcelklehr/floccus/releases/ Floccus] app is untested * Mobile Devices: ** Android: *** the '''Nextcloud Bookmarks''' app (available on [https://f-droid.org/ F-Droid]) works well *** the '''save to Nextcloud Bookmarks''' app (available on [https://f-droid.org/ F-Droid]) is supposed to work but does not seem to connect… == Documentation == * ''NextCloud'' section in the [https://docs.nextcloud.com/ Documentation Page] == Technical Details == This service is made using: * [https://nextcloud.com/ NextCloud] 8f58a82f2f4247f6f03f470281f17084f0395b19 0 76 824 457 2020-04-08T05:52:14Z Duck 2 wikitext text/x-wiki {{Template:Service | description = Available services: * a node on the Jabber network, based on XMPP, the open standard for instant messaging. | prerequisite = None | account = global-reg | ipv6 = true | security_notes = }} == Access == To connect you need and XMPP client, like for example: * [https://www.pidgin.im Pidgin] * [https://weechat.org/ WeeChat] with the jabber plugin You should only need to specify the domain in your preferred software: milkypond.org If you software does not discover all the settings with the domain, then you can enter then manually: * TCP port for client connections: 5222 * Host: jabber.milkypond.org The daemon listens on other TCP ports: * 5269 (server to server connections) * 5280 ([https://en.wikipedia.org/wiki/BOSH BOSH] http) * 5281 ([https://en.wikipedia.org/wiki/BOSH BOSH] https) == Features == MUC (multi-user chat) is available. dfa8659996e5c0a86deb38cf9bbfabd03a527429 830 824 2020-04-08T07:54:16Z Duck 2 wikitext text/x-wiki {{Template:Service | description = A node on the Jabber network, based on XMPP, the open standard for instant messaging. | prerequisite = None | account = global-reg | ipv6 = true | security_notes = }} == Access == To connect you need and XMPP client, like for example: * [https://www.pidgin.im Pidgin] * [https://weechat.org/ WeeChat] with the jabber plugin You should only need to specify the domain in your preferred software: milkypond.org If you software does not discover all the settings with the domain, then you can enter then manually: * TCP port for client connections: 5222 * Host: jabber.milkypond.org The daemon listens on other TCP ports: * 5269 (server to server connections) * 5280 ([https://en.wikipedia.org/wiki/BOSH BOSH] http) * 5281 ([https://en.wikipedia.org/wiki/BOSH BOSH] https) == Features == MUC (multi-user chat) is available. be0c1826b381563e219ba70ea2a51a334ca0a11a 831 830 2020-04-08T08:01:31Z Duck 2 wikitext text/x-wiki {{Template:Service | description = A node on the Jabber network, based on XMPP, the open standard for instant messaging. | prerequisite = None | account = global-reg | ipv6 = true | security_notes = }} == Access == To connect you need and XMPP client, like for example: * [https://www.pidgin.im Pidgin] * [https://weechat.org/ WeeChat] with the jabber plugin You should only need to specify the domain in your preferred software: milkypond.org If you software does not discover all the settings with the domain, then you can enter then manually: * TCP port for client connections: 5222 * Host: jabber.milkypond.org The daemon listens on other TCP ports: * 5269 (server to server connections) * 5280 ([https://en.wikipedia.org/wiki/BOSH BOSH] http) * 5281 ([https://en.wikipedia.org/wiki/BOSH BOSH] https) == Features == MUC (multi-user chat) is available. == Technical Details == This service is made using: * [https://prosody.im/ Prosody] 1602e2433f624f883cfa15a853c247f8afe274fd 832 831 2020-04-08T08:03:54Z Duck 2 wikitext text/x-wiki {{Template:Service | description = A node on the Jabber network, based on XMPP, the open standard for instant messaging. | prerequisite = None | account = global-reg | ipv6 = true | security_notes = This service is secure. }} == Access == To connect you need and XMPP client, like for example: * [https://www.pidgin.im Pidgin] * [https://weechat.org/ WeeChat] with the jabber plugin You should only need to specify the domain in your preferred software: milkypond.org If you software does not discover all the settings with the domain, then you can enter then manually: * TCP port for client connections: 5222 * Host: jabber.milkypond.org The daemon listens on other TCP ports: * 5269 (server to server connections) * 5280 ([https://en.wikipedia.org/wiki/BOSH BOSH] http) * 5281 ([https://en.wikipedia.org/wiki/BOSH BOSH] https) == Features == MUC (multi-user chat) is available. == Technical Details == This service is made using: * [https://prosody.im/ Prosody] d01e7f5e1ee785824e2c79ebc5de0bc0bbf16951 846 832 2020-04-08T11:59:01Z Duck 2 wikitext text/x-wiki {{Template:Service | description = A node on the Jabber network, based on XMPP, the open standard for instant messaging. | prerequisite = | account = global-reg | ipv6 = true | security_notes = This service is secure. }} == Access == To connect you need and XMPP client, like for example: * [https://www.pidgin.im Pidgin] * [https://weechat.org/ WeeChat] with the jabber plugin You should only need to specify the domain in your preferred software: milkypond.org If you software does not discover all the settings with the domain, then you can enter then manually: * TCP port for client connections: 5222 * Host: jabber.milkypond.org The daemon listens on other TCP ports: * 5269 (server to server connections) * 5280 ([https://en.wikipedia.org/wiki/BOSH BOSH] http) * 5281 ([https://en.wikipedia.org/wiki/BOSH BOSH] https) == Features == MUC (multi-user chat) is available. == Technical Details == This service is made using: * [https://prosody.im/ Prosody] d2db876b552da0c4f714e9457a41ed19ac7187e2 0 56 825 330 2020-04-08T05:54:44Z Duck 2 wikitext text/x-wiki {{Template:Service | description = An [[wikipedia:IRC_bouncer#IRC|IRC Bouncer]] is a proxy, relaying connection to one or multiple IRC servers. When you disconnect from the bouncer, the bouncer keep your connections alive and store messages sent to you or in channels you joined. When you are back connected to the bouncer, all your channels and private chats are automatically reopened, and you can access messages you missed. | prerequisite = You need to provide the following information: * default nick / user / realname * an encrypted password generated using the ''bipmkpw'' command (available on Thorfinn, or in the [https://bip.milkypond.org/ Bip] software) * list of networks you wish to connect to * list of channel you want to autojoin (for each network) * an other specific settings you wish | account = local | ipv6 = false | security_notes = Your messages are securely delivered to our server, but the rest of the transport security depends on the network capabilities (see the network list below). }} == Access == To connect you need and IRC client, as the bouncer acts like an IRC server. See the [[Services/IRC#Access|here]] for examples of usable softwares. The bouncer is able to connect to multiple networks, but so as not to mix connections (which may have users and channels of the same name, creating a conflict), you need to connect to the bouncer multiple times, one for each network. You need to configure these parameters for each connection: * host: irc-bouncer.duckcorp.org * port: 7778 * password: &lt;user&gt;:&lt;user-password&gt;:&lt;connection&gt; * activate SSL/TLS &lt;user&gt; is your username, &lt;user-password&gt; your password, and &lt;connection&gt; the name of the network you want to connect to (see the list of available networks below). == Available Networks == These are the available networks you may access, depending on your configuration: * milkypond (secured) * minbif ([[Services/IRC-IM-GW|IRC to IM gateway]], secured) * debianjp * freenode (secured) * oftc (secured) * ircnet * epiknet * gimpnet * rezosup * iie (secured) * n7mm (secured) == Technical Details == This service is made using: * [https://bip.milkypond.org/ Bip] ae26981508478890d0dd99b4401496a193582453 0 39 827 805 2020-04-08T06:22:12Z Duck 2 wikitext text/x-wiki Here is a short overview of the services provided by DuckCorp. Our services are supervised and important data are [[Services/Backup|saved regularly]]. {{warning}} [[Services/Security|Notes about security !]] {| class="wikitable" style="text-align: center; width: 100%;" |+ Available Services |- ! Category !! colspan="2" | Service !! Access !! Status !! Description |- | rowspan="5" | Communication || rowspan="2" | Mail || [[Services/Mail|eMails]] || users || {{status_ok}} || style="text-align: left;" | Mail boxes with anti-spam/anti-virus, filtering…, or mail redirections |- | [[Services/ML|Mailing-Lists]] || users || {{status_ok}} || style="text-align: left;" | Distribution lists for mails |- | rowspan="2" | IRC || [[Services/IRC|IRC Network]] || public || {{status_ok}} || style="text-align: left;" | MilkyPond Chat Network using a dedicated software or a Web-interface |- | [[Services/IRC-Bouncer|IRC Bouncer]] || users || {{status_ok}} || style="text-align: left;" | IRC proxy (IRC server relaying IRC communications, keeping connections open and remembering logs) |- | XMPP (Jabber) || [[Services/XMPP|XMPP Network]] || users || {{status_ok}} || style="text-align: left;" | Global Chat Network (inter-communication between many [[wikipedia:Xmpp#History|well-known public IM services]]) |- | rowspan="4" | Sharing || colspan="2" | [[Services/Gallery|Media Gallery]] || public/users || {{status_down}} || style="text-align: left;" | Photo and video gallery |- | colspan="2" | [[Services/Wiki|Wiki]] || public/users || {{status_ok}} || style="text-align: left;" | Documentation, technical knowledge, useful tips… |- | colspan="2" | [[Services/StuffCloud|StuffCloud]] || public/users || {{status_ok}} || style="text-align: left;" | Personal data store (contacts, calendars, files…) with syncing/sharing capabilities |- | colspan="2" | [[Services/FTP|File Repository]] || public/users || {{status_ok}} || style="text-align: left;" | Generic file sharing system (using FTP) |- | rowspan="3" | Utilities || colspan="2" | [[Services/WebFeeds|News WebReader]] || users || {{status_ok}} || style="text-align: left;" | News feeds reader through a web interface |- | colspan="2" | [[Services/NTP|Time Server]] || public || {{status_ok}} || style="text-align: left;" | System used to automatically setup time on your machines |- | colspan="2" | [[Services/Dico|Dictionary Server]] || public || {{status_ok}} || style="text-align: left;" | Words searching system via a dedicated software (using the DICT protocol) or a Web-interface |- | rowspan="6" | Development || colspan="2" | [[Services/Projects|Project Management & Issue Tracking]] || public/users || {{status_ok}} || style="text-align: left;" | Tool intended to help organize projects |- | rowspan="2" | Code || [[Services/VCS|VCS]] || public/users || {{status_ok}} || style="text-align: left;" | Code/configuration versioning tools (Git, SVN, Baz, Bzr…) |- | [[Services/CodeReview|Code Review]] || public/users || {{status_down}} || style="text-align: left;" | Tool intended to help improve software quality |- | rowspan="2" | Databases || [[Services/SQL|SQL]] || users || {{status_ok}} || style="text-align: left;" | SQL server (PostgreSQL or MySQL) |- | [[Services/LDAP|LDAP]] || users || {{status_ok}} || style="text-align: left;" | LDAP server (OpenLDAP) |- | colspan="2" | [[Services/SoftwareRepository|Software Repository]] || public/users || {{status_ok}} || style="text-align: left;" | Software repository, to provide custom packages (think Debian debs) or installation media (thinks DVDs) |- | rowspan="7" | Hosting || rowspan="2" | Hostnames Directory || [[Services/DNS|DNS]] || users || {{status_ok}} || style="text-align: left;" | Domain Name System (NS1/NS2, DNSSEC…) |- | [[Services/DDNS|Dynamic DNS]] || users || {{status_ok}} || style="text-align: left;" | Dynamic DNS entries, for places where IPs are dynamic and not under your control |- | rowspan="2" | Mail || [[Services/MailHosting|Mail Domains]] || users || {{status_ok}} || style="text-align: left;" | Mail hosting (MX1/MX2) |- | [[Services/MLHosting|Mailing-Lists]] || users || {{status_ok}} || style="text-align: left;" | Distribution lists for mail domains |- | colspan="2" | [[Services/WebHosting|Web Sites/Applications]] || users || {{status_ok}} || style="text-align: left;" | Web pages using HTML/XHTML, CSS, JS, and various server-side programming languages (SSI, PHP, Perl, Python, Ruby…) |- | colspan="2" | [[Services/XMPPHosting|XMPP Domains]] || users || {{status_ok}} || style="text-align: left;" | XMPP Node for a custom domain |- | colspan="2" | [[Services/Shell|Shell]] || trusted || {{status_ok}} || style="text-align: left;" | Useful for website administration, development, run custom scripts, persistent applications for text-mode geeks… |} == TODO == * Radio … b92cb0a973539b6c55a62a81a47bf419e05162d1 838 827 2020-04-08T11:29:23Z Duck 2 wikitext text/x-wiki Here is a short overview of the services provided by DuckCorp. Our services are supervised and important data are [[Services/Backup|saved regularly]]. {{warning}} [[Services/Security|Notes about security !]] {| class="wikitable" style="text-align: center; width: 100%;" |+ Available Services |- ! Category !! colspan="2" | Service !! Access !! Status !! Description |- | rowspan="5" | Communication || rowspan="2" | Mail || [[Services/Mail|eMails]] || users || {{status_ok}} || style="text-align: left;" | Mail boxes with anti-spam/anti-virus, filtering…, or mail redirections |- | [[Services/ML|Mailing-Lists]] || users || {{status_ok}} || style="text-align: left;" | Distribution lists for mails |- | rowspan="2" | IRC || [[Services/IRC|IRC Network]] || public || {{status_ok}} || style="text-align: left;" | MilkyPond Chat Network using a dedicated software or a Web-interface |- | [[Services/IRC-Bouncer|IRC Bouncer]] || users || {{status_ok}} || style="text-align: left;" | IRC proxy (IRC server relaying IRC communications, keeping connections open and remembering logs) |- | XMPP (Jabber) || [[Services/XMPP|XMPP Network]] || users || {{status_ok}} || style="text-align: left;" | Global Chat Network (inter-communication between many [[wikipedia:Xmpp#History|well-known public IM services]]) |- | rowspan="5" | Sharing || colspan="2" | [[Services/Gallery|Media Gallery]] || public/users || {{status_down}} || style="text-align: left;" | Photo and video gallery |- | colspan="2" | [[Services/Wiki|Wiki]] || public/users || {{status_ok}} || style="text-align: left;" | Documentation, technical knowledge, useful tips… |- | colspan="2" | [[Services/StuffCloud|StuffCloud]] || public/users || {{status_ok}} || style="text-align: left;" | Personal data store (contacts, calendars, files…) with syncing/sharing capabilities |- | colspan="2" | [[Services/FTP|File Repository]] || public/users || {{status_ok}} || style="text-align: left;" | Generic file sharing system (using FTP) |- | colspan="2" | [[Services/Radio|Radio]] || public/users || {{status_ok}} || style="text-align: left;" | Media Streaming |- | rowspan="3" | Utilities || colspan="2" | [[Services/WebFeeds|News WebReader]] || users || {{status_ok}} || style="text-align: left;" | News feeds reader through a web interface |- | colspan="2" | [[Services/NTP|Time Server]] || public || {{status_ok}} || style="text-align: left;" | System used to automatically setup time on your machines |- | colspan="2" | [[Services/Dico|Dictionary Server]] || public || {{status_ok}} || style="text-align: left;" | Words searching system via a dedicated software (using the DICT protocol) or a Web-interface |- | rowspan="6" | Development || colspan="2" | [[Services/Projects|Project Management & Issue Tracking]] || public/users || {{status_ok}} || style="text-align: left;" | Tool intended to help organize projects |- | rowspan="2" | Code || [[Services/VCS|VCS]] || public/users || {{status_ok}} || style="text-align: left;" | Code/configuration versioning tools (Git, SVN, Baz, Bzr…) |- | [[Services/CodeReview|Code Review]] || public/users || {{status_down}} || style="text-align: left;" | Tool intended to help improve software quality |- | rowspan="2" | Databases || [[Services/SQL|SQL]] || users || {{status_ok}} || style="text-align: left;" | SQL server (PostgreSQL or MySQL) |- | [[Services/LDAP|LDAP]] || users || {{status_ok}} || style="text-align: left;" | LDAP server (OpenLDAP) |- | colspan="2" | [[Services/SoftwareRepository|Software Repository]] || public/users || {{status_ok}} || style="text-align: left;" | Software repository, to provide custom packages (think Debian debs) or installation media (thinks DVDs) |- | rowspan="7" | Hosting || rowspan="2" | Hostnames Directory || [[Services/DNS|DNS]] || users || {{status_ok}} || style="text-align: left;" | Domain Name System (NS1/NS2, DNSSEC…) |- | [[Services/DDNS|Dynamic DNS]] || users || {{status_ok}} || style="text-align: left;" | Dynamic DNS entries, for places where IPs are dynamic and not under your control |- | rowspan="2" | Mail || [[Services/MailHosting|Mail Domains]] || users || {{status_ok}} || style="text-align: left;" | Mail hosting (MX1/MX2) |- | [[Services/MLHosting|Mailing-Lists]] || users || {{status_ok}} || style="text-align: left;" | Distribution lists for mail domains |- | colspan="2" | [[Services/WebHosting|Web Sites/Applications]] || users || {{status_ok}} || style="text-align: left;" | Web pages using HTML/XHTML, CSS, JS, and various server-side programming languages (SSI, PHP, Perl, Python, Ruby…) |- | colspan="2" | [[Services/XMPPHosting|XMPP Domains]] || users || {{status_ok}} || style="text-align: left;" | XMPP Node for a custom domain |- | colspan="2" | [[Services/Shell|Shell]] || trusted || {{status_ok}} || style="text-align: left;" | Useful for website administration, development, run custom scripts, persistent applications for text-mode geeks… |} 923574412021eb7eedb3ad10ef25f3c5f419dd1b 840 838 2020-04-08T11:41:04Z Duck 2 wikitext text/x-wiki Here is a short overview of the services provided by DuckCorp. Our services are supervised and important data are [[Services/Backup|saved regularly]]. {{warning}} [[Services/Security|Notes about security !]] {| class="wikitable" style="text-align: center; width: 100%;" |+ Available Services |- ! Category !! colspan="2" | Service !! Access !! Status !! Description |- | rowspan="5" | Communication || rowspan="2" | Mail || [[Services/Mail|eMails]] || users || {{status_ok}} || style="text-align: left;" | Mail boxes with anti-spam/anti-virus, filtering…, or mail redirections |- | [[Services/ML|Mailing-Lists]] || public/users || {{status_ok}} || style="text-align: left;" | Distribution lists for mails |- | rowspan="2" | IRC || [[Services/IRC|IRC Network]] || public || {{status_ok}} || style="text-align: left;" | MilkyPond Chat Network using a dedicated software or a Web-interface |- | [[Services/IRC-Bouncer|IRC Bouncer]] || users || {{status_ok}} || style="text-align: left;" | IRC proxy (IRC server relaying IRC communications, keeping connections open and remembering logs) |- | XMPP (Jabber) || [[Services/XMPP|XMPP Network]] || users || {{status_ok}} || style="text-align: left;" | Global Chat Network (inter-communication between many [[wikipedia:Xmpp#History|well-known public IM services]]) |- | rowspan="5" | Sharing || colspan="2" | [[Services/Gallery|Media Gallery]] || public/users || {{status_down}} || style="text-align: left;" | Photo and video gallery |- | colspan="2" | [[Services/Wiki|Wiki]] || public/users || {{status_ok}} || style="text-align: left;" | Documentation, technical knowledge, useful tips… |- | colspan="2" | [[Services/StuffCloud|StuffCloud]] || public/users || {{status_ok}} || style="text-align: left;" | Personal data store (contacts, calendars, files…) with syncing/sharing capabilities |- | colspan="2" | [[Services/FTP|File Repository]] || public/users || {{status_ok}} || style="text-align: left;" | Generic file sharing system (using FTP) |- | colspan="2" | [[Services/Radio|Radio]] || public/users || {{status_ok}} || style="text-align: left;" | Media Streaming |- | rowspan="3" | Utilities || colspan="2" | [[Services/WebFeeds|News WebReader]] || users || {{status_ok}} || style="text-align: left;" | News feeds reader through a web interface |- | colspan="2" | [[Services/NTP|Time Server]] || public || {{status_ok}} || style="text-align: left;" | System used to automatically setup time on your machines |- | colspan="2" | [[Services/Dico|Dictionary Server]] || public || {{status_ok}} || style="text-align: left;" | Words searching system via a dedicated software (using the DICT protocol) or a Web-interface |- | rowspan="6" | Development || colspan="2" | [[Services/Projects|Project Management & Issue Tracking]] || public/users || {{status_ok}} || style="text-align: left;" | Tool intended to help organize projects |- | rowspan="2" | Code || [[Services/VCS|VCS]] || public/users || {{status_ok}} || style="text-align: left;" | Code/configuration versioning tools (Git, SVN, Baz, Bzr…) |- | [[Services/CodeReview|Code Review]] || public/users || {{status_down}} || style="text-align: left;" | Tool intended to help improve software quality |- | rowspan="2" | Databases || [[Services/SQL|SQL]] || users || {{status_ok}} || style="text-align: left;" | SQL server (PostgreSQL or MySQL) |- | [[Services/LDAP|LDAP]] || users || {{status_ok}} || style="text-align: left;" | LDAP server (OpenLDAP) |- | colspan="2" | [[Services/SoftwareRepository|Software Repository]] || public/users || {{status_ok}} || style="text-align: left;" | Software repository, to provide custom packages (think Debian debs) or installation media (thinks DVDs) |- | rowspan="7" | Hosting || rowspan="2" | Hostnames Directory || [[Services/DNS|DNS]] || users || {{status_ok}} || style="text-align: left;" | Domain Name System (NS1/NS2, DNSSEC…) |- | [[Services/DDNS|Dynamic DNS]] || users || {{status_ok}} || style="text-align: left;" | Dynamic DNS entries, for places where IPs are dynamic and not under your control |- | rowspan="2" | Mail || [[Services/MailHosting|Mail Domains]] || users || {{status_ok}} || style="text-align: left;" | Mail hosting (MX1/MX2) |- | [[Services/MLHosting|Mailing-Lists]] || users || {{status_ok}} || style="text-align: left;" | Distribution lists for mail domains |- | colspan="2" | [[Services/WebHosting|Web Sites/Applications]] || users || {{status_ok}} || style="text-align: left;" | Web pages using HTML/XHTML, CSS, JS, and various server-side programming languages (SSI, PHP, Perl, Python, Ruby…) |- | colspan="2" | [[Services/XMPPHosting|XMPP Domains]] || users || {{status_ok}} || style="text-align: left;" | XMPP Node for a custom domain |- | colspan="2" | [[Services/Shell|Shell]] || trusted || {{status_ok}} || style="text-align: left;" | Useful for website administration, development, run custom scripts, persistent applications for text-mode geeks… |} 252701b4f9bcc22bba87df0fb6660feb67477b5c 0 48 828 536 2020-04-08T06:23:49Z Duck 2 wikitext text/x-wiki {{warning}} The backup sustem is down at the moment, this is [https://projects.duckcorp.org/issues/656 WIP]. Besides critical system and services data, most of users data are backuped up too. Data you can expect being saved: * mails, along with antispam learning data and SIEVE filters * shared services configurations and personnal data (webmail, projects, jabber, web stats, VCS…) * web data (hosted websites) * FTP data * /home on all machines where users can have shell access A few files or directory names are globally excluded from backup: * cache * .Trash In your personnal data, you can choose to exclude directories (and their children), either because you don't want us to copy your data elsewhere, or because it is not needed (allowing us to save data on the backup system). To do that, you simply need to create a ''.nobackup'' empty file inside the directories to ignore, nothing more. The backup system would detect it and skip the whole directory over. 04aa6e2e425aaa9edff2ef8f12e78ebe8d238477 0 180 829 2020-04-08T07:51:03Z Duck 2 Created page with "{{Template:Service | description = LDAP Databases, for various applications. | prerequisite = | account = local | ipv6 = true | security_notes = Access to the databases is sec..." wikitext text/x-wiki {{Template:Service | description = LDAP Databases, for various applications. | prerequisite = | account = local | ipv6 = true | security_notes = Access to the databases is secure. }} == Access == The master node is ''db-ldap-1.duckcorp.org'' and it is replicated on ''db-ldap-2.duckcorp.org''. A TLS connection is necessary to login. Part of the tree can be made accessible anonymously. There is no web interface. == Technical Details == This service is made using: * [https://www.openldap.org/ OpenLDAP] 0053ccf2c643cb7c5ce72392a0bb29a88e3be202 0 181 835 2020-04-08T08:06:01Z Duck 2 Created page with "{{Template:Service | description = A node on the Jabber network, based on XMPP, the open standard for instant messaging. | prerequisite = You need to buy a domain from a wi..." wikitext text/x-wiki {{Template:Service | description = A node on the Jabber network, based on XMPP, the open standard for instant messaging. | prerequisite = You need to buy a domain from a [[wikipedia:Domain_name_registrar|registrar]], setup a DNS (can be [[Services/DNS|hosted here]] too), and ask an administrator to configure this service. | account = global-reg | ipv6 = true | security_notes = This service is secure. }} == Full Hosting == You can have your own domain with the desired list of admins (JIDs) on our XMPP node. == Technical Details == See the [[Services/XMPP|XMPP Service]] page. eb19879619ee8c1a27b83ea3c7216ddf13bd73bc 836 835 2020-04-08T08:06:43Z Duck 2 wikitext text/x-wiki {{Template:Service | description = A node on the Jabber network, based on XMPP, the open standard for instant messaging. | prerequisite = You need to buy a domain from a [[wikipedia:Domain_name_registrar|registrar]], setup a DNS (can be [[Services/DNS|hosted here]] too), and ask an administrator to configure this service. | account = local | ipv6 = true | security_notes = This service is secure. }} == Full Hosting == You can have your own domain with the desired list of admins (JIDs) on our XMPP node. == Technical Details == See the [[Services/XMPP|XMPP Service]] page. 3a178a548ba40420b64b2ebf3cbf88ab08acfca7 837 836 2020-04-08T08:08:27Z Duck 2 /* Full Hosting */ wikitext text/x-wiki {{Template:Service | description = A node on the Jabber network, based on XMPP, the open standard for instant messaging. | prerequisite = You need to buy a domain from a [[wikipedia:Domain_name_registrar|registrar]], setup a DNS (can be [[Services/DNS|hosted here]] too), and ask an administrator to configure this service. | account = local | ipv6 = true | security_notes = This service is secure. }} == Full Hosting == You can have your own domain with the desired list of admins (JIDs) on our XMPP node. How you wish to authenticate your users needs to be discussed (we also provide databases). == Technical Details == See the [[Services/XMPP|XMPP Service]] page. 898adec62e65b674b91df29265c778d04fc8a805 0 182 839 2020-04-08T11:39:37Z Duck 2 Created page with "{{Template:Service | description = Media Streaming | prerequisite = If you wish to broadcast content, ask an administrator to configure this service. To avoid nasty content to..." wikitext text/x-wiki {{Template:Service | description = Media Streaming | prerequisite = If you wish to broadcast content, ask an administrator to configure this service. To avoid nasty content to be published only well-known users will be eligible for broadcasting. | account = local | ipv6 = true | security_notes = Security level of this service is unknown. }} == Access == You can access the web interface and see the current streams here: https://radio.duckcorp.org/ == Broadcast == If you wish to broadcast please contact an administrator and explain your project. == Technical Details == This service is made using: * [https://www.icecast.org/ Icecast] c6e8a6cc5f551f3b046cb25f9fb822b412b37c5f 0 183 842 2020-04-08T11:55:50Z Duck 2 Created page with "{{Template:Service | description = Mailing Lists Hosting | prerequisite = You need to buy a domain from a [[wikipedia:Domain_name_registrar|registrar]], setup a DNS (can be ..." wikitext text/x-wiki {{Template:Service | description = Mailing Lists Hosting | prerequisite = You need to buy a domain from a [[wikipedia:Domain_name_registrar|registrar]], setup a DNS (can be [[Services/DNS|hosted here]] too), and ask an administrator to configure this service. | account = local | ipv6 = true | security_notes = This service is secure. }} == Full Hosting == You can have your own lists with full administrative right using your domain. == Technical Details == See the [[Services/ML|ML Service]] page. 3816d637d733096812f0932bca03ebb0006e2d8f 0 184 843 2020-04-08T11:56:02Z Duck 2 Created page with "{{Template:Service | description = Mailing-Lists | prerequisite = None | account = local | ipv6 = true | security_notes = This service is secure. }} == Access == You can co..." wikitext text/x-wiki {{Template:Service | description = Mailing-Lists | prerequisite = None | account = local | ipv6 = true | security_notes = This service is secure. }} == Access == You can consult the lists and subscribe using the web interface at: https://lists.duckcorp.org/ == Official Lists == * '''DC-Admins''': A list to contact DuckCorp Administrators, anyone can post (with moderation) but only admins can read the archives * '''DC-Users''': A list to communicate news to our users. Only admins can post but anyone can read the archives. The latest entry is displayed on the DuckCorp website. == Lists for Projects == If you own a domain, then we can [[Services/MLHosting|host lists for you]] on it. If you do not have one we can host it on our domains. Please contact an administrator and explain your project. == Technical Details == This service is made using: * [https://www.list.org/ Mailman] bf1b651eb4a41c06d0eccb0d4608f6fe75b40c6d 845 843 2020-04-08T11:58:24Z Duck 2 wikitext text/x-wiki {{Template:Service | description = Mailing-Lists | prerequisite = | account = local | ipv6 = true | security_notes = This service is secure. }} == Access == You can consult the lists and subscribe using the web interface at: https://lists.duckcorp.org/ == Official Lists == * '''DC-Admins''': A list to contact DuckCorp Administrators, anyone can post (with moderation) but only admins can read the archives * '''DC-Users''': A list to communicate news to our users. Only admins can post but anyone can read the archives. The latest entry is displayed on the DuckCorp website. == Lists for Projects == If you own a domain, then we can [[Services/MLHosting|host lists for you]] on it. If you do not have one we can host it on our domains. Please contact an administrator and explain your project. == Technical Details == This service is made using: * [https://www.list.org/ Mailman] a7c09294d93cdfb1bfde9ba56c4cb5685a884683 10 58 844 341 2020-04-08T11:57:32Z Duck 2 wikitext text/x-wiki {| class="wikitable" |+ Service '{{TITLEPAGE}}' ! Description | colspan="4" | {{{description|}}} |- ! Prerequisite | colspan="4" | {{#if: {{{prerequisite|}}} | {{{prerequisite|}}} | None }} |- ! style="width: 15%;" | [[AccountType|Account]] | style="width: 15%;" | {{#if: {{{account|}}} | {{#ifeq: {{{account|}}} | global | <span style="color: green;">Global</span> | {{#ifeq: {{{account|}}} | global-reg | <span style="color: blue;">Global (registration required)</span> | <span style="color: orange;">Local (registration required)</span> }} }} | none }} ! style="width: 15%;" | [[wikipedia:Ipv6|IPv6 Ready]] | style="width: 8%;" | {{#if: {{{ipv6|}}} | {{#ifeq: {{{ipv6|}}} | true | <span style="color: green;">Yes</span> | <span style="color: orange;">No</span> }} | N/A }} | |- ! Security Notes | colspan="4" | {{{security_notes|}}} |} 56dfb654816bdc439a323886b1778654195fba0a 0 179 847 808 2020-04-08T11:59:24Z Duck 2 wikitext text/x-wiki {{Template:Service | description = Wiki with articles or tips on various subjects | prerequisite = | account = global | ipv6 = true | security_notes = This service is secure but don't input any private information as everything is public. }} == Access == Use this URL in your browser: https://wiki.duckcorp.org/ == Editorial Policy == This is a space of freedom but please be considerate with past works and use a respectful tone, thank you. == Documentation == * [https://www.mediawiki.org/wiki/Help:Contents Help Pages] == Technical Details == This service is made using: * [https://www.mediawiki.org/ MediaWiki] a74233d84e71ab5beaa81e707149b6c01c161b9a 0 75 850 663 2020-04-21T02:31:16Z Arnau 8 wikitext text/x-wiki {{Template:Service | description = A few VCS tools are available to DC users. | prerequisite = Write access is currently limited to people having a shell account. No prerequisite for read access. | account = global-reg | ipv6 = true | security_notes = This service is secure. }} == Access == Use the following URL to access public repositories: https://vcs.duckcorp.org/ Various VCS are possible: git, Mercurial, SVN, Bazaar… If you have [[Services/Shell|shell access]], public repositories are also available in ''/srv/vcs/'' on ''vcs.duckcorp.org'' == Managing a Repository == If you have [[Services/Shell|shell access]]: * ask an administrator if you need a space for public repositories * you can create private repositories at will in your home directory * ask an administrator if you need a project-specific space in ''/srv/projects/'' on ''vcs.duckcorp.org'' to store the project private repositories in it For the following steps, ask an administrator if you don't have shell access. === Git === A Git repository needs to be a ''bare'' repository, created like this: mkdir myrepo.git cd myrepo.git git init --bare A public repository should have a proper short description defined. Either edit the ''description'' file into the bare repository. Also, make sure that the repository has the proper permissions if you plan to activate Git or HTTP protocols: chmod -R o+rX myrepo.git To activate access via the Git protocol, you need to activate it: cd myrepo.git touch git-daemon-export-ok To activate access via the HTTP protocol, you need to enable updating the Git internal references: cd myrepo.git mv hooks/post-update.sample hooks/post-update Access methods sumup: * Direct SSH access: <tt>ssh://login@vcs.duckcorp.org/srv/vcs/git/...</tt> * [https://vcs-git.duckcorp.org/ Git via HTTP (read-only)] * Git via Git protocol using <tt>git://vcs-git.duckcorp.org/...</tt> to access <tt>/vcs/git/...</tt> * [https://vcs-git-viewer.duckcorp.org/ Git browser] fa8c8a51662088b3007d7134555d15555b6e5623 0 33 860 556 2021-03-26T10:17:39Z Duck 2 /* List of Previous Contributions */ wikitext text/x-wiki DuckCorp is built and maintained by volunteers, mostly with their own money. The services are totaly free of charge for all users, but you may wish to contribute to help us keep it working well and improve. == How to Contribute ? == You can help us with: * sponsoring: if you can host a machine and/or provide connectivity * equipments: see the list of possible improvements below * money: you can send us money which will be used in the association: ** by check (see the duckcorp.org whois for Duck's postal address, or ask him by mail or IRC) ** by account transfer to Duck's account in France or Japan ** by Paypal to duck@duckcorp.org == What can you Contribute ? == Here are ideas on which to contribute: * [[DcExpenses#Regular_Expenses|regular expenses]] * [https://projects.duckcorp.org/issues/537 Toushirou and Orfeo are getting old] * [???] buy a new machine, to provide: VMs, more services redondancy, ... (needed hardware not yet evaluated, more on this later) == List of Previous Contributions == Only pure financial contributions are listed here; equipments and sponsored purchases are listed on the [[DcExpenses|DuckCorp expenses page]]. {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Amount !! Donor !! Comments |- | 2021-03-26 || 20€ || Clawfire || via Paypal, commission paid by donnor |- | 2014-11-24 || 15€ || Clawfire || via Paypal, commission paid by donnor |- | 2014-07-14 || 15€ || Clawfire || via Paypal, commission paid by donnor |- | 2013-09-22 || 100$ USD || Damien || via Paypal => 69€ |- | 2011-01-10 || 500€ || AnonymousDonor1 || |- | 2010-05-16 || 42€ || Chloé || |} Note: early contributions in the CoinNetwork project are not taken into account, as most information is lost. b49fcd18c70a339be1da5a80250e993d306b173c 0 32 861 770 2021-04-28T06:14:11Z Duck 2 /* Exceptional Expenses */ wikitext text/x-wiki Let's be transparent about money too. Pure financial contributions are not listed here, but in the [[DcDonation|donation page]]. == Regular Expenses == This does not account for external sponsorship, but contributions by members. {| class="wikitable" style="text-align: center; width: 100%;" ! Object !! Amount !! Sponsor !! Comments |- | DuckCorp DNS domain || ~7€/year (since 2014-07)<br/><del>~15€/year</del> || Duck |- | MilkyPond DNS domain || ~7€/year (since 2014-07)<br/><del>~15€/year</del> || Rtp |- | Toushirou's housing || 41.56€/month || Duck || collocation with Sam (considering network switch and APC powerswitch shared rack space) |} Note: private Internet connections involved in DuckCorp's services are not taken into account. Thorfinn was once hosted on a VM coupled with the Internet offer, this was not mentioned either. == Exceptional Expenses == Note: this does not take into account expenses before 2006 because most historical data were lost. Note: machines, VMs, or containers hosted privately and involved in Duckcorp's services are not fully taken into account as owners kindly provided for their well being; this includes (by order of appearance): * Elwing (Duck): services reduced starting from 2010, and restarted in 2018 (see #637) * Daneel (Duck): in need of resurrection; was useful for backup and admin stuff * Korutopi (Arnau): stopped in 2018; was very useful for backup and monitoring * Nicecity (Pilou): backup (previously also monitoring) * Orthos (Pilou): monitoring === Improvement Expenses === {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Object !! Amount !! Sponsor !! Comments |- | 2018-06 || 3 disks for Toushirou-NG || ??? || Pilou || Western Digital Red 1To (WD10JFCX), RAID 1 with spare, see #612 |- | 2018-04 || more memory for Elwing || ??? || Arnau || 2*8GB, see #637. previously used in Mirimoto for Korutopi, unfortunately broken |- | 2018-04-25 || more memory for Elwing || 18770円 || Duck || 2*8GB, see #637 |- | 2018-04-11 || disks for Toushirou-NG || 241.12€ || Duck || 2*500GB SSD, see #614 |- | 2012-05-09 || more memory for Toushirou || ~60€ || Pilou || 2*2GB PC2-6400 instead of PC2-5300/5400 (see replacement memory details) |- | 2007-10 || replacement server (Orfeo-NG) || 1210€ || Duck || Sun Fire X4100 |- | 2007-05 || new server (Toushirou) || 1709.08€ || Duck || Supermicro PDSMI+ / Core 2 Duo E6600 / 2GB PC5400 / 3ware 9550SX4LP / 4x HD SATA II 250GB |} === Failure Expenses === {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Object !! Amount !! Sponsor !! Comments |- | 2017-??-?? || disks replacement || ???JPY || Arnau || still not stable, controller suspected to have problems |- | 2010-05-22 || replacement memory for Toushirou (2*2GB) || 105€ || Duck || PC2-5300/5400 2*2GB memory in a correct brand could not be found anymore, so we had to take PC2-6400 instead |- | 2010-01-06 || spare disk || 73€ || Duck || avoided tragedy when both disks in Daneel died at one week interval |- | 2007-09-29 || replacement server (Daneel-ng) || 534.90€ || Duck || machine too old and previous disk died horribly |- | 2006-01 || 300GB HD for Daneel (backup) || || AnonymousDonor1 || replaced since then |} === Other Expenses === {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Object !! Amount !! Sponsor !! Comments |- | 2010-06-29 || taxi || 26.20€ || Duck || Nerim bought Sivit, moving Toushirou to their new suite at Equinix PA3 (CBV->STD) |} b18460b0d8f6802a975ff168d49f559bbcae4281 872 861 2023-06-21T06:49:21Z Duck 2 /* Regular Expenses */ wikitext text/x-wiki Let's be transparent about money too. Pure financial contributions are not listed here, but in the [[DcDonation|donation page]]. == Regular Expenses == This does not account for external sponsorship, but contributions by members. {| class="wikitable" style="text-align: center; width: 100%;" ! Object !! Amount !! Sponsor !! Comments |- | DuckCorp DNS domain || 12.49€ (since 2017, [https://wiki.debian.org/MemberBenefits DD pricing])<br/><del>11.35 (since 2016-12, [https://wiki.debian.org/MemberBenefits DD pricing])</del><br/><del>~7€/year (since 2014-07, [https://wiki.debian.org/MemberBenefits DD pricing])</del><br/><del>~15€/year</del> || Duck |- | MilkyPond DNS domain || same prices as the DuckCorp domain || Rtp |- | Toushirou's housing || 63.18€/month (since 2023-04)<br/><del>54€/month (since 2022-05)</del><br/><del>40.80€/month</del> || Duck || collocation with Sam<br/>(considering network switch and APC powerswitch shared rack space) |} Note: private Internet connections involved in DuckCorp's services are not taken into account. Thorfinn was once hosted on a VM coupled with the Internet offer, this was not mentioned either. == Exceptional Expenses == Note: this does not take into account expenses before 2006 because most historical data were lost. Note: machines, VMs, or containers hosted privately and involved in Duckcorp's services are not fully taken into account as owners kindly provided for their well being; this includes (by order of appearance): * Elwing (Duck): services reduced starting from 2010, and restarted in 2018 (see #637) * Daneel (Duck): in need of resurrection; was useful for backup and admin stuff * Korutopi (Arnau): stopped in 2018; was very useful for backup and monitoring * Nicecity (Pilou): backup (previously also monitoring) * Orthos (Pilou): monitoring === Improvement Expenses === {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Object !! Amount !! Sponsor !! Comments |- | 2018-06 || 3 disks for Toushirou-NG || ??? || Pilou || Western Digital Red 1To (WD10JFCX), RAID 1 with spare, see #612 |- | 2018-04 || more memory for Elwing || ??? || Arnau || 2*8GB, see #637. previously used in Mirimoto for Korutopi, unfortunately broken |- | 2018-04-25 || more memory for Elwing || 18770円 || Duck || 2*8GB, see #637 |- | 2018-04-11 || disks for Toushirou-NG || 241.12€ || Duck || 2*500GB SSD, see #614 |- | 2012-05-09 || more memory for Toushirou || ~60€ || Pilou || 2*2GB PC2-6400 instead of PC2-5300/5400 (see replacement memory details) |- | 2007-10 || replacement server (Orfeo-NG) || 1210€ || Duck || Sun Fire X4100 |- | 2007-05 || new server (Toushirou) || 1709.08€ || Duck || Supermicro PDSMI+ / Core 2 Duo E6600 / 2GB PC5400 / 3ware 9550SX4LP / 4x HD SATA II 250GB |} === Failure Expenses === {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Object !! Amount !! Sponsor !! Comments |- | 2017-??-?? || disks replacement || ???JPY || Arnau || still not stable, controller suspected to have problems |- | 2010-05-22 || replacement memory for Toushirou (2*2GB) || 105€ || Duck || PC2-5300/5400 2*2GB memory in a correct brand could not be found anymore, so we had to take PC2-6400 instead |- | 2010-01-06 || spare disk || 73€ || Duck || avoided tragedy when both disks in Daneel died at one week interval |- | 2007-09-29 || replacement server (Daneel-ng) || 534.90€ || Duck || machine too old and previous disk died horribly |- | 2006-01 || 300GB HD for Daneel (backup) || || AnonymousDonor1 || replaced since then |} === Other Expenses === {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Object !! Amount !! Sponsor !! Comments |- | 2010-06-29 || taxi || 26.20€ || Duck || Nerim bought Sivit, moving Toushirou to their new suite at Equinix PA3 (CBV->STD) |} 6a47dc9e058d7bcaa7722f1da521e3edb67b1727 0 39 862 840 2021-05-20T03:23:46Z Duck 2 wikitext text/x-wiki Here is a short overview of the services provided by DuckCorp. Our services are supervised and important data are [[Services/Backup|saved regularly]]. {{warning}} [[Services/Security|Notes about security !]] {| class="wikitable" style="text-align: center; width: 100%;" |+ Available Services |- ! Category !! colspan="2" | Service !! Access !! Status !! Description |- | rowspan="7" | Communication || rowspan="2" | Mail || [[Services/Mail|eMails]] || users || {{status_ok}} || style="text-align: left;" | Mail boxes with anti-spam/anti-virus, filtering…, or mail redirections |- | [[Services/ML|Mailing-Lists]] || public/users || {{status_ok}} || style="text-align: left;" | Distribution lists for mails |- | rowspan="2" | IRC || [[Services/IRC|IRC Network]] || public || {{status_ok}} || style="text-align: left;" | MilkyPond Chat Network using a dedicated software or a Web-interface |- | [[Services/IRC-Bouncer|IRC Bouncer]] || users || {{status_ok}} || style="text-align: left;" | IRC proxy (IRC server relaying IRC communications, keeping connections open and remembering logs) |- | XMPP (Jabber) || [[Services/XMPP|XMPP Network]] || users || {{status_ok}} || style="text-align: left;" | Global Chat Network (inter-communication between many [[wikipedia:Xmpp#History|well-known public IM services]]) |- | Matrix || [[Services/Matrix|Matrix Node]] || users || {{status_ok}} || style="text-align: left;" | Decentralized Communication protocol |- | Web Key Directory || [[Services/WKD|WKD]] || users || {{status_ok}} || style="text-align: left;" | PGP Key Publishing Platform to simplify secure communication |- | rowspan="5" | Sharing || colspan="2" | [[Services/Gallery|Media Gallery]] || public/users || {{status_down}} || style="text-align: left;" | Photo and video gallery |- | colspan="2" | [[Services/Wiki|Wiki]] || public/users || {{status_ok}} || style="text-align: left;" | Documentation, technical knowledge, useful tips… |- | colspan="2" | [[Services/StuffCloud|StuffCloud]] || public/users || {{status_ok}} || style="text-align: left;" | Personal data store (contacts, calendars, files…) with syncing/sharing capabilities |- | colspan="2" | [[Services/FTP|File Repository]] || public/users || {{status_ok}} || style="text-align: left;" | Generic file sharing system (using FTP) |- | colspan="2" | [[Services/Radio|Radio]] || public/users || {{status_ok}} || style="text-align: left;" | Media Streaming |- | rowspan="3" | Utilities || colspan="2" | [[Services/WebFeeds|News WebReader]] || users || {{status_ok}} || style="text-align: left;" | News feeds reader through a web interface |- | colspan="2" | [[Services/NTP|Time Server]] || public || {{status_ok}} || style="text-align: left;" | System used to automatically setup time on your machines |- | colspan="2" | [[Services/Dico|Dictionary Server]] || public || {{status_ok}} || style="text-align: left;" | Words searching system via a dedicated software (using the DICT protocol) or a Web-interface |- | rowspan="6" | Development || colspan="2" | [[Services/Projects|Project Management & Issue Tracking]] || public/users || {{status_ok}} || style="text-align: left;" | Tool intended to help organize projects |- | rowspan="2" | Code || [[Services/VCS|VCS]] || public/users || {{status_ok}} || style="text-align: left;" | Code/configuration versioning tools (Git, SVN, Baz, Bzr…) |- | [[Services/CodeReview|Code Review]] || public/users || {{status_down}} || style="text-align: left;" | Tool intended to help improve software quality |- | rowspan="2" | Databases || [[Services/SQL|SQL]] || users || {{status_ok}} || style="text-align: left;" | SQL server (PostgreSQL or MySQL) |- | [[Services/LDAP|LDAP]] || users || {{status_ok}} || style="text-align: left;" | LDAP server (OpenLDAP) |- | colspan="2" | [[Services/SoftwareRepository|Software Repository]] || public/users || {{status_ok}} || style="text-align: left;" | Software repository, to provide custom packages (think Debian debs) or installation media (thinks DVDs) |- | rowspan="7" | Hosting || rowspan="2" | Hostnames Directory || [[Services/DNS|DNS]] || users || {{status_ok}} || style="text-align: left;" | Domain Name System (NS1/NS2, DNSSEC…) |- | [[Services/DDNS|Dynamic DNS]] || users || {{status_ok}} || style="text-align: left;" | Dynamic DNS entries, for places where IPs are dynamic and not under your control |- | rowspan="2" | Mail || [[Services/MailHosting|Mail Domains]] || users || {{status_ok}} || style="text-align: left;" | Mail hosting (MX1/MX2) |- | [[Services/MLHosting|Mailing-Lists]] || users || {{status_ok}} || style="text-align: left;" | Distribution lists for mail domains |- | colspan="2" | [[Services/WebHosting|Web Sites/Applications]] || users || {{status_ok}} || style="text-align: left;" | Web pages using HTML/XHTML, CSS, JS, and various server-side programming languages (SSI, PHP, Perl, Python, Ruby…) |- | colspan="2" | [[Services/XMPPHosting|XMPP Domains]] || users || {{status_ok}} || style="text-align: left;" | XMPP Node for a custom domain |- | colspan="2" | [[Services/Shell|Shell]] || trusted || {{status_ok}} || style="text-align: left;" | Useful for website administration, development, run custom scripts, persistent applications for text-mode geeks… |} 76749c3ad2c341368e42983e5a8af649cffedf29 0 185 863 2021-05-20T04:00:14Z Duck 2 Created page with "{{Template:Service | description = Directory and Update service to publish PGP Keys | prerequisite = | account = global-reg | ipv6 = true | security_notes = This service is s..." wikitext text/x-wiki {{Template:Service | description = Directory and Update service to publish PGP Keys | prerequisite = | account = global-reg | ipv6 = true | security_notes = This service is secure. }} == Access == To access this service you need PGP identities using email addresses on domains managed by DuckCorp. == Requesting an identity to be published == The ''gpg-wks-client'' command used below might not be in your path, it can often be found inside ''/usr/lib/gnupg/''. If the ''--send'' option fails in the following command, you can remove it and pipe the result into ''/usr/sbin/sendmail -oi -t'' directly. Request the inclusion or update of your key: gpg-wks-client --create --send <gpgkey-fpr> <email> <gpgkey-fpr> is the fingerprint of your GPG key. <email> must match one of the key identities (uids) as well as one of the published domains. When you receive the confirmation request email, save the attachment and send the confirmation: gpg-wks-client --send --read < <file> When you receive the publishing notification it is then published. == Verifying an identify is published == You can check the key is properly published for an identity with: gpg --auto-key-locate clear,nodefault,wkd --locate-keys <email> == Technical Details == This service is made using: * [https://gnupg.org/ GnuPG] b93ca62a270af204cfa6630c5ae9f306cfed5982 864 863 2021-05-20T09:02:59Z Duck 2 wikitext text/x-wiki {{Template:Service | description = Directory and Update service to publish PGP Keys. This service can be used to associate your PGP identities that matches the domains managed via DuckCorp with your public key. Many email clients can now use this method to discover your public key in order to encrypt mails to you. | prerequisite = | account = global-reg | ipv6 = true | security_notes = This service is secure. }} == Access == To access this service you need PGP identities using email addresses on domains managed by DuckCorp. == Requesting an identity to be published == If you have multiple identities matching domains managed via DuckCorp then you need to request publishing for each one separately. The ''gpg-wks-client'' command used below might not be in your path, it can often be found inside ''/usr/lib/gnupg/''. If the ''--send'' option fails in the following command, you can remove it and pipe the result into ''/usr/sbin/sendmail -oi -t'' directly. Request the inclusion or update of your key: gpg-wks-client --create --send <gpgkey-fpr> <email> <gpgkey-fpr> is the fingerprint of your GPG key. <email> must match one of the key identities (uids) as well as one of the published domains. When you receive the confirmation request email, save the attachment and send the confirmation: gpg-wks-client --send --read < <file> When you receive the notification email it is then published. == Verifying an identify is published == You can check the key is properly published for an identity with: gpg --auto-key-locate clear,nodefault,wkd --locate-keys <email> == Technical Details == This service is made using: * [https://gnupg.org/ GnuPG] 178fc37185b18a2aac6dfad97fbc24a2870e89ec 0 186 865 2021-05-20T09:36:40Z Duck 2 Created page with "{{Template:Service | description = Matrix is a decentralized communication Network. We have our own node associated with the MilkyPond domain. DuckCorp-specific channels are a..." wikitext text/x-wiki {{Template:Service | description = Matrix is a decentralized communication Network. We have our own node associated with the MilkyPond domain. DuckCorp-specific channels are available, but you can connect to any channel or talk to anyone on the global network. | prerequisite = | account = global-reg | ipv6 = true | security_notes = This service is secure. }} == Access == Use your LDAP uid/password on the '''milkypond.org''' domain to connect and your account will be created automagically the first time. {{warning}} '''Do not enable Integrations''': these are remote apps you can integrate into the Element web and Android applications but [https://github.com/vector-im/element-web/issues/7757 they are not opensource] and we don't know if they are secure and respect privacy === Using an Application === There are multiple clients on various platforms, you can pick one in this list: https://matrix.org/clients/ We tested Quaternion on Debian GNU/Linux and that worked fine. On Android the Element app (available on [https://f-droid.org/ F-Droid]) is very nice. === Using a Web Interface === Use the following URL: https://matrixonweb.milkypond.org/ == Official Channels == (like on IRC) * '''#MilkyPond''': main channel used to meet with other users and friends and ask general questions * '''#DuckCorp''': contact with DuckCorp Administrators and technical discussions == (experimental) Bridge with IRC == We experimented with a bridge to join communication between the #MilkyPond and #DuckCorp IRC channels and their Matrix counterpart but that did not work well because of several limitations and the fact end-to-end encryption was enabled on Matrix thus preventing the discussions to flow towards IRC which does not support such encryption. At the moment the bridge is only configured to bridge the #taiste channel for further experiments. The goal was to prevent splitting the community but maybe that's not such a good idea. Ideas welcome. == Technical Details == This service is made using: * [https://matrix.org/docs/projects/server/synapse Synapse] * [https://github.com/vector-im/element-web/ Element-web] * [https://github.com/matrix-org/matrix-appservice-irc Matrix IRC Bridge] 969cab78707864d062caf263c2ec39387b6f4271 870 865 2021-10-27T11:09:45Z Duck 2 /* Official Channels */ wikitext text/x-wiki {{Template:Service | description = Matrix is a decentralized communication Network. We have our own node associated with the MilkyPond domain. DuckCorp-specific channels are available, but you can connect to any channel or talk to anyone on the global network. | prerequisite = | account = global-reg | ipv6 = true | security_notes = This service is secure. }} == Access == Use your LDAP uid/password on the '''milkypond.org''' domain to connect and your account will be created automagically the first time. {{warning}} '''Do not enable Integrations''': these are remote apps you can integrate into the Element web and Android applications but [https://github.com/vector-im/element-web/issues/7757 they are not opensource] and we don't know if they are secure and respect privacy === Using an Application === There are multiple clients on various platforms, you can pick one in this list: https://matrix.org/clients/ We tested Quaternion on Debian GNU/Linux and that worked fine. On Android the Element app (available on [https://f-droid.org/ F-Droid]) is very nice. === Using a Web Interface === Use the following URL: https://matrixonweb.milkypond.org/ == Official Channels == The is a '''DuckCorp''' space containing the following channels: (like on IRC) * '''#MilkyPond''': main channel used to meet with other users and friends and ask general questions * '''#DuckCorp''': contact with DuckCorp Administrators and technical discussions == (experimental) Bridge with IRC == We experimented with a bridge to join communication between the #MilkyPond and #DuckCorp IRC channels and their Matrix counterpart but that did not work well because of several limitations and the fact end-to-end encryption was enabled on Matrix thus preventing the discussions to flow towards IRC which does not support such encryption. At the moment the bridge is only configured to bridge the #taiste channel for further experiments. The goal was to prevent splitting the community but maybe that's not such a good idea. Ideas welcome. == Technical Details == This service is made using: * [https://matrix.org/docs/projects/server/synapse Synapse] * [https://github.com/vector-im/element-web/ Element-web] * [https://github.com/matrix-org/matrix-appservice-irc Matrix IRC Bridge] c9d095f91909fb367e535f13f3fbace29b3abd19 0 43 866 815 2021-05-20T17:09:21Z Duck 2 wikitext text/x-wiki {{Template:Service | description = Available services: * full hosting (NS1) on our servers * replication (NS2) on our servers or, at your choice, partner servers (currently via Hivane) | prerequisite = You need to buy a domain from a [[wikipedia:Domain_name_registrar|registrar]] and ask an administrator to configure this service. | account = global-reg | ipv6 = true | security_notes = Your zone content can be secured using DNSSEC, and replication can be secured too using TSIG (see below). }} == Master Zones Administration == To have your master zone modified on our servers, you can: * use our [[UserMagicalInterface]] * ask administrators == DNS Security == To provide as much security as possible, DC supports the following mechanisms. === [[wikipedia:TSIG|TSIG]] === This protocol allows a secure transfer of zones between primary and secondary servers. The DC's DNS servers support TSIG and comminication between them are always secured. The following entities are known to support TSIG and can then securely transfer zones to/from DC: * [https://www.hivane.net/ Hivane] === [[wikipedia:Domain_Name_System_Security_Extensions|DNSSEC]] === ==== What is DNSSEC? ==== This protocol aims at establishing a chain of trust, from the root of the DNS, to ensure response to queries on a zone has not been altered on the way. With the root zone public key, it is possible to validate the replies step by step down to your zone, for example: root public key -> ''.'' zone -> NS for ''org.'' -> ''org.'' zone -> NS for ''milkypond.org.'' -> ''milkypond.org.'' zone -> ''irc.milkypond.org.'' entry. ==== How to use it for my zones? ==== DC DNS servers are able to handle the complicated procedure needed to sign a zone for you. You can just modify it the classic way, and have it signed automatically. If your provider gladly support DNSSEC, you just need to ask us to switch the zone to the secure mode. Beware DNS always means propagation delays, so you may have to wait a few days before the switch is completed and your zone fully secured over the whole world. ==== How to test my zone is secured? ==== First, you need a validating DNS server: * [https://nlnetlabs.nl/projects/unbound/about/ Unbound] does this out of the box * [https://bind9.net/ Bind] might need some settings if it's an old version: ** the root zone public key is now installed and configured in all major distributions ** add in your global options (''/etc/bind/named.conf.options''): dnssec-enable yes; dnssec-validation yes; ** restart bind Then, you can check it with the ''dig'' tool (available in the ''dnsutils'' Debian package): dig +dnssec <zone> Look at the flags: it is secured if you find the ''ad'' flag. If there is the ''aa'' flag instead, then you are interrogating on of the authoritative DNS servers for the zone, it is also secure, but better test it on another server to be sure it is propagated. {{warning}} If you check an entry of your zone which is a CNAME, beware the CNAME is resolved and if the destination name cannot be validated, then your entry won't either. == Documentation == * generic documentation on [[wikipedia:Domain_Name_System|DNS]] == Technical Details == This service is made using: * [https://bind9.net/ Bind9] 446530182427bf134195b571c5c944a9667cae2b 0 37 867 145 2021-05-29T09:07:20Z Duck 2 wikitext text/x-wiki {{Robelbox|title=Technical Information|theme={{{theme|9}}}}} {{Padbox}} * [[DcArchitecture|Architecture]] * [[Services| Available Services]] * [[UserMagicalInterface|User Magical Interface]] ('''DEPRECATED''', use ''dns4tenants'' instead) {{todo}} work in progress... {{Padbox/close}} {{Robelbox/close}} 16caf1ae98609876137c4474d45af31f3a51032f 0 149 868 804 2021-06-30T13:58:33Z Duck 2 wikitext text/x-wiki {{Template:Service | description = Web sites and applications hosting for DC users. | prerequisite = You would need a shell access, FTP access or VCS repository | account = global-reg | ipv6 = true | security_notes = This service is secured using HTTPS. The remaining non-HTTPS websites are being upgraded. }} == Access == Web hosting happens on Toushirou. Available methods: * using a [[Services/Shell|shell account]] is you already have one; if not, you might ask for one, but this is not easily granted for security reasons * using a [[Services/VCS|VCS repository]] * using an [[Services/FTP|FTP account]] is also possible but we try to deprecate this method. == Available Protocols == All websites are using HTTPS, with HTTP redirecting to HTTPs for security and privacy. Except if there is a very good reason, HTTP-only or without redirection is not an option. All websites are also available via HTTP2, with the only exception being sites relying on Apache indexes because of [https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850947 this bug]. == Available Languages == We currently support these langages: * Python 2.7 and 3.7, and WSGI applications * Ruby 2.5, and Rack-enabled (Rails…) applications * Perl 5.28 * PHP 7.3 * NodeJS 10.15 applications Java applications are not an option, but we may consider other languages though. If you need libraries and tools installed, please contact an administrator. == Website Database == SQL databases are available, please look at this [[Services/SQL|corner of the documentation]]. If the database node is hosted on Toushirou, then you may use UNIX socket access for increased performances. == Website Generation == If you have shell access, then you can handle this yourself, setup hooks/crontabs/… as needed. Contact us if you need help. If you don't have a shell access and your application needs to be generated, please ask an administrator. It may be possible to use a hook or crontab (not involving uncontrolled code for security reasons). == Website Authentication == If your application does not provide authentication you can use a file created with ``htpasswd`` and add in the directory to protect a ``.htaccess`` with: AuthBasicProvider file AuthUserFile /srv/pages-perso/<uid>/<directory-to-protect>/.htpasswd If you wish to require DuckCorp users you can use the DLAP provider and even combine the two: AuthBasicProvider ldap file AuthUserFile /srv/pages-perso/<uid>/<directory-to-protect>/.htpasswd Require valid-user == Technical Details == This service is made using: * [https://httpd.apache.org/ Apache Httpd] 1e778c7e5d711d7bd881cd69c6ee811625e2f1c0 0 55 871 859 2021-12-08T04:07:58Z Duck 2 /* Using an IRC Software */ wikitext text/x-wiki {{Template:Service | description = [[wikipedia:Irc|IRC]] (Internet Relay Chat) is a chat system. We have our own internal network, formerly used to contact administrators and discuss with other users. Even is not advertise widely, external people may join the network, so you can invite your friend. | prerequisite = | account = | ipv6 = true | security_notes = This service is secure. Users' identity is not guarantied though, but you can trust a service account once validated using another secure channel. }} == Access == === Using an IRC Software === To connect you need and IRC client, like for example: * [https://www.pidgin.im Pidgin] * [https://weechat.org/ WeeChat] If you have problems seeing the modes then you probably need to upgrade your client to [https://docs.inspircd.org/faq/#why-does-my-client-not-show-mode-changesopped-users-on-joinetc-correctly-when-using-inspircd-v3 fix bugs parsing the protocol]. You need to configure these parameters: * host: irc.milkypond.org * port: 6667, 6669, 6680 or '''6697''' * tls: enabled (compulsory since 2021-03-16) No password is needed to connect but you may pass your Service Account password and it will be passed to NickServ automagically. The recommended and most secure configuration is: * create a certificate and authenticate with CertFP (see below) * create a service account and associate your certificate with your account === Using a Web Interface === Use the following URL: https://irconweb.milkypond.org/ == Official Channels == * '''#MilkyPond''': main channel used to meet with other users and friends and ask general questions * '''#DuckCorp''': contact with DuckCorp Administrators and technical discussions == Contacting IRC Administrators == In case of problems on IRC you can find connected administrators using this command (mind the idle time): /QUOTE STATS P == Features == === Commands === You can see available commands using this command: /QUOTE HELP You can get help about a particular command using this command: /QUOTE HELP &lt;command&gt; The list of commands is also [https://docs.inspircd.org/2/commands/ documented here]. ==== Additional Commands for IRC Administrators ==== All special commands are listed in the Oper MOTD. === User Modes === You can see available user modes using this command: /QUOTE HELP UMODES ==== Filtering Unwanted Messages ==== We try to ban spam and nasty people from our network but if we're not fast enough (sleeping…) you might want to take action into your own hands. With the "Caller ID" mode (user mode +g) a user can define an access list. With this mode you will be notified when someone not in your accept list is trying to contact you, but at a reasonable rate. The person trying to contact you will get notified their messaqe has been blocked. You can use the '''ACCEPT''' command to define your accept list. To add someone to your list: /QUOTE ACCEPT &lt;nick&gt;,&lt;nick&gt;,&lt;nick&gt;,… That user will now be able to send messages to your client until the association is broken. Associations break in one of the following situations: when an accepted user QUIT's (or is on the other side of a split), you QUIT, or the accepted user changes their nick. The reason why a remote user's nick change will remove them from your accept list is so that you cannot track a user after they changed their nick. You can view you accept list at any time: /QUOTE ACCEPT * Removing a user from your accept list can be done with this command: /QUOTE ACCEPT -&lt;nick&gt; === Channel Modes === You can see available channel modes using this command: /QUOTE HELP CHMODES === IRC Services === To help not loose your favorite nick or channel, the IRC Services can register them so you're still in control. It also helps manage channel with a variety of tools. Look at the user introduction manual in the documentation below. List of Services: * ALIS: search available channels * USERSERV: register an account * INFOSERV: read operator news (not in use in this network, we send global announces and post to the mailing-list) * STATSERV: few network information (not that useful) List of Services available with an account (see USERSERV): * NICKSERV: register nicknames * GROUPSERV: manage group of users used in ACLs * CHANSERV: register and manage channels * MEMOSERV: send and receive memos from other registered users To get help on each service commands, use the following command: /QUOTE &lt;service&gt; HELP ==== Register an Account ==== To create an account first register it: /QUOTE nickserv register &lt;password&gt; &lt;email&gt; Then check your emails and use the provided verification command that should look like this: /QUOTE nickserv verify register &lt;nick&gt; &lt;code&gt; Your account will not be valid until verified. If you change your email address you will need to revalidate it using the same process. ==== Secure Service Authentication (CERTFP) ==== You can authenticate to your service account using a password, but it is more secure to use a certificate and not too complicated to setup. The Freenode network has a good [https://freenode.net/kb/answer/certfp documentation for this feature]. Don't forget to select the SASL/EXTERNAL authentication method and use TLS. The commands to associate your certificate to your account are the same as on Freenode: * get your fingerprint with: /whois &lt;mynick&gt; * add the fingerprint to your account (you need to have registered and account and by logged in): /QUOTE nickserv cert add &lt;fpr&gt; ==== Additional Services for IRC Administrators ==== (exact privileges depends on trust and delegation) * OPERSERV: superadmin commands * GLOBAL: messaging all users == Technical Details == This service is made using: * [https://www.inspircd.org/ InspIRCd] * [https://atheme.github.io/atheme.html Atheme IRC Services] * [https://thelounge.github.io/ The Lounge] (Web UI) 42486d0acd29d4c6a5de3b4b998181a2d886e699 0 33 873 860 2023-07-03T11:40:59Z Duck 2 /* List of Previous Contributions */ wikitext text/x-wiki DuckCorp is built and maintained by volunteers, mostly with their own money. The services are totaly free of charge for all users, but you may wish to contribute to help us keep it working well and improve. == How to Contribute ? == You can help us with: * sponsoring: if you can host a machine and/or provide connectivity * equipments: see the list of possible improvements below * money: you can send us money which will be used in the association: ** by check (see the duckcorp.org whois for Duck's postal address, or ask him by mail or IRC) ** by account transfer to Duck's account in France or Japan ** by Paypal to duck@duckcorp.org == What can you Contribute ? == Here are ideas on which to contribute: * [[DcExpenses#Regular_Expenses|regular expenses]] * [https://projects.duckcorp.org/issues/537 Toushirou and Orfeo are getting old] * [???] buy a new machine, to provide: VMs, more services redondancy, ... (needed hardware not yet evaluated, more on this later) == List of Previous Contributions == Only pure financial contributions are listed here; equipments and sponsored purchases are listed on the [[DcExpenses|DuckCorp expenses page]]. {| class="wikitable" style="text-align: center; width: 100%;" ! Date !! Amount !! Donor !! Comments |- | 2023-07-02 || 100€ || Louis || via Paypal, commission paid by donnor |- | 2021-03-26 || 20€ || Clawfire || via Paypal, commission paid by donnor |- | 2014-11-24 || 15€ || Clawfire || via Paypal, commission paid by donnor |- | 2014-07-14 || 15€ || Clawfire || via Paypal, commission paid by donnor |- | 2013-09-22 || 100$ USD || Damien || via Paypal => 69€ |- | 2011-01-10 || 500€ || AnonymousDonor1 || |- | 2010-05-16 || 42€ || Chloé || |} Note: early contributions in the CoinNetwork project are not taken into account, as most information is lost. bafb5e554df39708f3ebfc1c5fc7c014f06b9282